How to Run a Sprint Retrospective

Why retrospectives work — the evidence

Retrospectives aren't an agile ritual to be endured — the mechanisms behind them are some of the best-studied in organizational research.

The six phases, step by step

Whatever format you pick, a well-run retro moves through the same phases. Each one exists to protect the meeting from a specific failure mode.

1. 1

   Write in silence

   Everyone adds cards to the board at the same time, anonymously, with a timebox (5–10 minutes). Cards stay concealed while people write — nobody can see what anyone else wrote yet.

   Tip

   Resist the urge to chat during writing. Silence isn't awkward here, it's the point: simultaneous, independent writing is what stops the first opinion in the room from anchoring everyone else's.

   Avoid

   Letting people 'just discuss it live' instead of writing. The people who think out loud will dominate, and the quieter half of the team's honest input never makes it onto the board.

2. 2

   Vote with limited tokens

   Each person gets a small, fixed budget of voting tokens (3–5 works well) and places them on the cards they think deserve discussion. Scarcity is what makes the vote meaningful.

   Tip

   Configure fewer tokens than there are cards. If everyone can vote for everything, you've measured nothing — the constraint is what forces real prioritization.

   Avoid

   Unlimited +1s. A vote that costs nothing produces a board where everything is 'important', which is the same as nothing being important.

3. 3

   Discuss the top cards

   Walk through the highest-voted cards one by one, top vote-getter first. The facilitator steers which card the group is looking at; anyone can comment on any card.

   Tip

   Timebox each card (3–5 minutes) and do a quick 'keep going or move on?' check when time is up. The team's votes already told you what matters — trust them.

   Avoid

   Spending 25 minutes on the first card. The facilitator's main job in this phase is protecting time for card two and three.

4. 4

   Reveal and group themes

   Card authors are revealed, and the facilitator drags related cards together into named themes. Twelve scattered cards usually collapse into three or four real patterns.

   Tip

   Name themes after problems, not people — 'deploys are stressful', not 'the backend team is slow'. The theme name will outlive the meeting; make it something you can fix.

   Avoid

   Skipping grouping entirely. Ungrouped cards read as twelve disconnected complaints; grouped, they read as three problems with evidence.

5. 5

   Commit to action items

   Convert the discussion into specific action items with an owner and, ideally, a due date. This is the phase most retrospectives skip — and the reason most retrospectives feel pointless.

   Tip

   One to three actions, no more. A retro that produces eight actions produces zero completed actions. Small and owned beats ambitious and orphaned.

   Avoid

   Actions without owners. 'We should improve our testing' is a wish; 'Sarah spikes the flaky checkout test by Friday' is an action.

6. 6

   Close and measure

   Wrap up with a summary everyone can export, and a quick anonymous pulse — one tap on 'how was this sprint?' — so team health becomes a trend you can see over time, not a feeling.

   Tip

   Open your NEXT retro by reviewing this retro's action items. That thirty-second ritual is the single strongest signal that retro actions are real commitments.

   Avoid

   Ending without closing the loop. If actions vanish into a document nobody reopens, the team learns that speaking up changes nothing — the opposite of what a retro is for.

Common facilitation mistakes

Remote and async retrospectives

Frequently asked questions