Sprint Retrospective Template: 5 Formats for Agile Teams That Actually Improve
The number one cause of "retro fatigue" is using the same format every sprint. Teams that rotate between formats report 35% more actionable outcomes because variety keeps reflection fresh. This page provides five distinct retrospective formats with guidance on when to use each one.
Five Retrospective Formats
Start / Stop / Continue
30 minBest for: New teams, straightforward sprintsSet the Stage
3 minQuick check-in. State the goal: identify what to change.
Silent Writing
5 minEveryone writes items for each column independently.
Share and Discuss
15 minGroup similar items. Discuss themes. Focus on the 'Start' column first as it generates action.
Vote and Commit
5 minDot vote on top 2 items per column. Assign owners to the top 'Start' and 'Stop' items.
Close
2 minRead back commitments. Schedule follow-up check.
4Ls: Liked / Learned / Lacked / Longed For
45 minBest for: Teams needing emotional nuance, mixed sprint outcomesSet the Stage
3 minExplain the 4L framework. Each category captures a different emotional dimension.
Silent Reflection
7 minWrite sticky notes for each L category. Minimum 2 per category.
Category Walk-Through
25 minGo through each L. Liked: what energized us. Learned: what surprised us. Lacked: what was missing. Longed For: what we wish we had.
Action Items
8 minFocus actions on 'Lacked' and 'Longed For' columns. These are the improvement opportunities.
Close
2 minSummarize actions. Check team morale.
Sailboat
45 minBest for: Visual teams, identifying risks alongside winsDraw the Metaphor
3 minDraw a sailboat on a whiteboard. Label: Wind (what propels us), Anchor (what holds us back), Rocks (risks ahead), Island (our goals).
Silent Reflection
7 minEveryone adds sticky notes to each section of the sailboat.
Discuss Each Section
25 minStart with Wind (positive energy). Then Anchors (impediments). Then Rocks (risks). Finally, confirm the Island (are our goals still right?).
Action Items
8 minTurn Anchors into removal tasks. Turn Rocks into mitigation plans.
Close
2 minTake a photo of the sailboat. Share with the team.
Mad / Sad / Glad
30 minBest for: Teams experiencing conflict or frustrationSet the Stage
3 minAcknowledge that emotions are valid data. Create a safe space for honest expression.
Silent Reflection
5 minWrite items that made you Mad, Sad, or Glad during the sprint.
Share and Discuss
15 minStart with Glad (build positive energy). Then Mad (address frustrations directly). Then Sad (explore disappointments with empathy).
Action Items
5 minFocus on resolving 'Mad' items. Acknowledge 'Sad' items even if they cannot be immediately fixed.
Close
2 minCheck in on team emotional state. Express appreciation.
Timeline
60 minBest for: Long sprints, post-incident reviews, complex projectsBuild the Timeline
5 minDraw a horizontal timeline covering the sprint period. Mark key events (deployments, incidents, milestones).
Individual Annotations
10 minEveryone adds their own events, emotions, and observations to the timeline. Use color coding: green (positive), red (negative), yellow (neutral).
Walk Through Chronologically
30 minGo through the timeline day by day or event by event. Identify patterns: where did things go well? Where did they break down? What caused the turning points?
Pattern Analysis
10 minIdentify systemic patterns (not just individual events). Look for recurring themes, bottlenecks, and communication gaps.
Action Items and Close
5 minAddress the systemic patterns, not just symptoms. Assign owners.
Format Selection Guide
| Situation | Recommended Format | Why |
|---|---|---|
| New team (first 3 sprints) | Start/Stop/Continue | Simple, no prior context needed |
| Good sprint, want to deepen | 4Ls | Captures nuance and learning |
| Team conflict or frustration | Mad/Sad/Glad | Validates emotions directly |
| Need to identify future risks | Sailboat | Visual, includes forward-looking risks |
| Post-incident or long sprint | Timeline | Chronological analysis of what happened |
| Retro fatigue setting in | Any format not used in last 3 retros | Variety resets engagement |
Retrospective Anti-Patterns
The zero-action retro
Fix: Every retro must produce at least 2 action items with owners and deadlines. If the team cannot identify actions, the facilitation needs to go deeper.
The scrum master monologue
Fix: The facilitator should talk less than 20% of the time. Use silent writing, round-robin sharing, and dot voting to give everyone equal voice.
The recurring theme
Fix: If the same issue appears in 3 consecutive retros, it needs a dedicated problem-solving session, not another retro mention. Escalate it.
The no-follow-through retro
Fix: Start every retro by reviewing action items from the previous retro. If action items are consistently not completed, address that as the first retro topic.
Filled-Out Example: Start/Stop/Continue
Team Phoenix / Sprint 14 Retrospective / March 14, 2026 / 7 participants / Facilitator: Jamie
Start
- Pair programming on complex features (6 votes)
- Pre-sprint technical design docs (5 votes)
- Weekly demo to stakeholders (3 votes)
Stop
- Changing sprint scope mid-sprint (7 votes)
- Skipping code review for 'urgent' fixes (4 votes)
- Meetings without agendas (3 votes)
Continue
- 15-min daily standups (unanimous)
- Automated testing on every PR (5 votes)
- Rotating facilitator role (4 votes)
Action items: (1) Alex to set up pair programming schedule by March 17. (2) PM to implement sprint scope lock policy starting Sprint 15. (3) Team lead to create code review checklist for emergency fixes.
Daily Standup Template
The daily complement to your sprint retrospective.
Action Plan Template
Track retro action items with structured owners and deadlines.
Frequently Asked Questions
How long should a retrospective be?
30 minutes for a 1-week sprint, 45 minutes for a 2-week sprint, and 60 minutes for longer sprints or complex projects. The Timeline format typically needs 60 minutes regardless of sprint length.
Should managers attend the retro?
It depends on the team's psychological safety. If team members self-censor when managers are present, have the manager skip the retro and receive a summary. If the team is mature and trusts the manager, their presence can help because they can commit to organizational changes.
How do you handle retro fatigue?
Rotate formats every sprint. If the team has done Start/Stop/Continue three times in a row, switch to Sailboat or 4Ls. Also vary the facilitator. If the retro still feels stale, try a completely different activity: a team walk, a virtual escape room that surfaces collaboration patterns, or a 'retro of retros' where you retrospect on your retrospective process.
What if the team has nothing to discuss?
Silence in a retro is a signal, not an absence of issues. Use anonymous submission (digital sticky notes) to lower the barrier. Ask specific prompts: 'What surprised you this sprint?' If the team genuinely had a smooth sprint, celebrate that and keep the retro to 15 minutes.