Retrospective
Start Stop Continue
3 steps, 21 min · Method after Esther Derby & Diana Larsen, Agile Retrospectives (2006)
A first retro often ends the same way: a long list on the wall and nobody sure what happens next. Start Stop Continue keeps it small. The team says what to start, what to stop and what to keep doing, everyone gets a turn, and the three questions stand with their minutes on a screen the whole group sees, in the room or shared in a video call, so you can listen instead of keeping count.
The steps
- 1StartWhat should we start doing?7 min
- 2StopWhat should we stop doing?7 min
- 3ContinueWhat should we keep doing?7 min
These are the method’s minutes. During the session you add or take off a minute when the group needs it.
Roles
- Facilitator
- Leads the session, gives the word round the circle and decides when to move on.
- Note-taker
- Catches action ideas as you talk, one line each.
What the group sees
When Start Stop Continue fits
Pick it when the team is new to retrospectives, when you have half an hour, or when the last weeks were ordinary and you want to keep the habit of looking back without making it heavy. The three questions ask about behaviour, so the answers already sound like things to do.
Leave it when something big has happened: a release that failed, a quarrel, a colleague who left. Three tidy questions are too small for that. 4Ls gives more room for what people learned and missed, and Sailboat lets a team say a hard thing through a picture.
Leading it, question by question
Start. People write a few words on their phone first, then you go round the circle. The usual first answer is a wish, such as “better communication”. Ask one question back: what would we see on Monday if we did that? The answer to that is the real note.
Stop. The hardest of the three, because stopping something means somebody started it. Keep the question on what we do, not on who does it. When a name comes up, ask which habit is meant, and let the group talk about the habit.
Continue. The step that gets skipped when time is short, and should not be. This is where the team hears what works, and things that work but are never named disappear quietly when the pressure rises.
While you talk, the note-taker catches action ideas from a phone, one line each. On the last screen you give each one a name and a date, or drop it.
Three things to watch
- Twelve things to start. A long list feels productive and changes nothing. Close with one or two actions that have a name beside them.
- “Stop” becomes blame. If the room tightens, say aloud that the question is about our way of working, and move the talk from the person to the habit.
- The same answers as last time. That is a sign the last actions were not done, or that the format has worn thin. Ask which it is, and next time take another format.
Where it comes from
Nobody owns these three questions; they were used for feedback long before agile teams. Esther Derby and Diana Larsen describe the retrospective form in Agile Retrospectives (2006), among the short activities for deciding what to do. The step names and questions on the screen are our wording.
Other methods
- 4Ls · Retrospective, 4 steps, 24 min
- Sailboat · Retrospective, 3 steps, 20 min
- Incident method · Intervision, 8 steps, 38 min