Team Retrospective Template
Retros are where teams get better — when they're run well. Most aren't. Same feedback every sprint, no action taken, everyone going through the motions. This template breaks that cycle.
The problem with "what went well, what didn't"
It's tired. Same prompts. Same answers. Nobody's being honest because nobody sees the feedback change anything.
This template uses varied frameworks and prompts to surface new insights. And it tracks action items so last retro's commitments don't just disappear.
Retro flow
- Review last retro's actions — accountability first
- Set the stage — ground rules, psychological safety
- Data gathering — what happened? Facts before opinions
- Generate insights — why did things go that way?
- Decide what to do — specific, assigned action items
- Close — acknowledge, appreciate, commit
Multiple frameworks included
Rotate these to keep retros fresh:
- Start / Stop / Continue — simple and direct
- 4Ls — Liked, Learned, Lacked, Longed For
- Sailboat — Wind (helps), Anchors (drags), Rocks (risks)
- Mad / Sad / Glad — emotional check-in
The action items are the point
A retro without action items is just a venting session. This template ends with specific commitments, owners, and deadlines. And starts the next retro by reviewing them.
Ready to Build Your Presentation?
Choose from 17 professionally designed templates. Fill in your content, download, and present.
Plan your retro →Frequently Asked Questions
How long should a retro be?
60-90 minutes for a 2-week sprint. Shorter for shorter cycles. Don't rush — deep insights need time to surface.
Who should facilitate?
Rotate. Don't let the same person (usually the Scrum Master) run every one. Fresh facilitation brings fresh dynamics.
What if people don't speak up?
Silent brainstorming before discussion. Anonymous input. Smaller breakout groups. Explicit permission that criticism is welcome. Safety takes time to build.
How do I keep retros from feeling repetitive?
Change the framework. Focus on specific topics instead of general "how was the sprint." And actually implement action items — nothing kills engagement like ignored feedback.