The Sprint Retrospective

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regard to individuals, interactions, processes, tools and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The team discusses what went well during the Sprint, what problems it encountered and how those problems were, or were not, solved.

The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible; they may even be added to the Sprint Backlog for the next Sprint. Improvement does not have to wait for the Retrospective — it can happen at any time — but the Retrospective is the formal opportunity to focus on it.

The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint, usually shorter for shorter Sprints. The whole Scrum Team takes part, including the Product Owner and the Scrum Master.

Study focus: the Retrospective is about how the team works, not about inspecting the product — that is the Sprint Review. A Retrospective that produces no actionable improvement, or a Scrum Master who decides the improvements alone, misses the point.