HKSM
Retrospect Sprint
A meeting where the Scrum Master and Scrum Team reflect on the Sprint to capture lessons learned. These insights are documented and used to improve upcoming Sprints.
Key Points
- Conducted at the end of each Sprint to inspect team practices and identify improvements.
- Attended by the Scrum Master and Scrum Team; the focus is on process, teamwork, and tools.
- Results in documented lessons and clear action items to enhance the next Sprint.
- Emphasizes continuous improvement, not evaluating individual performance.
Example
After a two-week Sprint, the Scrum Master facilitates a Retrospect Sprint. The team notes delays caused by late code reviews and unclear test data. They agree on actions: introduce a daily code review rotation, prepare test data on day 1, and add both to the definition of done. These items are recorded and planned for the next Sprint.
PMP Example Question
Which Scrum event is primarily used to document lessons learned from the Sprint and define actions to improve the next Sprint?
- Sprint Review
- Daily Scrum
- Retrospect Sprint
- Product Backlog Refinement
Correct Answer: C — Retrospect Sprint
Explanation: The Retrospect Sprint focuses on reflecting on the process, capturing lessons learned, and creating improvement actions for future Sprints.
