A Scrum Team has been working on a product for nine Sprints. A new Product Owner comes in, understanding he is accountable for the Product Backlog. However, he is unsure about his responsibilities…

Question

Options

• AEnsuring that the most valuable functionality is produced first, at all times.
• BInteracting with stakeholders.
• CProviding the Development Team with detailed specifications.
• DDescribing features as Use Cases.
• ECreating detailed functional test cases.

• A
  88% (43)
• C
  6% (3)
• D
  4% (2)
• E
  2% (1)

Explanation

According to the Scrum Guide, the Product Owner is solely responsible for maximizing product value, which means continuously ordering the Product Backlog so the most valuable items are worked on first (A). The PO also serves as the primary liaison between the Scrum Team and stakeholders, collaborating with them to understand needs and communicate progress (B).

Why the distractors are wrong:

• C is incorrect because Scrum deliberately avoids detailed specifications - the PO defines what and why, while the Development Team determines how. Handing down specs is a waterfall/project-manager behavior, not a Scrum PO behavior.
• D is wrong because Scrum prescribes no specific format for backlog items. Use Cases are a legitimate technique, but they are not a Scrum requirement, and mandating them would contradict Scrum's format-agnostic approach.
• E is wrong because creating detailed test cases falls to the Development Team (which owns quality). The PO may define acceptance criteria, but writing functional test cases is not a PO responsibility.

Memory tip: Think of the PO as the "Value + Voice" role - they guard value (ordering the backlog for maximum impact) and are the voice of the customer/stakeholder. Any answer that pushes them into technical writing tasks (specs, test cases, prescribed formats) is a distractor.

No community discussion yet for this question.