Study guide

7.3 Product Backlog Management

PSM I — Professional Scrum Master I Scrum.org

Track your progress as you read

Finished sections get a check mark.

1 Introduction & PSM I Exam Overview

1.1 Current PSM I Exam Facts 1.2 Scoring & Time-Management Strategy 1.3 The 2020 Scrum Guide Is The Single Source Of Truth 1.4 A Realistic PSM I Study Plan

2 Scrum Theory, Empiricism & Values

2.1 What Scrum Is (and Is Not) 2.2 Empiricism and Empirical Process Control 2.3 The Three Pillars: Transparency, Inspection, Adaptation 2.4 Lean Thinking: Reduce Waste, Focus on Essentials 2.5 The Five Scrum Values

3 The Scrum Team & Accountabilities

3.1 The Scrum Team 3.2 The Developers 3.3 The Product Owner 3.4 The Scrum Master 3.5 Scrum Master Services to Team, Product Owner, and Organization

4 The Scrum Events

4.1 The Sprint 4.2 Sprint Planning 4.3 The Daily Scrum 4.4 The Sprint Review 4.5 The Sprint Retrospective 4.6 Timeboxing and Empiricism Across the Events

5 Scrum Artifacts & Commitments

5.1 Artifacts & the Transparency Mandate 5.2 Product Backlog & the Product Goal 5.3 Sprint Backlog & the Sprint Goal 5.4 The Increment & the Definition of Done 5.5 Commitments Summary & Exam Traps

6 Developing People & Teams

6.1 Self-Managing Teams 6.2 Facilitation 6.3 Scrum Master Stances 6.4 True Leadership That Serves 6.5 Conflict & Organizational Change

7 Managing Products with Agility

7.1 Product and Value 7.2 Product Goal Management 7.3 Product Backlog Management 7.4 Forecasting and Release Planning 7.5 Stakeholders, Evidence, and Business Agility

8 Final Review & Exam Strategy

8.1 Common Misconceptions & PSM I Traps 8.2 2020 Scrum Guide Rapid Review 8.3 Question Tactics & Time Management 8.4 Last-Minute Checklist

7.3 Product Backlog Management

Key Takeaways Explain This Topic AI

A single product has one Product Backlog and one Product Owner, even when multiple teams work on it

The Product Owner is accountable for ordering the Product Backlog and keeping it transparent, visible, and understood

The Product Owner may delegate Product Backlog management work but remains accountable, and the whole organization must respect their decisions

Product Backlog refinement is an ongoing activity with no mandated timebox; the Developers who do the work size the items

Stakeholders provide input and feedback but do not own or reorder the Product Backlog; ordering criteria such as value, risk, and dependencies are professional practice, not a Scrum rule

Last updated: June 2026

The Single Product Backlog

The Product Backlog is an emergent, ordered list of what is needed to improve the product . It is the single source of work for the Scrum Team, and it is never "complete" — as long as the product exists and can be improved, the Product Backlog exists and evolves.

Quick Answer: One product has one Product Backlog and one Product Owner. The Product Owner is accountable for it, may delegate the work, orders it, and keeps it transparent. Refinement is an ongoing activity, not a mandated event, and the Developers size the items.

Hard Scrum Guide rules

The Product Owner is accountable for effective Product Backlog management , which the Guide enumerates as:

Developing and explicitly communicating the Product Goal.

Creating and clearly communicating Product Backlog items.

Ordering Product Backlog items.

Ensuring the Product Backlog is transparent, visible, and understood.

The Product Owner may have others perform this work but remains accountable for it. For the Product Owner to succeed, the entire organization must respect their decisions — these decisions are visible in the content and ordering of the Product Backlog and through the inspectable Increment at the Sprint Review. No one is allowed to tell the Developers to work from a different set of requirements, and the Developers are not allowed to act on what anyone else says over the Product Owner's ordering.

Ordering, Refinement, Sizing, and Transparency

The Scrum Guide does not prescribe how to order the Product Backlog. It requires only that the Product Owner orders it to best achieve goals and missions. In practice, professional Product Owners weigh several factors when ordering — and recognizing these as practice , not Scrum rules, is exactly what the exam tests:

Value — items expected to deliver the most outcome for users and the business.

Risk — pulling risky or uncertain items earlier so assumptions are tested while there is still time to respond.

Dependencies — sequencing so that enabling work precedes work that needs it.

Size / cost and learning needs — balancing quick wins against larger bets.

Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller, more precise items. It is ongoing , has no Scrum-mandated event or timebox , and the Developers who will do the work are responsible for the sizing of items. The Product Owner can influence the team by helping it understand and select trade-offs, but the people who will perform the work decide how large it is.

  • Activity Hard Scrum rule Supporting practice
  • One backlog per product Yes — single Product Backlog —
  • PO accountable, may delegate Yes —
  • Backlog transparent / understood Yes Tooling, layout, INVEST
  • Refinement is ongoing Yes (no mandated timebox) DEEP, slicing, story mapping
  • Sizing by the Developers Yes (the how is open) Story points, t-shirt sizes
  • Ordering criteria PO orders it Value / risk / dependency models
  • Stakeholder input and common traps

Stakeholders supply needs, input, and feedback — notably through the Sprint Review — but they do not own or directly reorder the Product Backlog. The Product Owner is the single accountable person, which protects focus and prevents a backlog "ruled by committee." A Scrum Master helps the organization respect this and coaches stakeholders to channel input through the Product Owner.

Two traps recur: (1) "Each Scrum Team on a product gets its own Product Backlog" — for multiple teams on one product there is still one Product Backlog and one Product Owner ; (2) "Refinement is a mandatory event with a fixed timebox" — it is an ongoing activity , not a formal Scrum event.

Transparency, Delegation, and the DEEP Heuristic

The Product Owner's accountability to keep the Product Backlog transparent, visible, and understood is what makes empirical product management possible: if the backlog is opaque or out of date, every decision made from it rests on a flawed picture, and inspection produces faulty adaptation. Transparency here is not optional polish — it is a precondition for the inspect-and-adapt loop to work at all.

A helpful (non-Scrum-Guide) professional heuristic for a healthy Product Backlog is DEEP :

Letter Meaning What it implies

D — Detailed appropriately Near-term items are well understood; distant items are coarse Don't over-specify work that may change

E — Emergent The backlog evolves as the product and environment change It is never "finished"

E — Estimated / sized Items carry a relative sense of size from the Developers The how of sizing is the team's choice

P — Prioritized (ordered) The Product Owner orders to best achieve goals Most valuable / risk-reducing items rise

DEEP is a practice , not a Scrum Guide rule — recognizing that on the exam is itself a tested skill.

Delegation without losing accountability

The Product Owner may delegate backlog work — for example, business analysts may write item details, or Developers may help slice and clarify items during refinement. What cannot be delegated is the accountability for the result. A common trap presents a scenario where the Product Owner has handed item-writing to others and asks "who is now accountable?" The answer remains the Product Owner . Similarly, a Scrum Master who reorders the backlog "to help" has overstepped: ordering is the Product Owner's accountability, and the Scrum Master serves by coaching the organization to respect it, not by taking it over.

Single backlog, single direction

When several teams share one product, a single ordered Product Backlog and a single Product Owner preserve one coherent direction. Split the backlog and you split the value accountability, lose the single ordered source of truth, and reintroduce the very coordination problems Scrum's structure is meant to dissolve.