What went well
Wins, moments of flow, decisions that paid off, collaboration that clicked. This column runs first — anchoring the team in genuine positives before they open the hard conversations.
Free template
Free sprint retro template — whiteboard-ready.
Run an honest sprint retrospective on a real whiteboard. Snap it when you're done — BoardSnap turns every sticky into a structured action plan in seconds.
Download on the
App Store
Free to start. Pro from $9.99/mo or $69.99/yr.
When to run this
Run a sprint retro at the end of every sprint — typically the last afternoon of a two-week cycle. Don't skip it when the sprint went badly; those are the sessions that produce the most durable improvements.
The retro is the one meeting where the team owns the process. A physical whiteboard, markers in hand, beats a shared digital canvas for raw honesty. People write differently when they hold the marker themselves.
The structure
What didn't go well
Blockers, rework, missed estimates, unclear specs, tech debt that bit you. Write one issue per sticky. No names — focus on the system, not the person.
What confused us
Ambiguities, unclear requirements, process steps nobody understood, external dependencies that were opaque. Distinct from 'didn't go well' — these are knowledge gaps, not failures.
Action items
Specific, owned, time-bounded commitments that come out of the session. Each item gets a name and a sprint. This column is the only output that matters — everything else is context.
How to run it
- Set the stage (5 min)
Restate the sprint goal and the actual outcome in one sentence each. Remind the team that the retro is a blame-free space — you're fixing the system, not auditing individuals.
- Silent write (10 min)
Everyone writes stickies independently — one idea per note — and places them in the first three columns. Silence forces individual thinking before group dynamics kick in.
- Cluster and read-out (10 min)
The facilitator groups related stickies and each author reads theirs aloud. No debate yet — just shared understanding. Dot-vote to surface the themes worth discussing.
- Discuss top themes (15 min)
Work through the highest-voted clusters. Ask 'why did this happen?' at least twice before jumping to solutions. The first answer is usually a symptom.
- Define action items (10 min)
Turn each insight into a concrete action: verb + object + owner + deadline. If it can't be done in the next sprint, break it down or park it in the backlog.
- Snap and ship
Before you erase the board, snap it with BoardSnap. The AI reads every sticky, clusters the themes, and outputs a structured summary with tri-state action items — ready to paste into Jira, Linear, or Notion.
Why sprint retros on a whiteboard + BoardSnap is better than digital
Digital retro tools like Miro and FigJam feel frictionless until you notice the drop in candor. Typing on a shared screen in front of your manager is different from writing on a sticky note and slapping it on a column. The physical act of writing — and the temporary nature of a board — lowers the social cost of honesty.
The problem with physical boards has always been capture: someone takes a blurry photo, emails it around, and the action items die in a thread. BoardSnap closes that gap. Snap the board the moment the session ends and BoardSnap AI reads every sticky, groups the themes, and hands back a clean action plan with open/in-progress/done states — synced to whatever tool your team actually uses.
Frequently asked
How long should a sprint retro take?
30–60 minutes for most teams. Two-week sprints typically warrant a full hour. Shorter sprints can get away with 30–45 minutes. If your retros regularly run over, it's usually a sign that action items aren't being captured between sessions — problems compound and the list gets long.
What's the right number of action items per retro?
Three or fewer. Teams that leave with seven action items implement zero. Pick the highest-leverage change, assign it to one person, and actually do it. A retro with one completed action item is worth more than five with none.
Who should facilitate the sprint retro?
The Scrum Master traditionally facilitates, but rotating the role across team members keeps it fresh and builds facilitation skills. The facilitator shouldn't be the person with the most authority in the room — it suppresses input from quieter voices.
Can I use this template for a remote team?
Yes — print it, draw it on your local whiteboard, or open a digital canvas for the writing phase. For co-located teams, a physical whiteboard genuinely works better. For fully remote teams, a shared digital canvas is the practical choice. Either way, snap the result with BoardSnap to generate the action plan.
How do I stop the retro from becoming a complaint session?
Two rules help: give equal time to 'what went well' before opening the hard columns, and require that every problem raised ends in a proposed action. 'The deploys are slow' becomes 'we add a deploy-time alert to the next sprint.' Constraints produce solutions.
Related templates
Daily standup template
Keep the team aligned between sprints with a tight 15-minute standup format.
Sprint planning template
Plan the next sprint immediately after the retro — velocity data is fresh.
4Ls retro template
An alternative retro format: Liked, Learned, Lacked, Longed for.
Start / stop / continue retro
A three-column retro format focused on behavioral change.
Run your next sprint retro and BoardSnap will summarize it.
No exporting, no transcription. Snap the board, get the action plan.
Free · 1 project, 30 boards
Pro $9.99/mo · everything unlimited
Pro $69.99/yr · save 42%