HKSM
Retrospect Sprint Meeting
A time-limited meeting in the Retrospect Sprint process where the Scrum Team examines the most recent Sprint to find ways to improve. For a one-month Sprint, it is limited to 4 hours, and the duration is scaled up or down based on the Sprint length. The team reviews workflows, tools, collaboration and communication practices, and other project-relevant factors to identify actionable improvements.
Key Points
- Time-box: up to 4 hours for a one-month Sprint, scaled proportionally for shorter or longer Sprints.
- Participants: the entire Scrum Team collaborates in a blameless, improvement-focused discussion.
- Scope: inspect processes, tools, collaboration, communication, and other factors affecting delivery.
- Outcome: specific, owned action items to implement in the next Sprint to enhance performance.
Example
After a 2-week Sprint, the team holds a 2-hour retrospective. They discover that manual release steps caused delays. They agree to add a task to automate packaging and document the release checklist, assigning clear owners for the next Sprint.
PMP Example Question
Which Scrum event is limited to 4 hours for a one-month Sprint and focuses on improving how the team works, including processes, tools, and collaboration?
- Sprint Planning
- Daily Scrum
- Retrospect Sprint Meeting
- Sprint Review
Correct Answer: C — Retrospect Sprint Meeting
Explanation: The Retrospect Sprint Meeting (retrospective) is time-boxed to 4 hours for a one-month Sprint and is dedicated to inspecting and improving team practices.
