Facilitating Sprint Retrospectives
Send this doc link 24 hours before the retro, then run the 45-minute session:
Sprint Retro - [Sprint #] - [Date]
Add anonymous input below before the meeting. One thought per line.
Meeting agenda (45 min total):
1. Silent read + clarify (5 min)
2. Group similar themes (5 min)
3. Discuss START (10 min)
4. Discuss STOP (10 min)
5. Discuss CONTINUE (5 min)
6. Pick action items + assign owners (10 min)
Progress:
- Create shared doc from template 24-48h before retro
- Send doc link + reminder to all 6 team members
- Nudge anyone who hasn't contributed 2h before meeting
- Open meeting, screen-share the doc
- Silent 5-min read of all entries
- Cluster duplicate/related entries together
- Timebox discussion per section, use a visible timer
- Narrow discussion to 2-3 action items max
- Assign exactly one owner per action item (no co-owners)
- Set a due date or "check-in at next retro" for each item
- Post summary (themes + action items + owners) in team channel same day
- Open next retro by reviewing previous action items' status
Step details
Pre-collection (async, anonymous)
- Use a doc, not a live poll — anonymity increases candor.
- Anonymous means no names on entries, but facilitator should still skim for anything urgent (blocker, conflict) before the meeting.
Grouping
- Merge near-duplicates ("standups too long" + "standups drag on") into one theme so discussion isn't repetitive.
Discussion
- Discuss themes, not individual quotes — keeps it about patterns, not people.
- If a topic threatens to blow the timebox, park it: "let's take this offline" + note it in the doc for next time.
Action items
- Cap at 2-3 items. More than that and nothing gets done.
- Every item gets exactly one named owner and one deadline (or explicit "revisit next retro").
- If no one volunteers, the facilitator assigns — don't let an item leave the room ownerless.
Close-out
- Summary posted the same day while it's fresh, even if brief.
- Next retro starts by asking each owner for a 1-line status update on their action item — this is what makes retros actually change behavior instead of becoming a recurring complaint session.
Example 1: Input: Anonymous doc has 4 STOP entries: "too many meetings," "meetings eating focus time," "no meeting-free blocks," "standup runs 20+ min." Output: Grouped into one theme: "Meeting load is too high." Discussion produces action item: "Trial a meeting-free block Tue/Thu afternoons for 2 sprints." Owner: Priya. Due: start next Monday, review at retro in 2 sprints.
Example 2: Input: START section has one entry: "start writing design docs before big features." CONTINUE section has 3 entries all praising the new PR review turnaround time. Output: START discussed (10 min), turns into action item "Draft a 1-page design doc template" — Owner: Marcus, due before next sprint planning. CONTINUE section discussed briefly (5 min), no action item needed — team agrees to keep current PR review practice, noted in summary as a "keep doing" win.
- Keep the doc link the same every week (same doc, new section per sprint, or a recurring template) so it becomes a habit.
- Rotate who "reads aloud" grouped themes if you want to reduce facilitator dominance.
- Track action items across retros in one running list — visibility on old items is what builds accountability.
- If the same STOP item appears 3 sprints running, escalate it — it's not being a retro topic, it's a real problem.
- Keep the CONTINUE section — teams skip celebrating what's working and morale suffers.
- Don't let discussion run long on STOP and steal time from action item assignment — protect the last 10 minutes fiercely.
- Don't assign co-owners "to be fair" — diffused ownership means nothing happens.
- Don't skip the async collection step even when the team is busy — live-only brainstorming in a 6-person team suppresses dissent, especially from junior members.
- Don't turn retro into a status meeting — sprint progress belongs in standup, not here.
- Don't let action items pile up unaddressed across multiple retros without acknowledgment — either close them, re-scope them, or explicitly drop them with a reason.