Retrospective games and ideas: 11 formats for agile teams
A sprint retrospective is the meeting where a Scrum team looks at how the last sprint went and picks what to change in the next one. This page describes 11 retrospective formats, with the steps and the duration of each.
The 11 retrospective formats at a glance
| Format | Best for | Example duration |
|---|---|---|
| ESVP check-in | Opening: finding out who wants to be in the room | 10 min |
| Start/Stop/Continue | A first retrospective, or a team short on time | 45 min |
| Mad/Sad/Glad | A sprint that left people frustrated or tired | 45 to 60 min |
| 4Ls | The end of a release or a project | 60 min |
| Sailboat (Speedboat) | A team with a goal and risks ahead | 60 min |
| Starfish | A team that has worn out Start/Stop/Continue | 60 min |
| Timeline | A long sprint, a release or an incident | 60 to 90 min |
| 5 Whys | One problem that keeps coming back | 20 to 30 min |
| Lean Coffee | Unrelated topics that nobody has sorted | 60 min |
| Dot voting | Choosing which topics become actions | 5 min |
| ROTI closing | Closing: scoring the meeting itself | 5 min |
The durations are examples for a team of 5 to 8 people, not rules. ESVP, dot voting and ROTI are short activities that open, narrow down or close a retrospective built on one of the other eight formats.
What is a sprint retrospective?
The 2020 Scrum Guide gives the sprint retrospective one purpose: to plan ways to increase quality and effectiveness. It is the last event of the sprint, after the sprint review.
- Who attends: the Scrum Team, meaning the developers, the product owner and the scrum master.
- What is inspected: individuals, interactions, processes, tools and the Definition of Done.
- How long: a maximum of three hours for a one-month sprint, and usually shorter for shorter sprints. As an example, a team on two-week sprints can book 60 to 90 minutes; the guide gives no figure for that sprint length.
- What comes out: the most helpful changes the team identified. The guide says they are addressed as soon as possible and may be added to the Sprint Backlog of the next sprint.
The five phases of a retrospective
Esther Derby and Diana Larsen described this structure in "Agile Retrospectives: Making Good Teams Great", published in 2006.
- Set the stage: state the goal and the timebox, and get every person to speak once. ESVP belongs here.
- Gather data: collect what happened during the sprint, facts and feelings. Start/Stop/Continue, Mad/Sad/Glad, 4Ls, Sailboat, Starfish and Timeline belong here.
- Generate insights: look for the causes behind the data. 5 Whys belongs here.
- Decide what to do: pick one or two actions, each with an owner. Dot voting belongs here.
- Close the retrospective: record the actions and score the meeting. ROTI belongs here.
Lean Coffee replaces phases 2 and 3: the team builds its agenda and discusses it in the same meeting.
The 11 formats, step by step
ESVP check-in
Use it to open a retrospective when you do not know how willing people are to take part. Allow about 10 minutes. Derby and Larsen describe it in their book as an anonymous poll.
- Write the four roles on a board. An Explorer wants to discover new ideas. A Shopper will be happy to leave with one useful idea. A Vacationer is glad to be away from daily work. A Prisoner feels forced to attend.
- Each person writes one letter, E, S, V or P, on a folded slip of paper, without a name.
- Count the slips and draw the four totals as bars on the board.
- Tear up the slips in front of the group, so nobody can match handwriting to a vote.
- Ask the group what the totals mean for the next hour.
Start/Stop/Continue
Use it for a first retrospective, or when the team has 45 minutes.
- Draw three columns: Start (what the team does not do yet), Stop (what costs more than it brings) and Continue (what works).
- Everyone writes notes in silence for 5 minutes, one idea per note.
- Each person reads their notes aloud and places them in a column.
- Group the notes that say the same thing.
- Vote with dots, then turn the top one or two groups into actions.
Mad/Sad/Glad
Use it after a sprint with a missed goal, an incident or a conflict, when people need to say how they feel before they discuss process. Plan 45 to 60 minutes. The activity is described in Derby and Larsen's book.
- Draw three columns: Mad (what made me angry), Sad (what disappointed me) and Glad (what made me happy).
- Everyone writes notes in silence for 5 to 10 minutes.
- Place the notes, then group them by topic and give each group a name.
- Discuss the largest groups, starting with Mad.
- Pick one action for the group that received the most notes.
4Ls: Liked, Learned, Lacked, Longed for
Use it at the end of a release or a project, when the question is what the team learned as much as what went wrong. Plan 60 minutes. Mary Gorman and Ellen Gottesdiener described the format in June 2010.
- Draw four areas: Liked, Learned, Lacked and Longed for.
- Everyone writes notes in silence for 10 minutes. "Lacked" is something that was missing, such as a test environment. "Longed for" is something the person wished for, such as a design review before coding.
- Split into four subgroups, one per area. Each subgroup clusters the notes of its area and reports the themes it found.
- The whole team picks the actions from the Lacked and Longed for themes.
Sailboat (Speedboat)
Use it when the team has a clear goal, such as a release date, and wants to list what helps and what threatens it. Plan 60 minutes. The format also goes by Speedboat, the name of a game Luke Hohmann published in "Innovation Games" in 2006, in which customers identify their biggest pain points with a product.
- Draw a boat, an island, the wind, an anchor and rocks.
- Write the goal on the island.
- Everyone writes notes for 10 minutes: wind for what pushes the team forward, anchor for what slows it down, rocks for the risks ahead.
- Place the notes on the drawing and group them.
- Vote on the anchors and the rocks.
- Write one action for the heaviest anchor and one for the nearest rock.
Starfish
Use it when Start/Stop/Continue has become routine: two extra branches let people ask for more or less of a practice without dropping it. Plan 60 minutes. Patrick Kua described the Starfish on his blog in March 2006.
- Draw five branches from one point: Keep doing, Less of, More of, Stop doing, Start doing.
- Everyone writes notes in silence for 10 minutes.
- Go through the branches one at a time and place the notes.
- Vote with dots across the whole board.
- Turn the top two notes into actions with an owner.
Timeline
Use it after a long sprint, a release or an incident, when people remember different parts of the story. Plan 60 to 90 minutes. The activity is described in Derby and Larsen's book.
- Draw a horizontal line from the first day to the last day of the period.
- Everyone writes the events they remember, one per note: a deployment, an outage, a person joining, a change of scope.
- Place the notes on the line in order.
- Each person adds a green dot on the events they that felt good to them and a red dot on the ones that felt bad.
- Read the line from left to right and stop where the red dots gather.
- Pick the actions from those points.
5 Whys
Use it on one problem that came back in several sprints. Allow 20 to 30 minutes, after the team has gathered data. Taiichi Ohno describes the technique in "Toyota Production System", translated into English in 1988.
- Write the problem as a fact: "The release shipped two days late."
- Ask why and write the answer: "The regression tests failed on Thursday."
- Ask why about that answer: "A database migration was merged on Wednesday evening without running them."
- Repeat until an answer names something the team can change. Five is a guide: some chains end at three, some at seven.
- Write the action against the last answer, here "the pipeline blocks a merge when the regression tests have not run".
Lean Coffee
Use it when people arrive with unrelated topics. Plan 60 minutes. Jim Benson and Jeremy Lightsmith started Lean Coffee in Seattle in 2009.
- Draw three columns: To discuss, Discussing, Discussed.
- Everyone writes topics for 5 minutes, one per note, and presents each in one sentence.
- Each person gets two votes. Order the To discuss column by number of votes.
- Move the first topic to Discussing and start a timer, for example 7 minutes.
- When the timer rings, everyone shows a thumb: up to add time, for example 3 minutes, down to move to the next topic.
- Note any action before moving the topic to Discussed.
- Stop 5 minutes before the end and read the actions aloud.
Dot voting
Use it when the board holds more topics than the team can discuss. Allow about 5 minutes.
- Give each person the same number of dots, for example three.
- Everyone places their dots on the notes or groups they want to act on. Putting two dots on the same note is allowed.
- Count the dots and keep the top one or two items.
On a wall, the last voters see the first dots. Some online whiteboards have a voting mode that hides the votes until the count.
ROTI closing
ROTI stands for return on time invested. Use it in the last 5 minutes to score the retrospective itself. Derby and Larsen describe the activity in their book, with a scale from 0 to 4.
- Explain the scale: 0 means "no benefit for the time invested", 2 means "a benefit equal to the time invested", 4 means "a benefit greater than the time invested".
- Everyone shows a number of fingers at the same moment, from a closed fist for 0 to four fingers.
- Ask the people who showed 0 or 1 what they wanted and did not get.
- Write the average next to the date and compare it with the previous retrospectives.
Retrospective ideas for remote teams
- Use an online whiteboard with one column per category, prepared before the meeting.
- Have everyone write for 5 minutes with the notes hidden, then reveal them all at once: the first note read does not steer the others.
- Keep the meeting to 60 minutes, and add a 5-minute break if it goes past 90.
- Name a facilitator who is not the note-taker.
- For a team spread across time zones, open the board 24 hours ahead for writing and keep the call for grouping, voting and deciding.
- Replace the ROTI fingers with a number typed in the chat and sent on a countdown.
Common retrospective mistakes
- Leaving without an action. A retrospective that ends on a list of complaints changes nothing in the next sprint. Each action needs an owner and a date.
- Running the same format every time. When the same notes come back sprint after sprint, change the format: another one asks the team other questions.
- Inviting a manager whose presence silences people. The Scrum Guide lists the Scrum Team as the participants. If the person who writes performance reviews is in the room, problems go unsaid.
- Taking on too many actions. A team that leaves with eight actions rarely finishes them. Keep one or two, and start the next retrospective by checking them.
An action that needs development work goes into the next sprint planning, where the team can size it with planning poker.
FAQ
What are the 5 stages of a retrospective?
Set the stage, gather data, generate insights, decide what to do, close the retrospective. Esther Derby and Diana Larsen described these five phases in "Agile Retrospectives: Making Good Teams Great", published in 2006.
How long should a sprint retrospective last?
The 2020 Scrum Guide sets a maximum of three hours for a one-month sprint and says the event is usually shorter for shorter sprints. As an example, a team on two-week sprints can book 60 to 90 minutes; the guide gives no figure for that sprint length.
Who attends the sprint retrospective?
The Scrum Team: the developers, the product owner and the scrum master. The Scrum Guide names no other participant. A manager or a stakeholder comes only if the team invites them.
What is the difference between a sprint review and a sprint retrospective?
The sprint review inspects the product: the Scrum Team shows the result of the sprint to stakeholders, for a maximum of four hours for a one-month sprint. The sprint retrospective comes after it and inspects how the team works, for a maximum of three hours.