Product Backlog Management and Product Value in Scrum
Introduction
Product Backlog management starts with the outcome the product should achieve. If a bank wants more customers to resolve card disputes in its app, the Product Owner can order a small usable change early, then use support calls and completion data to see whether it helped. Feedback can change what comes next.
This PSM I lesson covers Product Value, Product Backlog Management, and Stakeholders & Customers in Scrum.org’s Managing Products with Agility focus area. You will practice ordering and refining items, evaluating their value, and keeping decisions with the appropriate accountability.
Learning objectives
- Explain that value is delivered through usable, valuable Increments and is inspected through empirical evidence.
- Describe the Product Owner's accountability for maximizing value and for effective Product Backlog management.
- Explain how the Product Backlog is ordered and why order is not the same as strict priority numbering or a fixed scope.
- Describe Product Backlog refinement: what it is, who takes part, how much to refine and when.
- Explain how the Product Goal gives the Product Backlog direction.
- Describe how Scrum Teams work with stakeholders and customers, and what the Scrum Master does to help.
- Recognise typical anti-patterns: committee-owned backlogs, a backlog that is a dumping ground, and refinement treated as a mandatory meeting.
1. What "value" means in Scrum
Value depends on what matters to customers, users, and the organization. A product may reduce waiting time, lower a cost, generate revenue, or reduce risk. The Product Owner is accountable for maximizing product value. At the outset, expected value is a hypothesis. Review user behavior, interviews, or other evidence after delivery to see whether it materialized.
The team can learn through experiments as well as delivery. A usable Increment gives stakeholders something concrete to inspect. The team can discuss its impact at the Sprint Review and use new information to adapt its Product Backlog.
Example: one feature, three kinds of value
A subscription video company considers a feature that lets viewers download episodes to watch offline. The Product Owner lists the possible value:
- Customer value: commuters can watch without mobile data.
- Business value: an estimated reduction of monthly churn from 4.0% to 3.6% on 500,000 subscribers, equivalent to about 2,000 fewer cancellations in a month at that subscriber count if the estimated change holds.
- Learning value: a first release for one platform shows whether downloads are actually used before the work is repeated on three more platforms.
The Product Owner ordered the first slice (Android, one catalogue) high in the Product Backlog because it delivers the most learning and a measurable outcome early. This is value-driven ordering, and it gives the Product Owner a way to check the estimate against actual use.
2. The Product Owner and the Product Backlog
The Product Backlog is the Scrum Team’s ordered list of work to improve one product. The Product Owner answers for its contents, ordering, and transparency, and communicates the Product Goal. Others can help write or clarify items. Stakeholders can propose changes and explain the expected outcomes. The Product Owner remains accountable for ordering. See Scrum artifacts and their commitments for how the Product Goal guides this artifact.
The Product Goal
The Product Goal describes a future state the Scrum Team can work toward. It sits in the Product Backlog and gives the team a basis for choosing and ordering work. The team completes or abandons one Product Goal before taking on another.
A usable Product Goal is concrete enough to guide decisions. "Be the best banking app" is not. "Let 80% of existing customers complete a card dispute in the app without calling support" is.
3. Ordering the Product Backlog
Ordering is deciding which work comes first. It can reflect value, risk, dependencies, cost of delay, learning, regulatory dates and other factors. The Scrum Guide does not prescribe a technique. The Product Owner chooses.
| Ordering factor | Question it answers | Example |
|---|---|---|
| Value | What helps customers or the business most? | Checkout speed raises completed purchases |
| Risk and uncertainty | What could invalidate our assumptions? | A new payment provider has an unproven API |
| Dependencies | What must exist before something else? | Single sign-on before personalised dashboards |
| Cost of delay | What do we lose per week by waiting? | A tax rule changes on 1 January |
| Effort | How big is it relative to the benefit? | A small change with a large effect first |
| Learning | What will we learn by building it first? | A thin slice that tests demand |
Common techniques exist, such as weighted scoring, cost of delay, Kano analysis, impact mapping, user story mapping and MoSCoW. They are tools the Product Owner may use. None is required by Scrum, and an exam answer that presents one of them as "the Scrum way" is wrong.
Worked example: ordering with cost of delay
Scenario. A Product Owner is ordering three initiatives across several Sprints. The Developers have estimated the work assuming the initiatives are done sequentially. Each can be broken into usable slices.
| Item | Estimated cost of waiting | Duration estimate | Constraint |
|---|---|---|---|
| A. New invoicing rule | EUR 20,000 per week after the deadline | 3 weeks | Deadline in 5 weeks |
| B. Referral bonus | EUR 8,000 in foregone benefit per week | 2 weeks | No hard date |
| C. Search redesign | EUR 6,000 in foregone benefit per week | 1 week | No hard date |
Step 1. Protect the deadline. A takes three weeks and needs to finish within five. Doing B first would leave no buffer. The Product Owner orders A first because the estimated duration and hard deadline make delay risky.
Step 2. Compare the discretionary items. One optional heuristic is to divide estimated cost of delay by duration. B scores 8,000 / 2 = 4,000 and C scores 6,000 / 1 = 6,000. Those scores favor doing C before B, assuming their estimates hold and neither depends on the other.
Solution. Order A, C, B. A’s penalty starts after the deadline, so treating it as a flat cost from today would be misleading. If scope or estimates change, the Product Owner can revise the order. The calculation informs the decision and does not replace discussion with the Developers or stakeholders.
4. Product Backlog items, size and "ready"
A Product Backlog item (PBI) can take many forms: user stories, use cases, experiments, defects, technical work and improvements. Scrum does not require any form. The Scrum Guide does not require the Product Backlog item to be a user story, nor "ready" as a formal gate, and it does not introduce a Definition of Ready.
Items at the top of the Product Backlog are usually smaller, clearer and more detailed than those lower down, because the Scrum Team will work on them sooner. Refinement helps the team judge whether an item can meet the Definition of Done within one Sprint. If it cannot, the team can split it or learn more before selection.
The Developers are responsible for sizing. The Product Owner may influence them by helping them understand and select trade-offs, but the people who will perform the work make the final estimate. Scrum does not prescribe story points, hours or any unit.
5. Product Backlog refinement
Refinement is the ongoing work of making items small and clear enough for a decision. The Product Owner can explain the outcome, Developers can identify dependencies and size the item, and a specialist can answer an open question.
Scrum defines no refinement meeting or duration. A team can use a regular session or refine in shorter conversations as questions arise. Start with items likely to be selected soon, and add detail when it will help make a decision.
Example: refinement that adapts
A Scrum Team working on an online grocery app holds a 45-minute refinement session on Tuesday of the second week of each Sprint. In one session they take the item "Customers can reorder a previous basket".
- The Product Owner explains the goal: customers who buy the same 15 items weekly should be able to repeat the order in under 30 seconds.
- Developers ask clarifying questions: what if an item is out of stock? What if the price changed? What about substitutions?
- The team splits the item into three smaller ones: reorder with all items in stock; reorder with substitutions; price-change notification.
- The Developers estimate the first as small and the other two as medium. The Product Owner orders the first near the top and the rest lower.
No one declared items "approved" by a gatekeeper. The result is a clearer, smaller, ordered set of items that supports an efficient Sprint Planning.
Comparison: refinement versus Sprint Planning
| Aspect | Refinement | Sprint Planning |
|---|---|---|
| Scrum event? | No, an ongoing activity | Yes, an event with a timebox |
| Purpose | Make items clear, small and ordered | Decide why the Sprint is valuable, what can be Done and how the work will be done |
| Output | More precise Product Backlog | Sprint Goal, selected items, plan |
| Who decides? | Product Owner and Developers collaborate | The entire Scrum Team collaborates |
| Timebox | None prescribed | At most eight hours for a one-month Sprint |
6. A living Product Backlog
The Product Backlog is never complete. As long as the product exists, so does its Product Backlog. It changes when market conditions, technology or understanding change. Several practices keep it healthy.
- Remove or archive items that no longer serve the Product Goal, instead of keeping a graveyard of 1,000 items. An item that stays untouched for a year is a candidate for removal.
- Keep one Product Backlog per product. Teams on the same product share the Product Backlog, Product Goal, and Product Owner.
- Keep it transparent. If stakeholders cannot see the order, they will try to influence the work some other way.
- Treat defects and technical debt as Product Backlog items when they are not fixed inside the Sprint, so the Product Owner can order them with everything else.
Pitfall: the backlog as a promise
Stakeholders sometimes read the Product Backlog as a contract with fixed scope and dates. It reflects what is known now, and the Product Owner can reorder it whenever evidence warrants a change. The Scrum Master teaches stakeholders that an item's presence in the backlog is not a commitment to deliver it.
7. Working with stakeholders and customers
Scrum assumes close collaboration with the people who use and pay for the product. Several parts of the framework create this contact:
- Use the Sprint Review to inspect the Sprint outcome with stakeholders and discuss what has changed. See how the Sprint Review supports adaptation.
- Refinement can include stakeholders or domain experts.
- Stakeholders can collaborate directly with the Scrum Team. Bring requests that affect Product Backlog ordering to the Product Owner.
The Scrum Master helps the Product Owner make goals and items clear, plan using evidence, and collaborate with stakeholders. For example, the Scrum Master can facilitate a discussion about conflicting requests while the Product Owner decides how to order them.
Table: stakeholder requests and the right response
| Situation | Weak response | Better response |
|---|---|---|
| A senior manager asks a Developer directly to add a feature | The Developer adds it quietly | Developer explains that requests go to the Product Owner, and tells the Scrum Master |
| Two departments both claim top priority | The Scrum Master picks | The Product Owner decides with stakeholders, the Scrum Master facilitates a transparent conversation |
| A customer wants a custom feature for one account | The team builds it at once | The Product Owner weighs it against the Product Goal and other value |
| Stakeholders want a fixed date and scope for six months | Promise it | Explain the empirical forecast; offer fixed date with variable scope, or the reverse |
8. Pitfalls and exam tips
Pitfall: the Product Owner as a messenger. A Product Owner who simply passes on stakeholder wishes does not maximize value. The Product Owner makes decisions and can say no.
Pitfall: Product Backlog owned by a committee. The Scrum Guide says the Product Owner is one person, not a committee. Committees may be consulted, but the order is one person's decision.
Pitfall: confusing refinement with an event. If an answer says refinement is a formal Scrum event with a required duration, it is wrong.
Pitfall: treating a Definition of Ready as mandatory. It is not in the Scrum Guide. A team may use such a checklist, but it must not become a gate that blocks collaboration.
Pitfall: the Scrum Master orders the backlog. The Scrum Master helps with techniques and transparency; the Product Owner orders.
Exam tip. When a question asks "who is accountable for ordering the Product Backlog?", the answer is the Product Owner, even if Developers do most of the writing. When it asks "who decides how much to select in a Sprint?", the answer is the Developers. When it asks about "the best next step" with an overloaded or unclear backlog, prefer answers that increase transparency and keep decisions with the right role.
Exam tip. Be wary of absolutes: "must", "always", "never" about techniques (story points, user stories, Definition of Ready, weighted scoring). The Scrum Guide prescribes accountabilities, events, artifacts and rules, not techniques.
9. Mini case study
Case. A Scrum Team builds a mobile app for a regional bank. The Product Backlog has 340 items, many two years old. The Head of Retail demands that her 12 requests take the top 12 places and threatens to escalate. The Developers say refinement is "a waste of time" and want a finished list of detailed requirements before they start any Sprint. The Product Owner is unsure how to react.
Questions. What should the Scrum Master do? What should the Product Owner do?
Commented solution.
- Product Owner. The Product Owner should remain the decision maker. They meet the Head of Retail, listen, ask about the outcomes behind the 12 requests, and evaluate them against the Product Goal and other value. Some may rise in the order; others may not. The decision and the reasons are made visible in the Product Backlog.
- Product Owner and Developers. The backlog needs cleaning. Items untouched for a long time are reviewed with stakeholders and removed or archived if no longer relevant. This shrinks 340 to a manageable list and makes the ordering transparent.
- Refinement. The Scrum Master coaches the Developers that "complete detailed requirements first" is not agile: details are added just in time as understanding grows, and the Developers' questions during refinement reduce waste. The team agrees how and when to refine, for example two short sessions each Sprint.
- Scrum Master and escalation. The Scrum Master helps the Head of Retail understand how the Product Owner makes ordering decisions, invites her to the Sprint Review where she can see progress and influence the Product Owner with evidence, and does not decide the order for the Product Owner.
Why the alternatives fail. The Scrum Master choosing the order takes over the Product Owner's accountability. Accepting all 12 requests removes the Product Owner's role and likely lowers value. Starting no Sprint until everything is specified ignores empiricism and delays feedback.
Key terms
- Value: benefit to customers, users and the organization, confirmed through observation.
- Product Goal: a long-term objective for the product; the future state the Scrum Team plans against.
- Product Backlog: an emergent, ordered list of what is needed to improve the product.
- Ordering: deciding the sequence of Product Backlog items; the Product Owner's decision.
- Refinement: the ongoing activity of adding detail, order and size to Product Backlog items.
- Sizing: estimating the effort of an item, done by the Developers.
- Stakeholder: a person outside the Scrum Team with an interest in the product.
- Cost of delay: the value lost per unit of time by postponing an item.
Summary checklist
- I can state that the Product Owner is accountable for maximizing value and for Product Backlog management, and is one person.
- I can explain that value is delivered in Done Increments and checked through empirical feedback.
- I know the Product Goal belongs to the Product Backlog and that a team works on one goal at a time.
- I know Scrum does not prescribe an ordering technique, item format, estimation unit or Definition of Ready.
- I can explain that refinement is an ongoing activity, not an event, and that the Scrum Team decides how and when to do it.
- I know the Developers are responsible for sizing.
- I can describe how the Scrum Master serves the Product Owner and facilitates stakeholder collaboration without taking decisions.
- I know several teams on one product share one Product Backlog and one Product Owner.
Sources
- The Scrum Guide, November 2020: https://scrumguides.org/scrum-guide.html (opens in a new tab) (sections "Product Owner", "Product Backlog", "Commitment: Product Goal", "Sprint Planning").
- Scrum.org, Professional Scrum Master I assessment: https://www.scrum.org/assessments/professional-scrum-master-i-certification (opens in a new tab)
- Scrum.org, Managing Products with Agility: https://www.scrum.org/professional-scrum-competencies/managing-products-with-agility (opens in a new tab)
