A retro is only useful to the extent that the next sprint runs differently. Most retros generate feelings and no changes.
The four sections every retro needs
- Themes, not quotes. Group 12 similar sticky notes into 1 theme with a count. It changes the debate.
- Decisions separate from actions. "We're going to try async standups on Tuesdays" is a decision. "Write the async standup doc" is an action.
- Every action has an owner and a due date. No owner = no action.
- Not changing. The hardest section to write and the most important. It stops the same complaint returning next sprint.
The recurring flag
If a theme appeared in the last retro too, name it. Two sprints in a row = escalate. Three = the team has a systemic issue that a single action item won't fix.
Length discipline
45 minutes for a 2-week sprint retro. Anything longer and the second half is theater.
Draft yours with the Sprint Retro Facilitator.