How much of the Sprint Backlog must be defined during Sprint Planning? (Choose the best answer)

Question

Options

• AEnough so the Developers can create a forecast of what they can do during the Sprint.
• BAll of the potential work. Sprint Planning is not over until 100% of the work is identified and
• CJust enough to understand design and architectural implications.
• DJust enough tasks for the Scrum Master to be confident in the Developer's understanding of the

• A
  89% (16)
• B
  6% (1)
• C
  6% (1)

Explanation

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a "Done" Increment. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Developers work through the plan and learn more about the work needed to achieve the Sprint Goal. The Sprint Backlog is not a commitment to deliver a fixed scope of work, but rather a forecast of what the Developers believe they can do in the Sprint. Therefore, the Sprint Backlog does not need to be fully defined during the Sprint Planning, but only enough so the Developers can create a realistic forecast of what they can do during the

No community discussion yet for this question.