During Sprint Planning the Product Owner and the Developers are unable to reach an understanding about the highest order Product Backlog items. Because of this, the Developers are unable to…

Question

Options

• ACancel the Sprint Send the entire team to an advanced Scrum training and then start a new Sprint
• BDuring the next Sprint Retrospective discuss why this happened and what changes will make it
• CContinue the Sprint Planning event past its timebox until an adequate number ot Product Backlog
• DForecast the Product Backlog items that are most likely to meet the Sprint Goal and create the
• EAsk everyone to take as much time as needed to analyze the Product Backlog first, and then

• A
  4% (1)
• B
  67% (16)
• C
  21% (5)
• E
  8% (2)

Explanation

Since the Product Owner and Developers agreed on a Sprint Goal, (D) the correct action is to forecast the Product Backlog items most likely to achieve that Sprint Goal and begin the Sprint - the Sprint Goal is the anchor, not the exact item count. (B) The Sprint Retrospective is the appropriate Scrum event to inspect and adapt the planning process that caused this breakdown, so discussing it there is correct. Option A (cancel the Sprint) is wrong - the Sprint hasn't started and a Sprint Goal exists, so cancellation is unjustified. Option C (extend Sprint Planning past its timebox) violates Scrum's time-boxing principle. Option E (unlimited analysis time) is also wrong and violates time-boxing.

No community discussion yet for this question.