📘 Facilitation guide
How to Run a Sprint Retrospective
A simple, repeatable five-phase structure any Scrum Master can use to turn a routine meeting into real improvement — plus a free online board to run it.
Step by step
- 1
Set the stage
Open with a quick check-in and remind everyone the retro is blameless. Psychological safety is the single biggest predictor of a useful retrospective.
- 2
Gather data
Have the team add cards about the sprint — what happened, how it felt. Use a template like Start/Stop/Keep to give structure.
- 3
Generate insight
Group similar cards, upvote what matters, and discuss the top themes. Ask “why” until you reach a root cause, not just a symptom.
- 4
Decide on actions
Agree on two or three concrete, owned action items. Fewer, finished actions beat a long list nobody touches.
- 5
Close the retro
Recap the actions, thank the team, and capture a quick pulse on the retro itself so you can improve the format too.
How long should a retrospective be?
A good rule is roughly 45 minutes per one-week sprint, scaling up modestly for longer sprints. The discipline matters more than the duration: a focused 30-minute retro that produces two real actions beats a sprawling 90-minute one that produces a wall of sticky notes and no change.
Common retrospective mistakes
The most common failure is no follow-through — actions are agreed and then forgotten. Start every retro by reviewing the last one's actions to close that loop. Other traps: letting the loudest person dominate (use silent upvoting), turning it into a status meeting, and skipping the retro entirely when things are busy — which is exactly when teams need it most.
Keep it blameless
Frame problems as system and process issues, not individual fault. People stop sharing the moment a retro feels like a performance review.
Rotate the format
Running the same template every sprint dulls engagement. Alternate between Start/Stop/Keep, Good/Bad/Improve, and Went Well/To Improve to keep eyes fresh.
Frequently asked questions
▸Who facilitates the retrospective?
Usually the Scrum Master, but rotating facilitation keeps it fresh and builds shared ownership of the team's process.
▸Should the manager attend?
Generally no, unless they're part of the delivery team. Their presence can suppress candour. If they join, agree on blameless ground rules first.
▸What if nothing went wrong?
Great sprints still teach you what to keep doing. Use the retro to capture what worked so you can deliberately repeat it.
▸How do we make actions stick?
Limit to two or three, give each an owner and a due sprint, and review them at the start of the next retro.
▸Can we run this remotely?
Yes. A shared online retro board lets distributed teams add cards, upvote, and export actions together in real time.
Related guides
Run a better retro this sprint
Open the free retro board, pick a template, and put this guide into practice.