True or False: The Product Owner makes sure the Developers select enough from the Product
Backlog for a Sprint to satisfy the stakeholders.
Correct Answer:
B
The Product Owner does not make sure the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are the ones who determine how many Product Backlog items they select for a Sprint, based on their capacity and the Sprint Goal1. The Product Owner and the Developers collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog[3][3]. The Product Owner does not have the authority to tell the Developers how much work they should do, as this would
violate the principle of self-management4. References:
1: The Scrum Guide, November 2020, p. 6
2: The Scrum Guide, November 2020, p. 10
[3][3]: The Scrum Guide, November 2020, p. 6
4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
Who is responsible for the sizing of Product Backlog items? (choose the best answer)
Correct Answer:
D
According to Scrum.org, the Developers who will be doing the work are responsible for the sizing of Product Backlog items1. The Product Owner may influence the Developers by helping them understand and select trade-offs1. This implies that the Developers size the items after clarifying requirements with the Product Owner1.
True or False: Product Owners must create clear and unambiguous acceptance criteria for each Product Backlog item before it may be selected in Sprint Planning.
Correct Answer:
B
It is not true that a Product Owner must create clear and unambiguous acceptance criteria for each Product Backlog item before it may be selected in Sprint Planning. This is because:
✑ Acceptance criteria are a set of conditions that a Product Backlog item must satisfy to be accepted by the Product Owner or the stakeholders. They are used to verify that the item meets the expected quality and value standards.
✑ Acceptance criteria are not mandatory or prescribed in Scrum. They are one of the possible techniques that a Product Owner may use to communicate their expectations and requirements to the Developers and the stakeholders. They are not part of the Scrum Guide or the Definition of Done.
✑ Acceptance criteria do not need to be created before Sprint Planning. They can be created or refined at any time during the product development process, as long as they are clear and agreed upon before the item is considered complete. They can also be changed or updated based on feedback or new insights.
✑ The only requirement for a Product Backlog item to be selected in Sprint Planning is that it is sufficiently clear and ready for selection. This means that it has enough detail and precision for the Developers to understand what they are supposed to build and why. It also means that it has been refined and ordered by the Product Owner based on value and impact.
References:
✑ [Scrum Guide], page 14, section “Sprint Planning”
✑ [Scrum Guide], page 12, section “Product Backlog Refinement”
✑ [Professional Scrum Product Owner™ Training], page 7, section “Product Backlog Management”
A new Developer is having continuing conflicts with existing members of the Scrum Team,
which is impacting the delivery of the Increment. If necessary, who is responsible for removing
the Developer from the Scrum Team? (choose the best answer)
Correct Answer:
B
The Scrum Team is a self-managing unit that organizes its own work and delivers a valuable product1. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers2. The Scrum Team is accountable for creating a valuable, useful Increment every Sprint[3][3]. If a Developer is having conflicts with other team members that affect the delivery of the Increment, the Scrum Team is responsible for resolving the issue and deciding whether to remove the Developer from the team or not. The Product Owner, the Scrum Master, and the hiring manager do not have the authority to remove a Developer from the Scrum Team, as this would violate the principle of self-management4. References:
1: The Scrum Guide, November 2020, p. 5
2: The Scrum Guide, November 2020, p. 6
[3][3]: The Scrum Guide, November 2020, p. 9
4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
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”
