Professional Scrum Master I (PSM I)Scrum FrameworkMedium
A Scrum Team has been struggling with unpredictable Sprint durations. Sometimes Sprints last two weeks, other times three, based on when they feel 'Done' with the work. This makes it difficult for stakeholders to plan and for the Product Owner to forecast releases. Which Scrum Event's time-box is being fundamentally misunderstood or ignored?
- ASprint Planning
- BSprint Review
- CSprint
- DDaily Scrum
Show answer & explanationAnswer & explanation
Correct answer: C. Sprint
The Sprint itself is a time-boxed event of one month or less during which a 'Done', usable, and potentially releasable Increment is created. Its fixed length provides regularity and predictability for planning and inspection. Varying Sprint durations indicates a misunderstanding of the Sprint as a time-box.
Why the other options are wrong
- A. Sprint Planning is time-boxed, but its misunderstanding would affect the planning of work, not the overall Sprint length.
- B. The Sprint Review is time-boxed, but its misunderstanding would affect feedback and adaptation, not the overall Sprint length.
- D. The Daily Scrum is time-boxed, but its length does not dictate the overall Sprint duration.
Sprint Time-box
The Sprint is a fixed-length event of one month or less. Its consistent duration provides rhythm and predictability, allowing for regular inspection and adaptation of the product and process.
- Fixed length (1 month or less).
- Container for all other Scrum events.
- Provides rhythm and predictability.
Memory trick: Predictable Sprints Ensure Steady Progress.