Sprint Retrospective Explained: Purpose, Format and Scrum Master Role
The Sprint Retrospective is the Scrum event where the Scrum Team looks back at the Sprint and identifies ways to improve its effectiveness and quality.
The focus is not on blaming people. The goal is to learn from the Sprint and decide what can be improved in the next one.
Purpose of the Sprint Retrospective
The Scrum Team inspects areas such as:
- People and interactions
- Processes
- Tools
- Definition of Done
- Other factors that affected the Sprint
When Does It Happen?
The Sprint Retrospective takes place toward the end of the Sprint, after the Sprint Review and before the next Sprint Planning.
For a one-month Sprint, it has a maximum timebox of three hours. Shorter Sprints usually have shorter Retrospectives. :contentReference[oaicite:1]{index=1}
What Happens During the Retrospective?
1. Inspect the Sprint
The team discusses what happened during the Sprint, including successes, problems and factors that affected the work.
2. Identify Improvements
The team identifies the most useful changes that could improve quality and effectiveness.
3. Decide What to Change
The team chooses practical improvements rather than creating a long list of actions that nobody will follow.
4. Apply the Improvements
Important improvements should be implemented as soon as possible. They can also be added to the next Sprint Backlog when appropriate. :contentReference[oaicite:2]{index=2}
Simple Retrospective Questions
Example
Suppose a team repeatedly waits several days for another team to provide an API.
During the Retrospective, the Scrum Team identifies this dependency as a problem.
Instead of simply recording the problem, the team might agree to involve the other team earlier during planning and establish a clearer dependency-handling process.
An improvement should be specific enough that the team can actually try it and later determine whether it helped.
Common Retrospective Techniques
- Start, Stop, Continue — what should we start, stop and continue doing?
- Mad, Sad, Glad — explore emotional reactions to the Sprint.
- 4Ls — Liked, Learned, Lacked and Longed for.
- Timeline — review important events throughout the Sprint.
The Scrum framework does not require one specific Retrospective technique. The Scrum Team can choose a format that helps achieve the purpose of the event.
What Is the Scrum Master's Role?
The Scrum Master helps create an environment where the team can openly discuss problems and improvements.
The Scrum Master should encourage constructive discussion, help the team stay focused, and support the implementation of useful improvements.
Common Mistakes
Key Takeaway
A Retrospective is valuable only when the team uses what it learns to improve how it works.
The goal is not to find someone to blame. The goal is to make the next Sprint better.