Sprint Retrospective
An end-of-Sprint meeting where the team examines how they worked, identifies what went well and what did not, and agrees on specific changes to improve in the next Sprint.
Key Points
- Held after the Sprint Review and before the next Sprint starts.
- Includes the whole Scrum Team and focuses on the process and teamwork, not the product.
- Produces a small set of actionable improvement items to try in the next Sprint.
- Facilitated to encourage honest inspection and continuous improvement within a timebox.
Example
After a two-week Sprint, the team meets for 60 minutes to analyze their workflow. They note that code reviews were delayed, agree to introduce a daily review window, and decide to limit work in progress to reduce context switching. They add these actions to the next Sprint plan.
PMP Example Question
Which Scrum event is specifically intended to inspect the team's process and define improvements for the next Sprint?
- Sprint Review
- Daily Scrum
- Sprint Retrospective
- Backlog Refinement
Correct Answer: C — Sprint Retrospective
Explanation: The Sprint Retrospective focuses on how the team works and results in actionable changes for the next Sprint. The Sprint Review inspects the product, not the process.
HKSM