True or False: The Product Owner must write all of the Product Backlog items (e.g., user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team.
Correct Answer:
B
It is not true that the Product Owner must write all of the Product Backlog items (e.g. user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team. This is because:
✑ The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is never complete and constantly changes to reflect the needs and desires of the customers, users, and stakeholders.
✑ 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.
✑ The Product Owner is also accountable for managing the Product Backlog items effectively. They must ensure that they are transparent, visible, and understood by everyone who needs to work on them. They must also collaborate with the Developers and stakeholders to refine, order, and prioritize them based on value and impact.
✑ The Product Owner does not need to write all of the Product Backlog items by themselves or before handing them over to the Scrum Team. They can involve others in creating or contributing to them, such as customers, users, stakeholders, or Developers. They can also add or modify them at any time during the product development process, as long as they are clear and ready for selection in Sprint Planning.
References:
✑ [Scrum Guide], page 6, section “Product Owner”
✑ [Scrum Guide], page 11, section “Product Backlog”
✑ [Scrum Guide], page 10, section “Product Goal”
✑ [Scrum Guide], page 12, section “Product Backlog Refinement”
✑ [Scrum Guide], page 14, section “Sprint Planning”
During the Sprint Retrospective a Scrum Team has identified several high priority process improvements. Which of the following statements is most accurate?
(choose the best answer)
Correct Answer:
A
The Scrum Guide states that "By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the
inspection of the Scrum Team itself."1 This means that the Scrum Team may add the high priority process improvements to the Sprint Backlog for the next Sprint, as part of their plan to deliver the Increment and achieve the Sprint Goal. The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.1 References:
✑ 1: The Scrum Guide2, page 16
✑ 2: The Scrum Guide
What is a Product Owner typically responsible for during a Sprint? (choose the best two answers)
Correct Answer:
EF
The Product Owner is typically responsible for collaborating with
stakeholders, users, and customers to understand their needs and expectations, and to validate the value of the product. The Product Owner is also responsible for working with the Scrum Team on Product Backlog refinement, which is the act of adding detail, estimates, and order to Product Backlog items.1 These two responsibilities help the Product Owner to maximize the value of the product and the work of the Developers. References:
✑ 1: The Scrum Guide2, page 18
✑ 2: The Scrum Guide
True or False: The Product Owner makes sure the correct stakeholders are invited to the
Sprint Retrospective. They might have important instructions for team improvements.
Correct Answer:
B
It is not true that the Product Owner makes sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements. This is because:
✑ The Sprint Retrospective is an event where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The purpose of the Sprint Retrospective is to plan ways to improve quality and effectiveness.
✑ The Sprint Retrospective is an internal event for the Scrum Team only. It is a safe and confidential space where the Scrum Team can openly and honestly reflect on their strengths and weaknesses, and identify actions to improve their performance and collaboration.
✑ The stakeholders are not invited to the Sprint Retrospective. They do not have a say in how the Scrum Team works or what they should improve. The stakeholders can provide feedback and suggestions to the Scrum Team in other events, such as the Sprint Review or the Product Backlog refinement sessions.
✑ The Product Owner is a member of the Scrum Team who 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.
✑ The Product Owner does not make sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements. This would violate the self-management and autonomy of the Scrum Team and undermine their trust and empowerment.
References:
✑ [Scrum Guide], page 18, section “Sprint Retrospective”
✑ [Scrum Guide], page 7, section “The Scrum Team”
✑ [Scrum Guide], page 17, section “Sprint Review”
✑ [Scrum Guide], page 6, section “Product Owner”
✑ [Scrum Guide], page 10, section “Product Goal”
Several Sprints into a project, the Product Owner tells the Scrum Master that a key stakeholder
just started using the product. The stakeholder is unhappy with the quality of the product.
What are two good options for the Scrum Master? (choose the best two answers)
Correct Answer:
AD
If a stakeholder is unhappy with the quality of the product, the Scrum Master can coach the Product Owner on how to effectively communicate this concern to the Developers1. The Scrum Master can also encourage the Product Owner to put quality specifications on the Product Backlog1. This allows the Developers to understand the stakeholder’s expectations and work towards meeting them1. The Developers are responsible for building quality into the product, but the stakeholders (through the Product Owner) are responsible for setting what is expected in terms of product and process quality1.
