What is the Sprint Retrospective
The Sprint Retrospective is the closing event of the Sprint. The team inspects how the last Sprint went and identifies the single change that would most improve effectiveness or happiness in the next Sprint.
It is time-boxed to a maximum of three hours for a one-month Sprint. Usually shorter for shorter Sprints.
Why It Matters
The Sprint Retrospective is where teams get faster. Without it, teams can run Sprints for years without improving. With it, small improvements compound into significant performance gains.
How It Works in Scrum
The team inspects:
- What went well in the Sprint
- What problems came up
- Which of those problems were solved, and which are still open
High-performing teams use the Retrospective to identify the single change that would most improve effectiveness or happiness in the next Sprint. That change goes into the next Sprint Backlog so it gets done as real work.
Common Mistakes
- Skipping it when "nothing happened." Every Sprint has lessons.
- No follow-through. A list of improvements that never gets done is a complaint session.
- Treating it as a performance review. The Retrospective inspects the team and the system, not individuals.
- Venting without action. Acknowledging frustration is fine. Stopping there is not.
- Letting it become routine. A team that runs the same template forever stops learning from it.
Key Takeaways
- The Sprint Retrospective closes the Sprint.
- The team picks one improvement that would most increase effectiveness or happiness.
- That improvement goes into the next Sprint Backlog.
- Teams get faster over time by acting on what they learn.