Exam ASF topic 1 question 77 discussion

C. "Because the Sprint duration is not based on single events" aligns with the Scrum Guide’s principle that: Sprint durations should remain consistent to support predictability and reduce complexity. Sprint duration should not be changed based on single events, such as a Product Owner’s vacation. Sprint length is determined by the Scrum Team, considering technical and business factors. typically agreed upon during Sprint Planning, not solely by the Development Team. 📌 Source: Scrum.org discussion on Sprint length [www.scrum.org] ❌ Why B Is Misleading: While it’s technically true that Sprint duration can be between 2 and 4 weeks, the question is about changing the duration mid-project due to a single event. That’s not recommended in Scrum.

C. No, because the Sprint duration is not based on single events.

Sprint duration is meant to create a stable, predictable rhythm for the team and the organization. Think of it like the heartbeat of your development process. Just as your heart maintains a steady rhythm to keep your body functioning smoothly, consistent Sprint duration helps teams maintain a reliable delivery pace and establish sustainable working patterns. When teams frequently change Sprint duration to accommodate individual schedules or events, several problems emerge. First, it disrupts the team's velocity measurements and makes planning less reliable. Second, it can create confusion about when various Scrum events should occur. Most importantly, it undermines the fundamental concept of timeboxing in Scrum, which helps manage complexity and risk through regular inspection and adaptation points.