How to run a sprint retro that actually produces change.
Short answer
A good sprint retrospective runs 30–60 minutes at the end of each sprint. Use a structured format — Start/Stop/Continue, 4Ls, or Mad/Sad/Glad — give the team 5 minutes of silent sticky-note writing, then group, discuss, and commit to 1–3 action items with named owners. The output is a short list of concrete changes, not a vague conversation.
Sprint retrospectives fail when they become complaint sessions with no follow-through. The format that consistently works has five phases.
1. Set the stage (5 min). Open with a one-word check-in or an anonymous mood score on a scale of 1–5. This gets people talking before the harder conversation. Reiterate the Prime Directive: everyone acted with the best intentions given what they knew.
2. Silent writing (5–8 min). Everyone writes sticky notes independently — one idea per note — before anyone speaks. This prevents loudest-voice bias. Use a timer. Digital tools like FigJam or a real whiteboard both work; a physical board gets more engagement in the same room.
3. Group and read out (10–15 min). A facilitator clusters duplicate or similar notes. Each contributor reads their own stickies aloud; no discussion yet. You're mapping the landscape, not solving it.
4. Dot-vote and discuss (10–15 min). Each person gets 3–5 votes to place on the most important items. The top 2–3 clusters get the remaining time for discussion. Ask "Why does this keep coming up?" and "What would have to change for this not to recur?"
5. Commit to action items (5–10 min). Write down 1–3 specific, owner-assigned action items with a deadline. "We should communicate better" is not an action item. "Maya adds a 10-min sync to Monday standup, starting next week" is.
Format options: Start/Stop/Continue is the easiest on-ramp. 4Ls (Liked, Learned, Lacked, Longed For) is better for teams that need richer language. Mad/Sad/Glad adds emotional vocabulary — useful after a rough sprint. DAKI (Drop/Add/Keep/Improve) is preferred by engineering-heavy teams that find emotional framing awkward.
Timing: 2-week sprints warrant 45–60 minutes. 1-week sprints do fine in 30 minutes. Never run longer than 90 minutes; fatigue kills honesty.
Common failure modes: No action items, or action items with no owner. Skipping the retro when the sprint was rough (that's exactly when it's most valuable). The same 3 people talking while others watch.
After the session, BoardSnap AI reads the whiteboard — clusters, votes, action items — and produces a clean summary with a tri-state action list (open / in-progress / done) so nothing from the board gets lost before the next sprint.
Frequently asked
How long should a sprint retro be?
30–60 minutes for most 2-week sprints. A 1-week sprint can do it in 30 minutes. Never go over 90 minutes — past that point, the conversation stops being honest.
Who facilitates the sprint retro?
The Scrum Master typically facilitates, but the role can rotate. The facilitator should not dominate discussion — their job is to keep time, group notes, and ensure every voice is heard.
What's the best retro format for a new team?
Start/Stop/Continue. It's the lowest friction format and produces clear, actionable categories immediately. Switch to Mad/Sad/Glad or 4Ls once the team is comfortable being honest.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.