Building a Reusable Sprint Retrospective Template

Build a reusable retrospective template that maps activities, timings and facilitator cues to the five phases, so anyone can run a solid sprint retro.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

A reusable retrospective template is a written plan for a retrospective that a facilitator can pick up and run with little preparation. It follows the five phases of the Five-Step Retrospective Framework and specifies, for each phase, an activity, a timebox, the materials needed and what the facilitator says to start and finish it. A good template turns the framework from something one skilled facilitator knows into something the whole team can use.

Templates solve three problems. Preparing a retrospective from scratch every sprint takes time, and busy facilitators cut corners. Retrospectives run by different people vary widely in quality. And a new facilitator, without a plan, tends to fall back on an open discussion that skips the insight and decision phases. A template with the phases built in prevents all three.

Many organizations publish their own. GitLab's engineering handbook recommends an agenda of introduction, gather data, generate insights, decide what to do and close, and points groups to a retrospective issue template for collecting feedback asynchronously (GitLab Handbook). Atlassian's retrospective play is itself a template: a one-hour session in five timed steps, with preparation time, group size and follow-up guidance (Atlassian).

A retrospective facilitation template needs more than a list of activities. Retromat, which generates random plans with one activity per phase, warns that the activities in such a plan rarely fit together until someone adjusts them (Retromat). A template is that adjustment written down: activities chosen so each phase's output feeds the next, timings that add up to the session length, and cues that help a facilitator move between phases.

A small library works better than one template. Most teams need a standard sprint template, a short version for weeks with little time, a longer one for releases or incidents, and a remote version. This skill covers how to design, test and maintain them.

How It Works

Every template has the same skeleton: the five phases, each with an activity, a timebox, materials and cues. Two published one-hour plans show how the time can be split:

Both give the largest share to insights and decisions, where the actions come from. Treat the splits as starting points and adjust them after running the template. For session length, the Scrum Guide caps the retrospective at a maximum of three hours for a one-month Sprint and says it is usually shorter for shorter Sprints (Scrum Guide); the Agile Alliance describes retrospectives as typically lasting between one and three hours (Agile Alliance).

The activity slot for each phase is where templates differ. Choose activities that connect: a timeline in the data phase produces events that a 5 Whys can analyze; a prompt board produces notes that cluster easily. Include one activity that brings in project data, since research by Matthies and Dobrigkeit found most retrospective activities "neglect to take existing project data into account" (Matthies and Dobrigkeit).

Facilitator cues make the template usable by someone else. For each phase, write the opening sentence, the instructions for the activity, and the transition to the next phase. Add notes on what to watch for, such as a check-in that shows low energy or a data phase running long.

Metadata makes a library searchable: the situation each template suits, its length, whether it works remotely, and when it was last run. A template that has not been used or reviewed for a long time should be retired or refreshed.

Step-by-Step Guide

Step 1: Define the template's purpose and length

Decide what situation the template is for: a regular sprint, a short week, a release or incident, a new team, or a remote session. Set the total length. Write the purpose in one sentence at the top of the template so a facilitator can tell at a glance whether it fits.

Step 2: Choose an activity for each phase

Pick one activity per phase that suits the template's purpose. Start with the data activity, then choose the others to connect to it. Check that each activity's output is the input the next one needs. Name a simpler backup activity for the phases most likely to run into trouble.

Step 3: Assign timeboxes

Split the total time across the phases, giving the largest share to insights and decisions. Include the time needed to explain each activity. Leave a small buffer for discussion that runs long. Check that the timeboxes add up to the session length.

Step 4: Write facilitator cues and transitions

For each phase, write the opening line, the activity instructions and the transition sentence. Add notes on what to watch for and how to adapt. Write for a facilitator who has not run this template before. Keep the cues short enough to read at a glance during the session.

Step 5: List materials and preparation

List what needs to exist before the session: a board layout, prompts, data to pull, the previous actions, and any digital tools. Note how far in advance each item is needed. For remote templates, include instructions for asynchronous data collection and anonymous input.

Step 6: Tag and store the template

Record the template's purpose, length, format and date. Store it where every facilitator on the team can find it. Link related templates, such as the short and long versions of the same plan. Keep the library small enough that people know what is in it.

Step 7: Run it, review it and refine it

Use the template in a real retrospective and note where the timing slipped, which cues were unclear and how the team responded. Use the closing feedback as evidence. Update the template and record what changed. Retire templates that nobody uses or that consistently get poor feedback.

Best Practices

• Build the five phases into every template. A template that skips a phase teaches facilitators to skip it too.
• Give the most time to insights and decisions. Both published plans in the table above put the largest blocks there.
• Write cues for someone who is not you. A template only one person can run is a personal plan.
• Include real data in at least one activity, which Matthies and Dobrigkeit argue is advantageous and underused.
• Keep a short and a remote version of the standard template. They are the variants teams reach for most often.
• Review templates using the team's closing feedback, and record what you changed and why.

Common Mistakes

• Building one template and using it forever: The same plan every sprint produces the same answers. Keep a small library and rotate.
• Timeboxes that do not add up: A template that is ten minutes too long cuts the close every time. Check the arithmetic and include explanation time.
• Activities that do not connect: If the insight activity cannot use the data collected, both phases lose value. Check the flow before saving a template.
• Missing facilitator cues: A list of activity names leaves a new facilitator guessing. Write the opening, instructions and transition for each phase.
• Never retiring templates: A library full of unused plans is hard to search. Remove templates that no longer fit.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: Five-Step Retrospective Framework

Related Skills

• Choosing Retrospective Activities and Exercises
• Setting the Stage in a Sprint Retrospective
• Closing a Retrospective Meeting Effectively

Sources

• GitLab Handbook: Group Retrospectives
• Atlassian Team Playbook: Sprint Retrospective
• Retromat: About
• Retrium: The Five Phases of a Successful Retrospective
• The Scrum Guide
• Agile Alliance Glossary: Heartbeat Retrospective
• Matthies and Dobrigkeit: Experience vs Data

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.