Scrum is based on empiricism. All of its artifacts must be transparent to ensure sufficient accuracy of inspection. How can the Scrum Team maintain the Product Backlog to maximize its transparency? (choose the best answer)
Correct Answer: E
Explanation The Scrum Team can maintain the Product Backlog to maximize its transparency by continually keeping it up to date with the most recent insights because: * It reflects the current state of the product and the work. The Product Backlog is a dynamic and emergent artifact that represents all the possible features, functions, requirements, enhancements, and fixes that constitute changes to the product. By updating it frequently, the Scrum Team can ensure that the Product Backlog is accurate, complete, and relevant. * It enables the Product Owner to optimize the value of the product and the work of the Scrum Team. The Product Owner is accountable for effective Product Backlog management, which includes ordering, refining, and communicating the Product Backlog items. By updating it frequently, the Product Owner can incorporate new learnings, feedback, opportunities, and changes into the product decisions and priorities. * It supports the inspection and adaptation of the Scrum Team and the stakeholders. The Product Backlog is a source of information and transparency for everyone involved in the product development. By updating it frequently, the Scrum Team and the stakeholders can inspect the progress and outcomes of each Sprint, and adapt their plans and actions accordingly. References: * Scrum Guide 2020, page 10: "The Product Backlog is an emergent, ordered list of what is needed to improve the product." * Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ensuring that the Product Backlog is transparent, visible and understood." * Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions." * Scrum Guide 2020, page 11: "Higher ordered Product Backlog items are clearer and more refined than lower ordered ones." * Scrum Guide 2020, page 15: "The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."
Question 77
Why is it important that there is only one Product Owner per product? (choose the best three answers)
Correct Answer: C,D,E
The reasons why it is important that there is only one Product Owner per product are: * It is clear who is accountable for the ultimate value of the product. The Product Owner is accountable * for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team. * It helps avoid barriers to effective communication and rapid decision-making. The Product Owner is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must also collaborate with the Developers and the stakeholders to refine, order, and prioritize the Product Backlog items based on value and impact. * The Scrum Team always knows who determines the order of the Product Backlog. The Product Owner has the final authority to decide what items are more important and valuable for the product. They must communicate this order clearly and consistently to the Scrum Team and the stakeholders. They must also respect and support the self-management of the Developers in choosing how best to accomplish their work. Other options, such as the Scrum Master knowing who acts as their backup while on vacation or it would confuse the stakeholders if they had to work with more than one person, are not valid reasons why it is important that there is only one Product Owner per product. They may reflect a misunderstanding of the roles and accountabilities of the Scrum Team or the stakeholders. References: * [Scrum Guide], page 6, section "Product Owner" * [Scrum Guide], page 11, section "Product Backlog" * [Scrum Guide], page 12, section "Product Backlog Refinement" * [Scrum Guide], page 11, section "Product Backlog" * [Scrum Guide], page 7, section "Developers"
Question 78
When can Developers cancel a Sprint? (choose the best answer)
Correct Answer: C
According to the Scrum Guide, a Sprint can be canceled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be canceled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be canceled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense. Developers cannot cancel a Sprint on their own, even if they face challenges or difficulties with the selected Product Backlog items, the functional expectations, the technical dependencies, or the Product Owner's availability. Instead, they should collaborate with the Product Owner and the Scrum Master to find the best way to deliver value within the Sprint and adapt to the changing situation. Reference: The Scrum Guide Understanding and Applying the Scrum Framework Professional Scrum Product Owner I Certification
Question 79
True or False: An Increment must be released to customers or users at the end of each Sprint.
Correct Answer: B
An Increment is a concrete stepping stone toward the product vision. It is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be "Done", which means it meets the Definition of Done and is usable. The Scrum Team decides when and how to release an Increment to customers or users. The Product Owner is responsible for maximizing the value of the product and the work of the Developers, and may decide to release an Increment at any time during or after a Sprint. The Developers are responsible for creating a potentially releasable Increment each Sprint, and may collaborate with the Product Owner and the stakeholders to determine the best way to deliver value. Releasing an Increment to customers or users is not mandatory at the end of each Sprint. The Scrum Team may choose to release an Increment more or less frequently, depending on the product goals, market conditions, customer feedback, or technical feasibility. However, releasing an Increment regularly can provide many benefits, such as: Validating assumptions and hypotheses about the product value and quality. Obtaining feedback and data from real users and customers. Increasing customer satisfaction and loyalty. Reducing risks and uncertainties. Improving transparency and collaboration. Reference: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Increment: https://www.scrum.org/resources/what-is-an-increment Releasing Value: https://www.scrum.org/resources/blog/releasing-value
Question 80
True or False: The Scrum Team is accountable for creating a valuable increment every Sprint.
Correct Answer: A
The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint. An Increment is a concrete stepping stone toward the product vision. It is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be "Done", which means it meets the Definition of Done and is usable. The Scrum Team is accountable for creating a valuable increment every Sprint, not just once or occasionally. This means that the Scrum Team must deliver a product functionality that provides value to the customers and users and contributes to the product goals and missions. The value of an increment can be measured by various factors, such as customer satisfaction, feedback, revenue, market share, or social impact. The Scrum Team is also accountable for creating a valuable increment every Sprint, not just any increment. This means that the Scrum Team must deliver a product functionality that meets the quality standards and expectations of the customers and users and complies with the Definition of Done. The quality of an increment can be measured by various factors, such as usability, reliability, performance, security, or maintainability. Reference: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Scrum Team: https://www.scrum.org/resources/what-is-a-scrum-team Increment: https://www.scrum.org/resources/what-is-an-increment
