Which topics should be discussed in the Sprint Review? (choose the best answer)

Correct Answer:C
The main topic of discussion is the product Increment, which is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints1. The product Increment is demonstrated and inspected by the attendees, and feedback is collected to inform the next Sprint Planning12. The Sprint Review may also include other topics, such as the Product Backlog, the Product Goal, the market conditions, the budget, and the timeline, but the product Increment is the essential topic1234. The Scrum process, and how it was used during the Sprint, is not a topic for the Sprint Review, but rather for the Sprint Retrospective, which is a separate event where the Scrum Team inspects and adapts its way of working1. Coding and engineering practices are also not relevant for the Sprint Review, as they are internal aspects of the Development Team that do not affect the value of the product Increment1. Therefore, the correct answer is C. The product Increment.

True or False: Multiple Scrum Teams working on the same product must have the same Sprint
start date.

Correct Answer:B
Multiple Scrum Teams working on the same product do not have to have the same Sprint start date. The Scrum Guide does not prescribe any synchronization of Sprints across multiple teams1. However, it is recommended that the teams align their Sprint cadence and duration, and coordinate their dependencies and integration through a shared Product Backlog, a common Definition of Done, and frequent communication2. This way, the teams can deliver a coherent and valuable product Increment every Sprint[3][3].
References:
1: The Scrum Guide, November 2020, p. 9
2: Managing Products with Agility, Scrum.org, accessed on December 16, 2023 [3][3]: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

Which is NOT a valid consideration when ordering a Product Backlog? (choose the best answer)

Correct Answer:D
✑ 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.
✑ The Product Owner is accountable for ordering the Product Backlog. 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 tools and techniques used to create, manage, or refine the Product Backlog are not a valid consideration when ordering the Product Backlog. The tools and techniques are means to an end, not an end in themselves. The tools and techniques do not affect the value or quality of the product or service delivered. The tools and techniques may vary from one Product Owner to another, depending on their preferences, skills, or context. The tools and techniques may also change over time, as new technologies or practices emerge or evolve.
References:
✑ Scrum Guide: https://www.scrumguides.org/scrum-guide.html
✑ Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog
✑ Product Owner: https://www.scrum.org/resources/what-is-a-product-owner

If Product Backlog refinement is needed, when is the ideal time for refinement to take place and
who should participate? (choose the best two answers)

Correct Answer:AE
The ideal time for refinement to take place and who should participate are the Scrum Team during the current Sprint, if they have been unable during preceding Sprints to define Product Backlog items with enough precision to begin work, and the Scrum Team on an ongoing basis, defining Product Backlog items into smaller more precise items that are ready for selection. This is because:
✑ Product Backlog refinement is the act of adding detail, estimates, and order to Product Backlog items. It is an ongoing and collaborative process that involves the whole Scrum Team.
✑ The Scrum Team should refine the Product Backlog as needed to ensure that there are enough items that are sufficiently clear and ready for selection in Sprint Planning. The amount of time spent on refinement usually varies from one Scrum Team to another, but it is recommended not to exceed 10% of the capacity of the Developers.
✑ The Scrum Team may also use a Sprint to refine the Product Backlog if they have not been able to do so in previous Sprints. This may happen when the product is new or complex, or when there is a significant change in the product vision or direction. However, this should be an exception rather than a rule, as it may delay the delivery of value and feedback.
Other options, such as business analysts doing the refinement work for the Scrum Team, the Product Owner doing the refinement alone in Sprint 0 or between Sprints, or handing off the ownership of the Product Backlog to someone else, are not consistent with the principles and values of Scrum. They may lead to misunderstandings, misalignment, or loss of ownership and accountability.
References:
✑ [Scrum Guide], page 11, section “Product Backlog”
✑ [Scrum Guide], page 12, section “Product Backlog Refinement”
✑ [Professional Scrum Product Owner™ Training], page 7, section “Product Backlog Management”
✑ [Professional Scrum Product Owner™ Training], page 8, section “Release Management”
✑ [Professional Scrum Product Owner™ Training], page 9, section “Business Strategy”

Who does the work to make sure Product Backlog items conform to the Definition of Done? (choose the best answer)

Correct Answer:D
The work to make sure Product Backlog items conform to the Definition of Done is done by the Developers. This is because:
✑ 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 Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what “Done” means for any Product Backlog item that is selected for a Sprint.
✑ The Developers are self-managing professionals who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team.
Other options, such as the Product Owner, the Quality Assurance Team, the Scrum Team, or the Scrum Master, are not responsible for making sure Product Backlog items conform to the Definition of Done. They may have different roles and accountabilities in Scrum, but they do not do the actual work of creating a “Done” Increment.
References:
✑ [Scrum Guide], page 7, section “Developers”
✑ [Scrum Guide], page 10, section “Definition of Done”
✑ [Scrum Guide], page 7, section “The Scrum Team”

Which of the following practices might help the Product Owner minimize waste in developing
and sustaining the Product Backlog? (choose the best two answers)

Correct Answer:CD
The practices that might help the Product Owner minimize waste in developing and sustaining the Product Backlog are:
✑ Remove items from the Product Backlog that have not been addressed in a long time. This helps keep the Product Backlog relevant, concise, and focused on delivering value. Items that have not been addressed in a long time may indicate that they are not important, feasible, or desirable anymore. They may also clutter or confuse the Product Backlog and make it harder to order and prioritize.
✑ Only fully describe Product Backlog items when it seems likely they will be implemented. This helps avoid spending too much time or effort on items that may change or be discarded later. Items that are likely to be implemented soon should have more detail and precision than items that are further away or uncertain. The level of detail and precision required for each item depends on its order, size, and complexity.
Other options, such as avoiding distracting the Scrum Team by maintaining newly gathered Product Backlog items in a separate Product Backlog until they are fully understood or handing off ownership of the Product Backlog to someone else, are not practices that might help minimize waste in developing and sustaining the Product Backlog. They may actually create more waste by reducing transparency, collaboration, alignment, or ownership. References:
✑ [Scrum Guide], page 11, section “Product Backlog”
✑ [Scrum Guide], page 6, section “Product Owner”
✑ [Scrum Guide], page 12, section “Product Backlog Refinement”