Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done? (choose the best two answers)
Correct Answer: C,D
Explanation The Product Owner should care that the Scrum Team adheres to its Definition of Done because: It helps to forecast the team's productivity over time. By having a clear and consistent Definition of Done, the Product Owner can measure the amount of work that the team can deliver in each Sprint and plan accordingly. It affects the product's total cost of ownership. By ensuring that the work done by the team meets the quality standards and expectations of the stakeholders, the Product Owner can reduce the risk of technical debt, rework, defects, and maintenance costs in the future. References: Scrum Guide 2020, page 10: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product." Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and, ensuring that the Product Backlog is transparent, visible and understood." Scrum Guide 2020, page 14: "The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration."
Question 82
The Developers find out during the Sprint that they are not likely to build everything they forecast. What would you expect a Product Owner to do? (choose the best answer)
Correct Answer: D
If the Developers find out during the Sprint that they are not likely to build everything they forecast, the best response from the Product Owner is to re-work the selected Product Backlog items with the Developers to meet the Sprint Goal. This is because: * The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the Sprint. * The Developers are accountable for creating a "Done" Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete. * The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal. * The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and guidance to the Developers as needed to help them create a valuable Increment. * If the Developers find out during the Sprint that they are not likely to build everything they forecast, it means that there is a gap between their initial plan and their actual progress. This may happen due to various reasons, such as new insights, changing requirements, technical challenges, or unforeseen circumstances. * In this situation, the Product Owner should work with the Developers to re-work the selected Product Backlog items to meet the Sprint Goal. This may involve adding, removing, or modifying some items, as long as they still support the Sprint Goal and deliver value. The Product Owner should also communicate any changes or impacts to the stakeholders and customers as appropriate. Other options, such as skipping Product Backlog refinement activities, informing management that more Developers are needed, changing the Sprint Goal, or canceling the Sprint, are not valid responses from the Product Owner as they do not reflect what should happen in Scrum or how to deal with uncertainty and complexity. References: * [Scrum Guide], page 15, section "Sprint Goal" * [Scrum Guide], page 7, section "Developers" * [Scrum Guide], page 6, section "Product Owner" * [Scrum Guide], page 10, section "Definition of Done" * [Scrum Guide], page 10, section "Increment" * [Scrum Guide], page 10, section "Product Goal"
Question 83
All Scrum artifacts must be transparent to ensure sufficient accuracy of inspection. Which two measures ensure that the Product Backlog is transparent? (choose the best two answers)
Correct Answer: A,B
Explanation Transparency is one of the three pillars of Scrum, along with inspection and adaptation. Transparency means that all aspects of the Scrum process and the product are visible and understandable to everyone who needs to work on or with them. Transparency enables effective inspection and adaptation, which are essential for delivering valuable products and improving the Scrum Team's performance. All Scrum artifacts must be transparent to ensure sufficient accuracy of inspection. Scrum artifacts include the Product Backlog, the Sprint Backlog, and the Increment. The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product. Two measures that ensure that the Product Backlog is transparent are: The Product Backlog is ordered: The Product Owner orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions. The order of the Product Backlog items provides a clear and consistent indication of what is most important and urgent for the product. The order of the Product Backlog items also helps the Scrum Team and the stakeholders to plan and forecast effectively. The Product Backlog is available to all stakeholders: The Product Owner makes the Product Backlog visible and accessible to everyone who has a stake in the product, such as customers, users, sponsors, managers, or other teams. The availability of the Product Backlog enables transparency, collaboration, feedback, and alignment among all parties involved in the product development. The other options are not valid or relevant measures to ensure that the Product Backlog is transparent. They are either too restrictive, arbitrary, or unrelated to the Product Backlog's transparency. They are: Each Product Backlog item has a MoSCoW priority: MoSCoW is a technique for prioritizing requirements based on their importance: Must have, Should have, Could have, or Won't have. While this technique can be useful for some products or contexts, it is not a mandatory or universal way to order the Product Backlog items. The Product Owner may use other factors or methods to order the Product Backlog items based on their value and relevance for the product. The Product Backlog only has work for the next 2 Sprints: This is a too limiting and unrealistic measure for the Product Backlog. The Product Backlog should contain all the work that is known to be needed in the product, not just for the next 2 Sprints. The Product Backlog is a living artifact that evolves as the product and the market change. The Product Owner should continuously refine and update the Product Backlog to reflect the current and future needs and expectations of the customers and users. The Product Backlog is managed using a web-based tool: This is an irrelevant measure for the Product Backlog's transparency. The Product Owner can use any tool or format to manage the Product Backlog, as long as it is clear, concise, and valuable. The tool or format does not affect the transparency of the Product Backlog itself. What matters more is how the Product Owner communicates and collaborates with the Scrum Team and the stakeholders using the Product Backlog. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Transparency: https://www.scrum.org/resources/blog/transparency-scrum-value Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog MoSCoW: https://www.agilealliance.org/glossary/moscow/
Question 84
Scrum combines three formal events for inspection and adaptation within a containing event, the Sprint.
Correct Answer: B
Question 85
Why is the Daily Scrum held at the same time and same place? (choose the best answer)
Correct Answer: D
The Daily Scrum is held at the same time and same place because: * The consistency reduces complexity. By having a fixed time and place for the Daily Scrum, the * Developers can avoid wasting time and energy on scheduling, logistics, or coordination issues. They can also establish a routine and a rhythm that helps them focus on their work and their Sprint Goal. * The consistency increases transparency. By having a fixed time and place for the Daily Scrum, the Developers can ensure that everyone is aware of when and where the meeting takes place, and that everyone has an opportunity to participate and share their progress, plans, and challenges. They can also invite other stakeholders or observers, if they find it useful, to provide feedback or support. * The consistency enhances collaboration. By having a fixed time and place for the Daily Scrum, the Developers can create a safe and comfortable space for them to communicate, interact, and collaborate with each other. They can also build trust, rapport, and accountability among themselves, and foster a sense of team spirit and ownership. References: * Scrum Guide 2020, page 12: "The Daily Scrum is held at the same time and place each day to reduce complexity." * Scrum Guide 2020, page 12: "The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work." * Scrum Guide 2020, page 13: "The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting."
