guide · retrospective
How to run a retro meeting that actually changes something
A retrospective, or retro, is the meeting at the end of a sprint where the team looks at how it worked and picks something to improve. Done well, it is the cheapest way for a team to get better every two weeks.
Done badly, it is the same complaints every sprint and no change. Here is a structure that keeps it useful.
A 5-step retro agenda (about 60 minutes)
- Set the stage (5 min): restate the purpose, remind everyone the goal is to improve the system, not to blame people.
- Gather data (15 min): everyone writes notes in the format’s columns, for example Start / Stop / Continue.
- Generate insights (15 min): group similar notes, then dot-vote on the themes that matter most.
- Decide what to do (15 min): turn the top one or two themes into action items with an owner and a date.
- Close (5 min): read back the actions and ask what to change about the retro itself.
Retro formats to try
Start / Stop / Continue
What should we start doing, stop doing and keep doing? Simple, action-focused and the easiest format for a new team.
What went well / What to improve
Two columns, quick to run, and good for short sprints or a fast check-in.
Mad / Sad / Glad
Focuses on how the sprint felt. Useful after a stressful release or when morale is low.
4Ls: Liked, Learned, Lacked, Longed for
Balances positives with gaps and brings out learning, which suits the end of a project.
Sailboat
Wind (what pushed us forward), anchors (what slowed us), rocks (risks ahead) and the island (our goal). A visual format that works well with a whiteboard.
Make the action items stick
- Pick one or two actions, not ten. Small changes that happen beat big ones that do not.
- Give each action an owner and a due date, and put it on the sprint board.
- Start the next retro by checking last sprint’s actions.
Running a remote retro
- Use an online retro board everyone can write on at the same time, and share it with one link.
- Ask everyone to add notes silently first so the loudest voice does not set the agenda.
- Use dot-voting to choose what to discuss.
- Keep cameras optional and the timebox strict.
A free online retro board
The skillzunoscrum retro board creates a shared retro room in seconds with no sign-up. Share the link, collect Start / Stop / Continue cards in real time, dot-vote on what matters most and leave with clear action items.
Notes carry the writer’s name, which suits a team that already trusts each other. If your team needs anonymous feedback, collect it another way first.
Frequently asked questions
What is a retro meeting?
A sprint retrospective: a meeting at the end of each sprint where the team reviews how it worked and agrees on improvements for the next sprint.
How long should a sprint retrospective be?
Up to 3 hours for a one-month sprint and less for shorter sprints. About 60 to 90 minutes is typical for a two-week sprint.
Who attends the retrospective?
The scrum team: developers, the product owner and the scrum master, who usually facilitates.
What is the best retrospective format?
Start / Stop / Continue is the easiest to begin with. Rotate formats like Mad / Sad / Glad or the 4Ls every few sprints to keep retros fresh.