Why is it important that there is only one Product Owner per product? (choose the best three answers)

Question

Options

• AThe Scrum Master knows who acts as their backup while on vacation.
• BIt would confuse the stakeholders if they had to work with more than one person.
• CIt is clear who is accountable for the ultimate value of the product.
• DIt helps avoid barriers to effective communication and rapid decision-making.
• EThe Scrum Team always knows who determines the order of the Product

Explanation

Having a single Product Owner ensures clear accountability (C), efficient decision-making (D), and unambiguous Backlog ownership (E) - all core to how Scrum is designed to function. The Scrum Guide explicitly states the Product Owner is solely accountable for maximizing product value and ordering the Product Backlog; splitting that role across multiple people creates conflicting priorities and decision paralysis, undermining the entire purpose of having an empowered product authority.

Why the distractors are wrong:

• A is irrelevant - the Scrum Master's vacation coverage has nothing to do with the rationale for a single Product Owner.
• B contains a grain of truth but is not a primary Scrum principle; stakeholder confusion is a symptom, not the core reason. The real issue is accountability and authority, not just confusion.

Memory tip: Think of the Product Owner as a single point of truth for value. Just as a ship needs one captain to set course, the product needs one PO to set direction - multiple captains steer the ship in circles (conflicting backlog order), slow it down (delayed decisions), and leave crew unsure who's in charge (no clear accountability).

No community discussion yet for this question.