Definition of the product owner
“The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.” The sentence comes from the Scrum Guide (scrumguides.org, November 2020; read on 12 November 2026), the text by Ken Schwaber and Jeff Sutherland that defines the product owner, abbreviated to PO.
On how to go about it, the Guide remains open: it “may vary widely across organizations, Scrum Teams, and individuals”.
It does not speak of a role when referring to the Product Owner. It defines “three specific accountabilities within the Scrum Team”: the Developers, the Product Owner and the Scrum Master. The French version renders “accountabilities” as “responsabilités” and “accountable” as “redevable”. It leaves the term itself in English, literally “owner of the product”, like Scrum Master or Sprint.
The Product Backlog, delegation and the power to decide
The Guide also makes the Product Owner accountable for managing the Product Backlog, “an emergent, ordered list of what is needed to improve the product”. In its terms, this management includes:
- developing and explicitly communicating the Product Goal;
- creating and clearly communicating Product Backlog items;
- ordering these items;
- ensuring that the Product Backlog is transparent, visible and understood.
The Product Owner may delegate this work, but remains accountable for it. They are “one person, not a committee”. The entire organisation must respect their decisions, visible in the content and ordering of the Product Backlog, and they alone have the authority to cancel a Sprint.
Product owner, project manager, product manager, proxy, SAFe: not to be confused
| Term | What it refers to | Source |
|---|---|---|
| Product owner | An accountability within the Scrum Team: the value of the product and the Product Backlog | Scrum Guide, November 2020 |
| Project manager | The person who answers for delivering a project: result, timescale, budget | Usage; absent from the Guide |
| Product manager | A job title: a product’s strategy, its market, its roadmap | Usage; absent from the Guide |
| Proxy product owner | A person who maintains the Product Backlog on behalf of a product owner | Usage |
The project manager, whose mandate is described in our article on the difference between a PMO and a project manager, leads a team, notably in a project-based organisation. The product owner, by contrast, does not assign work: the self-managing Scrum Team decides internally “who does what, when, and how”.
A job title and a Scrum accountability are not mutually exclusive: the same person can hold both. A proxy who cannot settle anything, on the other hand, departs from the person the Guide describes.
Finally, the SAFe framework uses the same name for a role that it defines itself. Its website (framework.scaledagile.com, page updated on 24 January 2025) defines it as the agile team member primarily responsible for maximising the value delivered by the team, by ensuring that the team’s backlog matches the needs of customers and stakeholders (our paraphrase). There, the role belongs to a broader function, Product Management. The rest of the page requires an account; our SAFe entry presents the framework.
A waiting list before a referral scheme: an example of arbitration
Imagine a chain of gyms developing its booking app. Marketing asks for a referral scheme, the gym managers for a waiting list. The product owner puts the waiting list at the top of the Product Backlog, because it serves the Product Goal. The marketing director may try to convince the product owner, as the Guide provides; the director does not change the Product Backlog themselves. The acceptance criteria can then be written as behaviour-driven development scenarios.
When several Scrum Teams work on the same product, the Guide gives them the same Product Goal, the same Product Backlog and the same Product Owner. As teams multiply, keeping to this rule becomes the organisational matter addressed on our agile at scale page.