Delivery
Sprint Retrospective Template
A retro without action items is group therapy. This free sprint retrospective template pairs classic prompts with an action tracker so each retro produces concrete, owned improvements — the same structure Planquora gives your Scrum ceremonies.
What it is
A sprint retrospective is the ceremony where the team reflects on the sprint just finished and decides what to change. It's the engine of continuous improvement in Scrum.
The format is simple: look at what went well, what didn't, and what to try next — then commit to a small number of specific actions with owners. The discipline is in the follow-through.
When to use it
- At the end of every sprint, before planning the next one.
- After a rough release or incident, as a focused post-mortem.
- Whenever the team's process feels off and you want to fix it deliberately.
The template
Discussion prompts
- What went well
- Wins worth keeping and repeating
- What didn't go well
- Friction, blockers, misses — be specific and blameless
- What puzzled us
- Surprises or things we didn't understand
- What to try next
- Experiments and changes for next sprint
# 1, 2, 3… | Action item One specific, doable change | Owner Who will make it happen | Due By when — usually next sprint | Status Open / Done |
|---|---|---|---|---|
| 1 | Add a definition-of-done checklist to each story | Scrum Master | Next sprint | Open |
| 2 | Timebox standup to 15 minutes | Team | Immediately | Open |
| 3 | Spike unclear API integration before committing it | Tech lead | Sprint planning | Open |
Tips
- Keep it blameless. Retros surface problems only if people feel safe naming them.
- Limit yourself to 2–3 action items. Ten actions means zero get done.
- Review last retro's actions at the start of this one. Accountability is the whole point.
- Vary the format occasionally (start/stop/continue, mad/sad/glad) to keep it fresh.
Browse all free templates or read the Help Center.