How to run a sprint retrospective
The short answer
Run a retrospective in five parts: set a safe tone, gather what went well and what didn't, look for causes behind the patterns, agree one or two specific improvements with owners, and close by checking how the retro itself went. Start the next retro by reviewing those improvements.
Step by step
- 1
Set the stage
Remind everyone the aim is to improve how the team works, not to blame anyone.
- 2
Gather data
Collect what went well, what didn't and what was confusing, silently first so everyone contributes.
- 3
Find causes
Group similar points and ask why they happened.
- 4
Decide what to change
Pick one or two improvements, each with an owner.
- 5
Close and follow up
Review last retro's improvements at the start of the next one.
Common mistakes
- Choosing too many improvements to actually do.
- Skipping the follow-up on last time's actions.
- Using the same format every sprint until people disengage.
Acta keeps each retro's agreed changes as action items, so the next retro starts with what actually happened.
Try Acta free for 15 daysQuestions
How long should a sprint retrospective be?
Up to 45 minutes per week of sprint, so up to 90 minutes for a two-week sprint.
Who attends the retrospective?
The whole delivery team, including the product owner; managers usually join only if the team invites them.