How to facilitate a sprint retrospective
Last reviewed by The thinkdrop facilitation team
To facilitate a sprint retrospective, start by reviewing whether last retro's actions happened, then give the team five silent minutes to write cards about specific moments in the sprint. Group the cards, discuss only the top three, and end with two or three actions that each have a named owner. Keep the whole session to 60 minutes for a two-week sprint.
Key facts
- Length
- 60 minutes for a two-week sprint
- Attendees
- The delivery team only, 5–9 people
- Silent writing
- 5 minutes before any discussion
- Topics discussed
- Top 3 only
- Actions taken away
- 2–3, each with an owner
- First agenda item
- Did last retro's actions happen?
Step by step
- Check last retro's actions first — Open with the actions from the previous retrospective and mark each done or not done. Nothing improves a team's engagement with retros faster than evidence that the last one changed something — and nothing kills it faster than three sprints of unactioned lists.
- Set the frame and the safety rule — State that the goal is the system, not the people. The prime directive — everyone did the best they could with what they knew at the time — is worth saying aloud when the sprint went badly.
- Collect in silence, about specific moments — Ask about moments rather than feelings: "which handoff cost us the most time?" beats "what went badly?". Five silent minutes, everyone writing cards, no discussion.
- Group and name the themes — Cluster the cards and let the team name each cluster. Themes almost always collapse into three or four real issues even when there are thirty cards.
- Vote, then discuss only the top three — Give everyone three votes. Discuss the top three themes properly rather than skimming all of them — a retro that touches everything changes nothing.
- Write actions that are small enough to finish — "Improve communication" is not an action. "Anna posts the deploy checklist in the channel before each release" is. Two or three of those, each with a name and a sprint deadline.
Prompts that get past "it was fine"
Generic prompts get generic answers. These are the ones that reliably produce real cards:
- Which moment did you feel most blocked, and who could have unblocked you?
- Where did we spend time that produced nothing we kept?
- Which handoff between people or teams cost us the most?
- What did we decide last retro that we actually did?
- What would have made this sprint one day shorter?
Rotate the format, not every sprint
Start/Stop/Continue, Mad/Sad/Glad, 4Ls and sailboat all work; the format matters far less than the prompts and the follow-through. Change format when the team is visibly bored of the current one, roughly every five or six sprints, not every time.
When the retro is a blame session
If discussion turns to a person, restate the question as a system question: not "why did you miss it" but "what would have caught this before release?". If it keeps happening, switch to anonymous cards for a few sprints.
60-minute retrospective agenda
| Time | Phase |
|---|---|
| 0–10 min | Review last retro's actions |
| 10–15 min | Silent card writing |
| 15–25 min | Group and name themes |
| 25–30 min | Vote |
| 30–50 min | Discuss the top three |
| 50–60 min | Agree 2–3 actions with owners |
Frequently asked questions
How long should a sprint retrospective be?
About 60 minutes for a two-week sprint, and 90 for a month-long one.
Who should attend a retrospective?
The delivery team that did the work — adding managers or stakeholders changes what people are willing to say.
How many actions should come out of a retrospective?
Two or three, each small enough to finish inside the next sprint and each with a named owner.
What do you do when a retrospective has nothing to discuss?
Ask about a specific moment in the sprint instead of the sprint as a whole — silence usually means the question was too broad.