Sprint Retrospective (Meeting)

The Sprint Retrospective is the final event in a Sprint. While the Sprint Review focuses on inspecting the product, the Retrospective is about inspecting and improving how the team works its collaboration, processes, and tools.

The Scrum Team reflects together on how the last Sprint went and identifies concrete ways to improve. It's an essential part of creating a culture of continuous learning and adaptation.

Focus areas

• What helped or hindered collaboration?

• Which processes or tools supported - or blocked - our flow?

• What can we try next to improve team dynamics or effectiveness?

The Retrospective is timeboxed to a maximum of 3 hours for a one-month Sprint (shorter for shorter Sprints) and typically facilitated by the Scrum Master. Everyone on the team participates.

A helpful structure many teams use is the 5-phase model by Diana Larsen and Esther Derby:

1. Set the stage

2. Gather data

3. Generate insights

4. Decide what to do

5. Close the retrospective

For ideas and formats, check out retromat.org, a popular tool for designing engaging retrospectives.

The goal of every Sprint Retrospective is to leave with 1 - 2 concrete improvements the team will try in the next Sprint - turning reflection into action.