Most scrum teams run the same retrospective every sprint: what went well, what didn't, what to change. Then they wonder why nothing actually changes. The right scrum retrospective template doesn't just collect feedback — it forces teams to confront uncomfortable truths, surface real blockers, and ship measurable improvements by the next sprint. According to the State of Agile report, the majority of practitioners say their retros have lost their edge, and the 16th State of Scrum data shows action items go unimplemented in nearly half of teams. This guide gives you five battle-tested scrum retrospective templates that drive real change, with facilitation scripts, timing guides, and notes on how AI is rewiring retros in 2026.
What is a scrum retrospective template?
A scrum retrospective template is a structured format that guides a team's reflection at the end of each sprint, defining the prompts, columns, and discussion flow used to surface what worked, what didn't, and what to improve. Templates replace open-ended discussion with focused inquiry, which keeps retros short, balanced, and outcome-driven — and produces action items the team will actually ship.
Why the default "what went well / what didn't" template fails
The classic two-column template works for the first three sprints. By sprint four, it becomes muscle memory. People copy items from the last retro. Action items pile up unowned. The retro stops being a learning ceremony and starts being a 45-minute formality on everyone's calendar.
The fix isn't more discipline. It's a better template — one that matches your team's current pain point. The five formats below are the ones experienced agile coaches reach for when retros go stale.
The 5 scrum retrospective templates that actually drive change
Each template here includes who it's best for, a facilitation script with timing, and the moment the format earns its keep. Pick one based on where your team is right now, not where it was six months ago.
1. The sailboat retrospective
Best for: teams that feel stuck and need to visualize what's pushing them forward versus holding them back.
The sailboat template uses a simple metaphor: your team is a boat sailing toward a goal (the island). Wind in the sails represents what's pushing you forward. Anchors represent what's slowing you down. Rocks ahead represent risks. The sun represents shared values that keep the team aligned.
Facilitation script (60 minutes):
Set the scene (5 min). Draw the sailboat, island, anchors, rocks, wind, and sun on the board. Define the island as the team's current goal — the next release, a quarterly OKR, or a product milestone.
Silent ideation (10 min). Each person adds sticky notes to each zone independently.
Group and theme (10 min). Cluster similar items together.
Discuss the heaviest anchors (15 min). The team picks the top two anchors to dig into.
Identify rocks ahead (10 min). Risk-mitigation conversation.
Commit to actions (10 min). Two SMART action items maximum, with named owners.
The sailboat works because the metaphor reframes complaints as systemic obstacles rather than personal grievances. People will name an anchor they wouldn't name a "problem."
2. The 4Ls retrospective (Liked, Learned, Lacked, Longed For)
Best for: teams reflecting on a longer cycle — a release, a quarter, or a project — when you need both learning and forward-looking signal.
The 4Ls splits reflection into four buckets: what the team Liked about the cycle, what they Learned, what they Lacked (resources, information, support), and what they Longed For (capabilities or conditions that would have made the work easier).
Facilitation script (60–75 minutes):
Frame the cycle being reviewed (5 min).
Silent brainstorm in each L (15 min).
Read-aloud round-robin (15 min). Each person shares one item per L.
Dot-vote the top two items in Lacked and Longed For (5 min).
Discuss top items, root-cause each (15 min).
Convert insights into experiments for next cycle (10 min).
The Lacked and Longed For columns are where the gold lives. They expose missing organizational scaffolding — onboarding documentation, decision frameworks, AI tooling, clear ownership — that a generic "what didn't go well" prompt rarely surfaces.
3. The starfish retrospective
Best for: mature teams ready for nuance beyond binary keep-and-stop thinking.
The starfish has five arms: Start, Stop, Continue, More of, Less of. The More of and Less of categories are the unlock — they let teams adjust intensity without abolishing practices that mostly work.
Facilitation script (50 minutes):
Recap the sprint (3 min).
Silent generation in all five arms (12 min).
Cluster duplicates (5 min).
Vote on the top item per arm (5 min).
Discuss votes (15 min).
Pick two actions with owners and acceptance criteria (10 min).
A team that does code review well but spends too long on it doesn't need to "stop" — they need "less of." The starfish gives them that vocabulary, which is exactly why it produces sharper actions than start/stop/continue.
4. The timeline retrospective
Best for: sprints that felt chaotic, projects with multiple distinct phases, or teams where memory of the sprint feels patchy.
A timeline retrospective rebuilds the sprint chronologically. Draw a horizontal line. Mark sprint start on the left, sprint end on the right. The team places sticky notes on the timeline at the moment events happened — a deployment, a stakeholder request, a system outage, a breakthrough — each tagged with a happiness emoji.
Facilitation script (75 minutes):
Draw the timeline with key dates marked (5 min).
Each person adds events they remember, with an emotion marker (15 min).
Read the timeline left to right, with brief commentary (15 min).
Identify two or three turning points where the sprint shifted, for better or worse (15 min).
Root-cause the negative turning points (15 min).
Commit to two actions (10 min).
The timeline retro is the format to use when the team says, "I have no idea what happened this sprint." It surfaces patterns — like every sprint having a chaotic Wednesday after stakeholder review — that aggregate retros miss entirely.
5. The mad / sad / glad retrospective
Best for: teams under stress, after a bad sprint, or when interpersonal friction is showing up in delivery metrics.
Mad / Sad / Glad sounds simplistic. It isn't. By forcing emotional labels, it surfaces issues that "what went wrong" never reaches: burnout, frustration with stakeholders, friction with another team, or grief over a deprioritized feature.
Facilitation script (45 minutes):
Establish psychological safety. Remind the team this is a no-blame space (3 min).
Silent generation across the three columns (10 min).
Read out loud, no debate (10 min).
Cluster (5 min).
Discuss patterns — what's making people mad or sad systemically? (12 min).
Decide on one structural change to test next sprint (5 min).
Use this format sparingly. It's the right tool for a hard moment, not a standing ceremony.
How to choose the right scrum retrospective template
The best scrum retrospective template depends on three variables: team maturity, sprint context, and the type of insight you need. The matching matters more than the format itself.
Quick selection guide:
New team, first 5 sprints: start, stop, continue or what went well / what didn't. Keep it simple while the team learns the ceremony.
Established team, normal sprint: starfish or sailboat. Push beyond binary thinking.
End of release or quarter: 4Ls. Wider lens, longer reflection.
Sprint felt chaotic: timeline. Rebuild memory.
Team morale is low: mad / sad / glad. Make space for what's actually being felt.
Team is gaming the format: rotate. Any template overused becomes wallpaper.
A senior agile coach should rotate templates every 3–5 sprints, even when nothing is broken. Novelty re-engages reflection muscles. Constant rotation, on the other hand, prevents the team from going deeper on a recurring theme — so don't rotate every sprint either.
How AI is changing scrum retrospectives in 2026
This is where most retro guides go quiet. They shouldn't. AI is rewiring how teams prepare for, run, and follow up on retrospectives — and ignoring it leaves real performance on the table.
AI-generated pre-retro insights
Modern AI retrospective tools — Parabol, Retrium, TeamRetro, Power Retro for Jira, Miro AI, Echometer, and a wave of newer entrants — ingest sprint data from Jira, GitHub, deployment logs, Slack channels, and calendar load, then generate a draft retro board before the meeting starts. The team walks in with sticky notes already populated by data: "Cycle time on Story X jumped from 2 days to 7 days," "PR review wait time averaged 18 hours, up from 6," "Three critical incidents during deploy windows."
This collapses the silent-ideation phase from 15 minutes to 5, and grounds the discussion in evidence rather than recall bias.
AI clustering and theme detection
After the team adds sticky notes, AI clusters related items and proposes themes — surfacing patterns humans miss when 80 stickies cover a Miro board. For distributed teams, this is the difference between a coherent retro and an overwhelmed facilitator.
Action-item tracking across sprints
The biggest retro failure mode is action items that vanish. AI tools now carry action items forward automatically, flag repeat issues across multiple retros, and prompt the team when a recurring theme has been raised three sprints in a row without resolution. That's the moment to escalate to leadership instead of debating the same anchor again.
What AI doesn't replace
AI doesn't replace the facilitator's judgment about psychological safety, team dynamics, or the moment to push deeper on an uncomfortable topic. The DORA 2025 report makes this explicit: AI accelerates throughput and instability simultaneously. Retros are where humans interpret that signal. Use AI to prepare; use humans to decide.
This is exactly where FixAgile, an Agile training and implementation framework designed for the age of AI, focuses its scrum master and coach training — teaching practitioners to combine AI-generated sprint analytics with the human judgment that turns data into decisions.
Common antipatterns that kill retrospectives
Even the best scrum retrospective template fails if the practice around it is broken. Watch for these patterns and address them directly.
The action-item graveyard. Teams generate three action items every retro, none get done, no one follows up. Fix: cap action items at two, name an owner, and schedule a check-in during the next sprint planning.
The same-five-people-talking retro. Quiet team members never speak. Fix: silent ideation first, then round-robin reading, then open discussion. Templates with parallel input (sailboat, 4Ls, starfish) help structurally.
The retro that becomes a status meeting. People list what they did, not what they learned. Fix: bound the prompts. "What slowed you down?" not "What did you work on?"
The sprint-blame retro. Discussion becomes an attack on a specific person, role, or team. Fix: the facilitator reframes specifics as systemic. "It sounds like our handoff process to QA needs structure" instead of "Sarah missed three stories."
The skipped retro. Teams cancel retros when sprints overrun. This is the worst possible signal — you're least reflective when you most need reflection. Fix: shorten the retro to 30 minutes if needed, but never skip it.
How to write retrospective action items that actually ship
The output of a retrospective is one thing: action items that change behavior next sprint. Strong action items share four traits.
They're specific. Not "improve testing." Replace with "Add a 30-minute test-design step to refinement, owned by the QA on the team."
They have a single owner. "The team" is not an owner. One name.
They have a sprint-level deadline. "By end of next sprint" beats "soon."
They have a measurable outcome. "Reduce PR review wait time below 8 hours" beats "review PRs faster."
A retro that ends with three vague action items has produced nothing. A retro that ends with two SMART actions has produced more than the majority of retros in the industry.
Frequently asked questions about scrum retrospective templates
How long should a scrum retrospective be?
For a two-week sprint, a retrospective should run 60 to 90 minutes. The Scrum Guide recommends a maximum of three hours for a one-month sprint. Anything shorter than 45 minutes risks skipping the action-item discussion, which is where retros earn their value.
Should every sprint use a different retrospective template?
No. Rotate templates every 3–5 sprints. Constant rotation prevents the team from going deeper on a recurring theme; repetition without variation produces fatigue. The right cadence is enough rotation to stay fresh, enough repetition to track progress on persistent issues.
Can AI run a retrospective on its own?
Not yet — and probably not ever. AI can prepare data, surface themes, cluster input, and track action items. It cannot read the room when an engineer hints at burnout, decide when to push back on a complaint, or hold space for difficult conversations. Use AI to handle data; use a human facilitator to handle people.
What's the best scrum retrospective template for remote teams?
Sailboat and starfish work especially well remote, because the visual metaphor anchors distributed attention. Pair them with a tool like Miro, Parabol, Retrium, or TeamRetro for shared collaboration and async pre-input from team members in different time zones.
Is the retrospective still relevant when half the work is AI-generated?
More relevant, not less. When AI accelerates output, organizational bottlenecks become the rate-limiting step. Retros are how teams find and remove those bottlenecks. Skipping retros in an AI-augmented team is the fastest way to ship more bugs faster.
Why retrospectives are the most important ceremony in modern Agile
Retrospectives are the only ceremony in Scrum where the process inspects itself. Every other ceremony delivers product value. The retro delivers process value.
That makes the retrospective the single most important lever for organizations modernizing Agile in the AI era. If your retros are stale, your transformation is stale. If your retros are surfacing real signal — the right anchors, the right blockers, the right calls for new structure — your team is actually adapting.
The hardest pattern in Agile right now is teams adopting AI tools for delivery while keeping their reflection practices stuck in 2018. The result: faster output, no smarter system, recurring fires. Modernized retros — supported by the right scrum retrospective template, an empowered facilitator, and AI-prepared sprint data — are how you close that gap.
Bring real change to your retrospectives
Pick a scrum retrospective template that matches your team's current pain point. Run it well. Generate two SMART action items. Track them to completion before the next retro. Rotate the template every few sprints. Use AI to prepare; use your facilitator to decide.
If your retros have stopped producing change — if the same anchors keep surfacing sprint after sprint, if action items disappear, or if your team has adopted AI tooling without adapting its agile practices — that's exactly what FixAgile's training programs are built to solve. Our hands-on coaching, scrum master tracks, and AI-readiness assessments help facilitators and engineering leaders rebuild reflection practices that drive real performance in the age of AI agents.
