Decide together
Run a sprint retrospective
A sprint retrospective agenda, formats and questions to copy, and how to collect anonymous input and vote on what to change.
Last updated
A retrospective is the meeting where a team looks back at the last sprint and agrees on what to change in the next one. It works when everyone speaks up and the team leaves with one or two concrete actions.
A 45-minute agenda
| Time | Step |
|---|---|
| 5 min | Check in. One question on how the sprint felt. |
| 10 min | Collect. Everyone writes down what went well and what didn’t. |
| 10 min | Group and discuss. Cluster similar points and talk through them. |
| 5 min | Vote. Pick the one or two topics that matter most. |
| 10 min | Decide actions. Who does what by when. |
| 5 min | Close. Check the actions from last time and rate the retro itself. |
Formats to copy
Start, stop, continue
- What should we start doing?
- What should we stop doing?
- What should we continue doing?
Mad, sad, glad
- What made you mad?
- What made you sad?
- What made you glad?
The 4 Ls
- What did you like?
- What did you learn?
- What was lacking?
- What did you long for?
Sailboat
- What’s the wind in our sails?
- What’s the anchor holding us back?
- Which rocks lie ahead?
Change the format every few sprints. The same three questions every two weeks get the same three answers.
More questions
- How did this sprint feel, from 1 to 10?
- What surprised us?
- Where did we lose the most time?
- What did we learn that the next sprint should use?
- Which decision would we make differently?
- Who deserves a thank-you?
- Did we finish what we planned? If not, why?
- What’s one thing we should try for just one sprint?
Run it with StrawPoll
- Start from the Team retrospective template: a scale for how the sprint felt and two open questions. Change the questions to your format.
- Send the link a day before, or give five quiet minutes at the start. Writing first, talking second gives everyone a voice, not just the fastest speakers.
- Keep it anonymous. Don’t add a name question, and see Collect honest, anonymous team feedback for the settings.
- Show the scale result with present mode to open the discussion.
- To choose what to work on, put the topics into a Multiple choice question with Allow more than one answer, or into a Ranking question, and let the team vote. The Prioritize the roadmap template does the same.
For estimating the next sprint’s stories, there’s a Planning poker template.
Make the actions stick
- Take few. One or two actions per sprint. Five actions mean none get done.
- Give each an owner and a date. “We should communicate better” isn’t an action. “Ana sets up a shared channel by Friday” is.
- Start the next retro with them. Done, not done, or dropped.
Follow the mood over time
Ask the same scale question every sprint and you’ll see a trend. With repeat voting, the team can answer the same poll once per sprint. Between retros, a short check-in question at the start of a meeting shows early when something is off.