Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 43 of 66
Free Preview · 66 of 218 · questions 1–66 of 218 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
The correct answer is 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. The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. The Sprint Backlog is created during the Sprint Planning event and then added to throughout the Sprint as new work is identified. The Sprint Backlog is owned by the Developers, and they are responsible for updating it and keeping it accurate. The Sprint Backlog should be detailed enough so that the Developers can create their best forecast of what they can do during the Sprint, and to start the first several days of the Sprint. However, it does not need to be complete, and it can be updated throughout the Sprint as new work is identified
Scrum Guide says “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.
Totally agree with you