How much of the Sprint Backlog must be defined during the Sprint Planning event? (choose the best answer)
Correct Answer: B
The amount of the Sprint Backlog that must be defined during the Sprint Planning event is enough so the Developers can create their forecast of what work they can do. This is because: * Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint. The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal. * The Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable. * The Developers are also accountable for creating a plan for how they will deliver the selected Product Backlog items as a "Done" Increment. The plan may include tasks, dependencies, risks, estimates, or other information that helps them organize and manage their work. * The amount of the Sprint Backlog that must be defined during Sprint Planning may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that the Developers can create their forecast of what work they can do and have a clear direction for the first few days of the Sprint. Other options, such as just enough to understand design and architectural implications, the entire Sprint Backlog being identified and estimated by the end of Sprint Planning, or just enough tasks for the Scrum Master to be confident in the Developers' understanding of the Sprint, are not valid answers as they do not reflect what must be defined during Sprint Planning or what is required for creating a Sprint forecast. References: * [Scrum Guide], page 14, section "Sprint Planning" * [Scrum Guide], page 7, section "Developers" * [Scrum Guide], page 15, section "Sprint Backlog" * [Scrum Guide], page 14, section "Sprint Planning"
Question 77
During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog? (choose the best answer)
Correct Answer: D
Explanation New work or further decomposition of work is added to the Sprint Backlog as soon as possible after it is identified because: It reflects the current state of the Sprint. The Sprint Backlog is a plan that the Developers create and update throughout the Sprint, based on their progress, learnings, and changes. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that the Sprint Backlog is transparent, accurate, and up-to-date. It enables the Developers to self-manage their work. The Developers are accountable for organizing and managing their own work, and they have the authority to change the Sprint Backlog as needed. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can exercise their autonomy and empowerment, and adjust their plan accordingly. It supports the achievement of the Sprint Goal. The Sprint Goal is a single objective that provides guidance and focus for the Developers throughout the Sprint. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that their work is aligned with and contributes to the Sprint Goal. References: Scrum Guide 2020, page 6: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint." Scrum Guide 2020, page 6: "The Developers are accountable for ... organizing and managing their work." Scrum Guide 2020, page 10: "The Sprint Goal is a single objective for the Sprint." Scrum Guide 2020, page 14: "The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current Definition of Done." Scrum Guide 2020, page 14: "The Sprint Backlog is composed of ... all of the work needed to deliver a product Increment that meets the Definition of Done." Scrum Guide 2020, page 14: "The Developers can change the content of the Sprint Backlog throughout the Sprint as more is learned."
Question 78
The satisfaction of which stakeholder is the most important?
Correct Answer: C
Question 79
Stakeholder collaboration should take place for a specific topic. Whou should make sure, that they are collaborating with the team if requested by the team?
Correct Answer: C
Question 80
What is the responsibility of the Product Owner in crafting the Sprint Goal? (choose the best answer)
Correct Answer: C
Explanation * The Sprint Goal is a short statement of what the Scrum Team intends to achieve during a Sprint. It provides guidance and direction for the Scrum Team, as well as a basis for inspecting and adapting the product and the process. The Sprint Goal is aligned with the product vision and goals, and it reflects the value and purpose of the Sprint. * The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time. * The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations. * The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment. * The responsibility of crafting the Sprint Goal is shared by both the Product Owner and the Developers. The Product Owner should come to Sprint Planning with a business objective in mind, based on their understanding of the product vision, goals, value proposition, stakeholder feedback, market conditions, or other relevant factors. The Product Owner should propose how this objective can be achieved by selecting some Product Backlog items that can deliver value to customers or users. The Developers * should collaborate with the Product Owner to craft a clear and concise Sprint Goal that expresses what they want to accomplish as a team during this Sprint. The Developers should also ensure that they have enough capacity and skills to deliver on this Sprint Goal. References: * Scrum Guide: https://www.scrumguides.org/scrum-guide.html * Sprint Goal: https://www.scrum.org/resources/what-is-a-sprint-goal * Product Owner: https://www.scrum.org/resources/what-is-a-product-owner * Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum * Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning
