Product owner delegation is the Scrum Guide 2020 rule that a Product Owner may hand Product Backlog management work to others, such as Developers, while remaining accountable for the result. On the Professional Scrum Product Owner I (PSPO I) exam this shows up as a two-part test: can the work move (yes), and can the accountability move (no). Candidates who merge the two lose easy points.
Why Product Owner Delegation Matters on the PSPO I Exam
Delegation questions are accountability questions in disguise, and accountability is one of the most tested ideas in the Scrum Guide. PSPO I lists Product Backlog Management and the Scrum Team under its focus areas, so wording about who does the work versus who answers for it appears across many items.
| PSPO I fact | Value |
|---|---|
| Questions | 80 |
| Time limit | 60 minutes |
| Passing score | 85% |
| Fee | $200 USD per attempt |
| Format | Multiple choice, multiple answer, true/false |
Last verified: October 2026, on the official Scrum.org PSPO I page. At 85% you can miss at most 12 of 80 questions.
How the Scrum Guide Frames Delegation
The Scrum Guide 2020 separates the work of Product Backlog management from the accountability for it. In the Product Owner section it lists four activities: developing and communicating the Product Goal, creating and communicating Product Backlog items, ordering them, and keeping the backlog transparent and understood.
Right after that list, the Guide says the Product Owner may do this work or delegate it to others, and adds: "Regardless, the Product Owner remains accountable." (Scrum Guide 2020)
Three other lines in the same section complete the picture:
- The Product Owner is accountable for maximizing the value of the product.
- Those wanting to change the Product Backlog do so by trying to convince the Product Owner.
- The entire organization must respect the Product Owner's decisions.
The Guide also makes the Developers who will do the work responsible for sizing, so backlog collaboration is built in. For the wider backlog picture, see Backlog Management and Backlog Refinement.
Worked Example: The Overloaded Product Owner
A Product Owner looks after a payments product and spends most of the week with stakeholders and regulators. She asks the Developers to draft new Product Backlog items, split large ones during refinement, and propose an order for the next few Sprints.
Is this allowed? Yes. The Developers are doing delegated Product Backlog management work. What does not change:
- When a stakeholder disputes the order, the Product Owner answers for it.
- When the order seems to work against value, the Product Owner decides whether to change it.
- When the Sprint Review shows the product is drifting from the Product Goal, the Product Owner is the one accountable for correcting course.
A useful test: whose name is on the outcome? In Scrum, always the Product Owner's.
Why Each Wrong Option Fails
The LinkedIn version of this question offered four answers. Here is why three of them are traps.
| Option | Claim | Why it fails |
|---|---|---|
| Only the Product Owner may manage the Product Backlog | No delegation | Too rigid. The Guide explicitly allows others to do the work. |
| Yes, and accountability transfers to the Developers | Delegation moves accountability | Confuses doing with answering for. Accountability never transfers. |
| The Product Owner may delegate the work but remains accountable | Correct | Matches the Guide's wording. |
| Product Backlog management cannot be delegated to anyone | No delegation | Contradicts the Guide outright. |
The pattern repeats on the exam: absolute words such as only, never, and cannot are often wrong when the Guide grants flexibility.
What Practitioners Say
Practitioners agree the work can be shared and argue mostly about how much.
- In a 2019 Scrum.org forum thread on whether a Product Owner can delegate to the team, most replies treat accountability as non-transferable. One later reply (2020) argued writing user stories can be delegated but ordering should stay with the Product Owner, a stricter view than the Guide requires.
- Professional Scrum Trainer Mary Iqbal writes in a 2024 Scrum.org blog post that one person cannot detail every item, especially when several teams work on one product. Delegating item writing frees the Product Owner for strategy.
- In a 2023 Scrum.org article, Iqbal lists drafting items, maintaining the roadmap, and gathering metrics as delegable, while stressing that "the Product Owner ultimately remains accountable".
The shared view: delegation is a capacity tool, not an exit from the role. For the day-to-day side, see Product Ownership in Practice.
Common Misconceptions
- Delegating means the Product Owner is weak. The Guide offers delegation as a normal option, not a failure mode.
- A business analyst can become a proxy Product Owner. Others can do the work, but the Product Owner remains one person and keeps the accountability.
- Developers should not touch the backlog. Refinement is collaborative, and Developers own sizing.
Practice Questions
Question 1
A Product Owner asks the Developers to handle day-to-day ordering and refinement of the Product Backlog. Is this allowed?
- A) No, only the Product Owner may manage the Product Backlog
- B) Yes, and accountability transfers to the Developers
- C) Yes, the Product Owner may delegate the work but remains accountable
- D) No, Product Backlog management cannot be delegated
Answer: C. The Guide allows delegation of the work and keeps the accountability with the Product Owner.
Question 2
A senior stakeholder wants an item moved to the top of the Product Backlog. The Developers currently maintain the order on the Product Owner's behalf. What should the stakeholder do?
- A) Ask the Developers to reorder it, since they maintain the order
- B) Try to convince the Product Owner
- C) Raise it with the Scrum Master, who arbitrates priority
- D) Add it to the Sprint Backlog directly
Answer: B. Those wanting to change the Product Backlog do so by convincing the Product Owner, whoever maintains it day to day.
Question 3
Who is responsible for sizing Product Backlog items during refinement? (Choose the best answer.)
- A) The Product Owner
- B) The Scrum Master
- C) The Developers who will be doing the work
- D) The stakeholders who requested the items
Answer: C. The Scrum Guide gives sizing to the Developers who will do the work. The Product Owner may help them understand trade-offs.
Related Topics
- Definition of Ready Template: a team practice for making delegated refinement consistent.
- How to Pass PSPO I in 30 Days: where accountability questions fit in a study plan.
- Practise accountability scenarios on the PSPO I exam simulator.
FAQ
Can a Product Owner delegate Product Backlog management?
Yes. The Scrum Guide 2020 says the Product Owner may do Product Backlog management work or delegate it to others. In every case the Product Owner remains accountable for it.
Does delegating the backlog make the Developers accountable?
No. Accountability does not transfer with the work. Developers who write or order items act on the Product Owner's behalf, and the Product Owner still answers for the backlog's content and order.
Can the Product Owner role be shared by a committee?
No. The Scrum Guide states the Product Owner is one person, not a committee. The Product Owner may represent many stakeholders' needs, but one person holds the accountability.
What Product Owner work is most commonly delegated?
Practitioners most often delegate drafting and splitting Product Backlog items and gathering data for decisions. Ordering can also be delegated under the Guide, though many Product Owners keep it close because they answer for it.
Sources
- The Scrum Guide 2020, Product Owner and Product Backlog sections
- Scrum.org: Professional Scrum Product Owner I assessment
- Scrum.org forum: Can the Product Owner delegate responsibilities to the Development team?
- Scrum.org blog: Who writes Product Backlog items in Scrum? (Mary Iqbal, 2024)
- Scrum.org blog: Navigating Product Owner Accountability in Scrum (Mary Iqbal, 2023)
- InfoQ: Changes in the 2020 Scrum Guide, interview with Schwaber and Sutherland