A sprint retrospective is the meeting at the end of a sprint where a team looks at how it worked, not what it built, and picks something to change. Run well, it stops a team hitting the same problems every sprint. Run badly, it is an hour of sticky notes that changes nothing.
Where the retrospective fits
In Scrum, work happens in sprints: fixed blocks of time, usually one to four weeks, each with a goal. Every sprint ends with two meetings, and they are easy to mix up.
- The sprint review looks at the product. The team shows what it built and talks with stakeholders about what to build next.
- The sprint retrospective looks at the team. It comes last and closes the sprint. The question is how the team worked: its communication, its tools, its planning and its definition of 'done'.
The Scrum Guide caps the retrospective at three hours for a one-month sprint, and less for shorter ones. On two-week sprints, an hour is common. It is for the team itself: the developers, the Scrum Master and the product owner. Many teams keep managers out unless they are invited, because people speak less openly in front of the person who writes their performance review.
If Scrum and sprints are new to you, Development Methodologies compares Scrum with the other common ways teams organise their work.
The three questions
Most retrospectives come down to three questions:
- What went well? This is worth keeping, so it doesn't get dropped by accident.
- What didn't go well? Problems, blockers, surprises and frustrations.
- What will we change next sprint? These are the action items.
The classic way to run this is a board with three columns, often called 'Went well', 'Didn't go well' and 'Action items'. Everyone writes notes for the first two columns, the team groups similar notes, and the third column is filled in together at the end.
Wondering how this was made? How we make these