What is the timebox for the Sprint Review? (choose the best answer)
Correct Answer:
C
The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:
✑ The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration.
✑ The timebox for each Scrum event is proportional to its frequency and duration. A one-month Sprint corresponds to a maximum calendar month.
✑ The timebox for a one-month Sprint Review is four hours. For shorter Sprints, it is usually shorter.
✑ The timebox ensures that there is enough time to inspect what has been done in relation to what could be done next and make any necessary adaptations to optimize value.
Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review. References:
✑ [Scrum Guide], page 17, section “Sprint Review”
✑ [Scrum Guide], page 9, section “Sprint”
✑ [Scrum Guide], page 9, section “Timeboxing Scrum Events”
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”
When does a Developer become accountable for an item in the Sprint Backlog? (choose the best answer)
Correct Answer:
C
The Developers on the Scrum Team share accountability for the Sprint Backlog, which is a forecast of the work and the plan to deliver the Sprint Goal12. The Sprint Backlog is dynamic and can be updated by the Developers as more is learned during the Sprint34. The Developers are not individually accountable for the items in the Sprint Backlog, nor are they assigned by the Scrum Master or the Product Owner5.
Why is it important that there is only one Product Owner per product? (choose the best three answers)
Correct Answer:
CDE
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”
A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountable for the Product Backlog.
However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog
should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog?
• Stability requirements
• Performance requirements
• Product Functionality
• Documentation
• Fixes
(choose the best answer)
Correct Answer:
A
✑ 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.
✑ All types of requirements are acceptable on a Product Backlog, as long as they are aligned with the product vision and goals, and they are transparent, clear, and valuable. The Product Backlog can include stability requirements, performance requirements, product functionality, documentation, fixes, or any other aspects that contribute to the quality and usability of the product.
✑ 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.
References:
✑ Scrum Guide: https://www.scrumguides.org/scrum-guide.html
✑ Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog