70-499 Question #73: Real Exam Question with Answer & Explanation

Question

Options

• AThe iteration length should be long enough to ensure than no more than 20 percent of the
• BThe iteration length should be consistent.
• CThe iteration length should be flexible.
• DThe sprint length should be long enough to create a usable and potentially releasable
• EThe iteration length should be longer than one month.

Explanation

I asked Ken Schwaber once how long a Sprint should be. His answer was, "As short as possible and no shorter." Sprints of longer than four weeks (one month) have a smell--the smell of water falling. When a Sprint's length is longer than a month, the definition of what is being built may change or complexity and risk may increase. By limiting the maximum length of a Sprint, at most one month of development effort would be wasted, rather than several months in a classic waterfall project. Conversely, Sprints with a length of less than one week are possible, but should be executed only by a high-performance Scrum Team. Even with very short Sprints, the overhead of the inner events must be factored in, leaving even less time for actual software development. Teams working in "micro sprints" like these need to be on their A-game every day. Ideally, the length of the Sprint does not change. If it must, it can only change in between Sprints, as a result of a decision made collaboratively during the prior Sprint's retrospective meeting. Any change to the length of a Sprint will cause disruption to the Development Team's cadence. This will correct over time, as will its Velocity. Professional Scrum Development with Microsoft Visual Studio 2012 p.15

No community discussion yet for this question.