SkarpSkarp

Chapter 4 of 21

Scrum Accountabilities I: Product Owner and Product Backlog Ownership

Step into the Product Owner’s shoes and see how owning the Product Backlog, Product Goal, and value decisions shapes every Sprint and every exam scenario.

27 min readen

Step 1 – Putting the Product Owner in Context

From Team to Product Owner

You already met the Scrum Team. Now we zoom in on one accountability: the Product Owner, the person focused on product value inside the Scrum Team.

Canonical Definition

Memorize this for PSM I: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."

Value as the North Star

Everything about the Product Owner is about value: not busyness, not documentation, but the value of the product for customers, users, and the organization.

Inside, Not Above, the Team

The Product Owner is part of the Scrum Team, not a boss outside it. Stakeholders and managers influence, but do not replace, the Product Owner’s accountability.

Step 2 – Core Product Owner Accountabilities

Accountability Recap

The Product Owner’s core sentence again: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."

Backlog Content and Ordering

The Product Owner is accountable for what goes on the Product Backlog and in which order items appear. Others can suggest, but the Product Owner decides.

Transparency and Accessibility

The Product Owner ensures the Product Backlog and Product Goal are visible, understandable, and accessible to the Scrum Team and stakeholders.

Product Goal and Value Calls

The Product Owner owns the Product Goal and key value decisions: what to build next, when to release, and when to stop or pivot.

Step 3 – Product Backlog Ownership in Detail

Canonical Product Backlog Definition

Know this sentence: "The Product Backlog is an emergent, ordered list of what is needed to improve the product."

Emergent and Empirical

Emergent means the Product Backlog is always changing as we learn. This reflects empiricism: we inspect results and adapt the work.

Aligned to the Product Goal

Each significant Product Backlog item should move the product toward the Product Goal, the future state the Scrum Team plans against.

Single Source of Work

The Product Backlog is the single source of work for the Scrum Team. The Product Owner is accountable for keeping it clear and complete.

Step 4 – Ordering vs Estimating: Practical Scenarios

Ordering vs Estimating

Ordering = what comes first (Product Owner). Estimating = how big/complex items are (Developers). Exam questions often mix these up.

Scenario: Manager Reorders Backlog

If a manager demands a feature be top of the Product Backlog, the Product Owner must decide. Stakeholders influence, but do not order.

Scenario: Product Owner Sets Estimates

Even if the Product Owner is technical, Developers own estimates. The Product Owner can discuss effort but not impose numbers.

Exam Shortcut

Ask yourself: is this about value and priority (PO) or effort and complexity (Developers)? That split answers many questions.

Step 5 – Product Goal and Value Decisions

Product Goal Definition

Remember: "The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against."

Product Owner and Product Goal

The Product Owner is accountable for defining, communicating, and deciding when to change the Product Goal, based on value and learning.

Release Decisions

The Product Owner decides when to release Increments that meet the Definition of Done, balancing value, risk, and timing.

Stopping and Pivoting

Sometimes the highest value choice is to stop or pivot the product. That tough call belongs to the Product Owner.

Step 6 – Product Owner vs Stakeholders vs Management

Three Forces

Differentiate: Product Owner (value decisions), stakeholders (input and feedback), management (budgets and strategy).

Who Orders Work?

Only the Product Owner orders the Product Backlog. Others can influence, but cannot directly reorder it in Scrum.

Who Manages People?

The Product Owner is usually not a line manager. They own product decisions, not HR decisions.

Who Guards Scrum?

"The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide." They coach PO, stakeholders, and Developers.

Step 7 – Thought Exercise: Who Decides What?

Work through these mini-scenarios. For each, decide who must make the decision: Product Owner, Developers, Scrum Master, or “Outside Scrum” (e.g., line manager, HR, legal). Then compare with the guidance.

  1. Scenario A – Changing the Product Goal
  • Market research shows customers are abandoning the current product category.
  • The Scrum Team believes a new direction is needed.
  • Question: Who decides to change the Product Goal?
  • Guidance: This is Product Owner accountability. The Product Owner should listen to the Scrum Team and stakeholders, but the decision is theirs.
  1. Scenario B – Choosing how to implement a feature
  • A PBI says “Enable users to reset passwords via SMS”.
  • There are three technical options with different trade-offs.
  • Question: Who decides which technical approach to use?
  • Guidance: Developers decide how to turn PBIs into a usable Increment. The Product Owner can explain constraints (budget, compliance), but not dictate the technical solution.
  1. Scenario C – Reassigning a developer to another product
  • A manager wants to move a developer from this Scrum Team to a different project.
  • Question: Who has the authority to reassign the developer?
  • Guidance: This is usually outside Scrum (line manager or HR), though the Scrum Master may highlight the impact on the Scrum Team and product.
  1. Scenario D – Canceling a low-value feature mid-Sprint
  • During the Sprint, new data shows a feature in progress will not deliver value.
  • Question: Who decides to drop this feature from the Product Backlog?
  • Guidance: The Product Owner decides. The Scrum Team may still complete enough work to keep the Increment coherent, but future work on that feature can be removed from the Product Backlog.

Step 8 – Quick Check: Product Owner and Backlog

Test your understanding of Product Owner accountability and Product Backlog ownership.

Which statement best reflects the Product Owner's accountability regarding the Product Backlog?

  1. The Product Owner is accountable for ordering the Product Backlog, but Developers are accountable for its transparency.
  2. The Product Owner is accountable for the Product Backlog's content, ordering, transparency, and ensuring it is accessible.
  3. Stakeholders define the Product Backlog content, and the Product Owner communicates it to the Scrum Team.
  4. The Scrum Master ensures the Product Backlog is ordered to maximize value.
Show Answer

Answer: B) The Product Owner is accountable for the Product Backlog's content, ordering, transparency, and ensuring it is accessible.

The Scrum Guide makes the Product Owner accountable for maximizing value, expressed through the Product Backlog's content, ordering, transparency, and accessibility. Developers estimate and plan the work, and the Scrum Master coaches, but neither owns the Product Backlog.

Step 9 – Exam-Style Question: Ordering vs Estimating

Try this PSM I–style question about ordering and estimating.

During Product Backlog refinement, the Product Owner asks Developers to increase the estimate of a high-value item so that stakeholders will 'take it more seriously'. What is the best response according to Scrum?

  1. Developers should adjust the estimate because the Product Owner is accountable for maximizing value.
  2. The Scrum Master should change the estimate to keep neutrality.
  3. Developers should keep control of estimates and explain that estimates must reflect effort, not politics.
  4. Stakeholders should vote on the estimate to ensure alignment.
Show Answer

Answer: C) Developers should keep control of estimates and explain that estimates must reflect effort, not politics.

Developers are accountable for estimates. The Product Owner can discuss and challenge, but estimates should reflect actual effort and complexity, not political goals. The Scrum Master might coach both sides, but does not set estimates.

Step 10 – Flashcards: Core Definitions and Splits

Use these flashcards to reinforce key Product Owner and Product Backlog concepts. Try to answer from memory before flipping.

Canonical definition of Product Owner (must know for PSM I)
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
Canonical definition of Product Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
Who is accountable for ordering the Product Backlog?
The Product Owner is accountable for ordering the Product Backlog.
Who estimates the effort of Product Backlog items?
Developers are accountable for estimates, because they do the work and understand the effort.
What does the Product Goal describe?
The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
Who can decide to change the Product Goal?
The Product Owner decides to change the Product Goal, considering input from the Scrum Team and stakeholders.
Stakeholder influence vs Product Owner accountability
Stakeholders can request, suggest, and provide feedback, but only the Product Owner is accountable for Product Backlog content and ordering.
Who is accountable for establishing Scrum as defined in the Scrum Guide?
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
What is the Product Owner's role in release decisions?
The Product Owner decides when to release Increments that meet the Definition of Done, based on value, risk, and strategy.
Is the Product Owner necessarily the line manager of Developers?
No. The Product Owner is an accountability inside the Scrum Team focused on product value, not a people-management role by default.

Step 11 – Putting It All Together and Next Steps

Core PO Sentence

Keep this front of mind: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."

Backlog Ownership Summary

The Product Owner owns Product Backlog content, ordering, transparency, and accessibility. Others can help, but cannot own these.

Who Decides What

PO: what and why, Product Goal, ordering, releases. Developers: estimates and how. Scrum Master: establish Scrum. Managers: people and budgets.

Exam Strategy

When unsure on PSM I, ask: is this about value and priority (PO) or effort and implementation (Developers) or Scrum rules (Scrum Master)?

Key Terms

Scrum
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
Ordering
The act of arranging Product Backlog items in a sequence that reflects their relative importance, risk, and value, an accountability of the Product Owner.
Developers
Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
Empiricism
Scrum is founded on empiricism and lean thinking. Empiricism means decisions are based on observation, experience, and experimentation.
Estimating
Assessing the effort, complexity, or size of Product Backlog items, an accountability of Developers.
Scrum Team
The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
Stakeholder
Any person or group with an interest in the product, such as customers, users, managers, or regulators, who provides input but does not own the Product Backlog.
Product Goal
The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
Product Owner
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
Product Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
Definition of Done
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.

Finished reading?

Test your understanding with a custom practice exam on this chapter.

Test yourself