HKSM
Length of Sprint
The fixed timebox for each Sprint, chosen jointly by the Product Owner and the Scrum Team using inputs such as business requirements and the release plan. After it is set, that duration is typically kept the same for all Sprints in the project.
Key Points
- Agreed by the Product Owner and Scrum Team, typically during or before release planning.
- Selected using inputs like business priorities, release planning schedule, risk, and desired feedback frequency.
- Once chosen, the Sprint duration remains stable; do not extend a Sprint to fit more scope.
- Common durations are 1–4 weeks; shorter Sprints increase feedback and control, longer Sprints reduce overhead.
Example
During release planning, the Product Owner and Scrum Team pick a 2-week Sprint to align with business needs and the release plan. Throughout the project they keep every Sprint at 2 weeks. When a stakeholder later asks to extend Sprint 5 to 3 weeks to include more features, the team keeps the 2-week timebox and reprioritizes the backlog instead.
PMP Example Question
In a new Scrum project, how is the Sprint length established and maintained?
- The Scrum Master sets it and changes it each Sprint to optimize throughput.
- The Product Owner sets it alone during release planning and may extend Sprints when scope grows.
- The Product Owner and Scrum Team agree on the duration using inputs like business needs and the release plan; once chosen, it remains consistent across Sprints.
- The project sponsor mandates it, and the team varies it to match stakeholder availability.
Correct Answer: C — Product Owner and Scrum Team agree on a fixed Sprint duration
Explanation: Sprint length is a collaborative decision informed by business and release planning inputs, and it should stay constant to preserve cadence and predictability.
