In 30 seconds
- Inspect people, process, tools and the Definition of Done.
- End with a few concrete actions, not a long wish list.
- Timeboxed to 3 hours for a one-month sprint, less for shorter ones.
Try it
A five-step structure
- Set the stage: make it safe to speak openly.
- Gather data: what happened this sprint?
- Generate insights: why did it happen?
- Decide what to do: pick one or two actions.
- Close: thank people, check the retro itself.
This shape comes from Esther Derby and Diana Larsen's book Agile Retrospectives.
Simple formats
- Start / Stop / Continue
- Went well / Didn't / Try next
- Mad / Sad / Glad for emotional temperature
- Sailboat: wind (helps), anchors (holds back), rocks (risks)
Rotate formats every few sprints to keep it fresh.
Making it stick
Add the chosen actions to the Sprint Backlog with an owner, and open the next retro by checking them. A retro that produces the same complaints every time is a sign actions aren't being followed through.
Myth vs reality
Myth · Retros are for complaining.
Reality · They're for deciding what to change.
Myth · Managers should attend to hear issues.
Reality · Only the Scrum team attends; safety depends on it.
Myth · Skip it when things go well.
Reality · Good sprints have lessons too, and the habit is the point.
The AI angle
AI can help group themes and surface data trends for a retrospective. Be careful about recording retros; people speak less freely when everything is analysed.
FAQ
Who facilitates?
Often the Scrum Master, but anyone on the team can.
How many actions should we pick?
One to three. More rarely gets done.
How is it different from the Sprint Review?
The Review inspects the product; the Retrospective inspects how the team works.