How much of the Sprint Backlog must be defined during the Sprint Planning event?
A. Just enough tasks for the Scrum Master to be confident in the Development Team’s understanding of the Sprint.
B. The entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting.
C. Enough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.
D. Just enough to understand design and architectural implications.
How To Pass PSM I Exam?Scrum PSM I PDF dumps.High quality PSM I PDF and software. VALID exam to help you pass. |
 |
How To Pass PSM II Exam?Scrum PSM II PDF dumps.High quality PSM II PDF and software. VALID exam to help you pass. |
|
It’s C, The answer is litterly after pressing the show answer button. ITS C
[…] For each selected Product Backlog item, the Developers plan the work necessary to create an Increment
that meets the Definition of Done. […]
The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are
together referred to as the Sprint Backlog. […]
Why is “for each” here to understand as “as much as you need” instead of “for all”?
can anyone explain why it is not B ?
As per Scrum Guide “The Sprint Goal must be finalized prior to the end of Sprint Planning” NOT the Sprint Backlog. Sprint Backlog can be updated anytime during the Sprint by the Development Team, keeping the Sprint Goal unchanged.
what must be done prior the end of sp planning is definition of Sp goal (answer to the question of “why”) and a selection of PBI envisioned during the sprint to fullfill Sp Goal (answer to the question of “what”) then dev plans the work needed NOT FOR ALL selected PBI within Sp Planning but the necessary ones to do (doing there best before timebox end) and the remaining ones will be treated during refinement meetings.