Separate accountability from doing every task
A Scrum Team includes a Product Owner, Scrum Master and Developers, with distinct accountabilities. The Product Owner is accountable for maximizing product value and effective Product Backlog management. The Scrum Master is accountable for establishing Scrum and the team’s effectiveness. Developers create the usable Increment and adapt their work toward the Sprint Goal. These descriptions help identify who remains accountable when a decision is difficult. They do not mean that collaboration stops at a role boundary or that one person must personally perform every related activity. Ask both who does a piece of work and who remains accountable for its outcome.
Product ownership can receive help
The Product Owner can delegate Product Backlog management work while remaining accountable. A Developer might help clarify a technical dependency, or another colleague might gather user feedback. That help does not create another Product Owner or transfer accountability to the helper. The Product Owner is one person, although the product can have many stakeholders with competing needs. A committee may supply advice and information; it does not become several simultaneous Product Owner accountabilities. When a case describes delegation, check whether accountability is still clear before calling the arrangement a violation. Doing work and holding accountability are related but different questions.
Worked example: conflicting customer requests
Fictional case: a subscription service receives requests from a large client and a group of smaller customers. The requests conflict, and the available usage evidence is incomplete. The Product Owner asks a Developer to investigate a dependency and a support colleague to summarize customer obstacles. That collaboration supplies evidence. The Product Owner still remains accountable for product value and effective backlog management. Neither the largest revenue contribution nor the shortest implementation estimate automatically settles the ordering. A Scrum Master can facilitate a productive discussion, but helping the discussion does not mean taking over the product decision.
Effectiveness includes organizational obstacles
The Scrum Master helps people understand and use Scrum and supports the Scrum Team’s effectiveness. An impediment might be inside the team’s current way of working or outside its authority. A cross-department policy that prevents verification of usable work can require organizational collaboration. Causing an impediment to be removed does not mean personally performing every task involved. It also does not authorize ignoring legitimate requirements. Identify who can act on the obstacle, help create a workable route and inspect whether the intervention actually improves progress. Avoid turning the Scrum Master into the default owner of every product or technical decision.
Transfer check: preserve the right owner
A Product Owner delegates the preparation of several backlog descriptions and then stops ensuring the backlog is clear or ordered. Is the problem the delegation itself? No. Delegation is permitted, but it has not removed accountability for effective management. State what is missing without inventing a rule that nobody else may help. In another case, executives disagree and ask the Scrum Master to become their product tie-breaker. Explain why a clearly accountable Product Owner is needed while stakeholder collaboration remains valuable. Practice the four linked decisions, comparing useful support with an actual transfer or loss of accountability.
A product’s largest customer asks for a feature, while other evidence suggests a different improvement may create more value. Who remains accountable for maximizing the product’s value and effective Product Backlog management?
- The Product Owner remains accountable for maximizing value and effective Product Backlog management. Stakeholder input and Developers’ knowledge are important evidence, but neither customer size nor technical effort transfers that accountability. The case does not give enough information to select the feature itself. It asks who must remain accountable while the competing evidence is considered, not whose opinion should always win.
Compare the other answer choices
A significant customer is an important stakeholder, but revenue size does not transfer Product Owner accountability.
The Scrum Master can help collaboration and effectiveness without taking over the product-value decision.
Developers contribute technical understanding, but effort alone is not value and does not transfer the Product Owner accountability.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
The Scrum Guide — November 2020