Look back
Start, stop, continue
A retrospective in three columns: what to start doing, what to stop, and what to keep, which leads straight to changes.
- Time30 to 45 minutes
- People3 to 12 people
- Steps4
What it's for
The simplest retrospective that still ends in action. Each column is already phrased as a change, so the discussion moves quickly from what happened to what to do about it.
Its weakness is the same thing: it skips over why. When a team keeps writing the same notes sprint after sprint, switch to a format that digs deeper.
How to run it
Write notes7 min
Silently, add notes to all three columns.
Read and group10 min
Each person reads theirs out; group duplicates.
Vote4 min3 votes each
Vote for the changes that would make the most difference.
Commit8 min
Turn the top two or three into actions with owners.
Tips
- Look at last time's actions first. A retro that never checks its actions stops being taken seriously.
- Limit the changes to two or three. Ten changes means none happen.
Where it comes from
A long-established feedback format in agile teams and management. Its origin is not documented.
Pairs well with
Mad, sad, glad
A retrospective that starts with feelings: what made people angry, what disappointed them, and what made them happy.
4Ls retrospective
A retrospective in four quadrants: what people liked, learned, lacked and longed for, which balances facts and wishes.
Starfish retrospective
A five-part retrospective: keep doing, do more of, do less of, stop doing, and start doing.