Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Transformation management and PMO

Product owner or product manager, two functions to distinguish before appointing anyone

In brief

In the Scrum Guide, the product owner is the person accountable for the value of a product and for its Product Backlog; product manager is a job title, absent from that guide, which in practice refers to the person in charge of a product's trajectory. Management Square compares product owner and product manager here (horizon, scope, counterparts, decisions) and describes the possible set-ups.

Page contents

The Scrum Guide defines the product owner and nowhere uses the term product manager. The SAFe framework defines both, and attaches the first to the function of the second. Outside these two texts, “product manager” is a job title, which each organisation fills in its own way. The question “product owner or product manager” therefore sets against each other two words that do not come from the same source.

In common usage, the product manager carries a product’s long horizon: who it is for, what problem it solves, what trajectory it follows. The product owner carries the order of a team’s work: what goes into the backlog, at what rank, and what waits. These are two functions, which can be given to a single person, to two, or to a product manager surrounded by several product owners. The set-up is chosen according to the number of teams and what each person has the power to decide.

One term in the Scrum Guide, two in the SAFe framework

The Scrum Guide (scrumguides.org, November 2020 version, read on 12 November 2026) describes only one accountability on this side: the Product Owner, “accountable for maximizing the value of the product resulting from the work of the Scrum Team” and for managing the Product Backlog. This management includes “developing and explicitly communicating the Product Goal”, which the Guide presents as “the long-term objective for the Scrum Team”. Read literally, the Scrum Product Owner therefore holds both the long horizon and the order of the backlog.

The SAFe framework splits these two responsibilities. The public part of its website (framework.scaledagile.com, read on the same day) presents the Product Owner as the member of the agile team primarily responsible for maximising the value delivered by that team, by ensuring that its backlog matches the needs of customers and stakeholders (page updated on 24 January 2025). It presents Product Management as the function responsible for defining “desirable, viable, feasible, and sustainable” solutions. According to this second page, updated on 15 October 2024, the function is generally held by Product Managers, who manage and prioritise the backlog of the agile release train (ART backlog). The rest of both pages requires an account and is not reproduced here.

The same name therefore refers to two scopes: an entire product in Scrum, one team’s backlog in SAFe. Outside these frameworks, the description of the product manager is a matter of usage and varies from one organisation to another.

The differences in practice, from horizon to decisions

When both job titles exist, common usage splits the responsibilities as follows. This table describes a convention, which each organisation adjusts; it reproduces no framework.

Product manager Product owner
Horizon The product over several quarters or several years: target, trajectory, business model or budget The next iterations and the current release
Scope A product or a range, whatever the number of teams One team’s backlog, or the product’s if there is only one team
Counterparts Customers and users, senior management, sales, marketing, finance The development team, key users, requesting business departments
Decisions The product’s objectives, what does or does not enter its trajectory, dropping an option The order of the backlog, the content of an iteration, acceptance of finished work
Keeps up to date The vision, the roadmap, the outcome objectives The backlog, its items and their acceptance criteria

This split reduces the product owner compared with the Scrum text: the value of the product and its long-term objective pass to the product manager. An organisation that adopts it departs from the Guide on this point. It is free to do so, provided it has written it down.

One person, two people, several product owners

The first set-up gives both functions to a single person. This is the reading of the Scrum Guide, and it suits a product served by one team, or a few. Its limit is time. Maintaining the backlog can fill the days to the point where the long horizon waits. Conversely, taken up by customers and senior management, the person can drift away from the team, which then looks for a substitute counterpart.

In the second, two people share the same product: the product manager keeps the trajectory, the product owner the backlog. The set-up works if a rule says who has the last word on the order of the backlog. According to the Scrum Guide, the Product Owner “is one person, not a committee”, and “the entire organization must respect their decisions”. Our reading follows from this: if the product manager can reorder the backlog, it is they who exercise the accountability the Guide calls Product Owner, and their colleague holds the backlog by delegation. The Guide allows this delegation: whoever delegates “remains accountable”.

The third combines one product manager with several product owners. It appears when several teams serve the same product, and the two texts do not answer in the same way. According to the Scrum Guide, they “should share the same Product Goal, Product Backlog, and Product Owner”. The SAFe website presents the Product Owner, for most organisations moving to agile, as a full-time role in each agile team, while Product Management prioritises the train’s backlog. Each product owner then orders their team’s backlog according to priorities set above them.

Product owner or product manager, a boundary to be written down

A job title does not say what its holder can decide. We suggest writing the boundary down on one page, decision by decision:

  • who sets the product’s objective, and who can change it;
  • who orders the backlog, and who can change that order;
  • who answers a department whose request is not taken up;
  • who decides the content of a production release;
  • who accepts finished work;
  • who arbitrates when two teams are both waiting for the same thing first.

Each line carries a single name. Two names on the same line signal a committee, or a decision that will be taken elsewhere.

Take an agricultural machinery manufacturer developing a maintenance application for its dealers. The product manager has put tracking of parts under warranty on the roadmap; a dealer first asks for an export of service interventions. If the page says that the product owner orders the backlog within the quarter’s objectives, they place the export after the warranty feature and explain this to the requester themselves. If the page says nothing, the request moves up from level to level until it finds someone who gives way.

Beyond job titles, the organisation between teams

Once there are several teams, the choice between two job titles gives way to organisational settings: one backlog or several, a body that arbitrates between teams, a way of handling their dependencies. One product owner per team, with no common priorities, can lead each team to optimise its own backlog.

These settings are the subject of our page agile at scale. The decision to adopt a framework is covered in our article on SAFe and scaled agile project management.

Before appointing anyone, the decision therefore concerns the set-up, then the page that writes down its boundary. On an existing product, this page is checked against a request recently refused or postponed: who said no, to whom, and did the answer hold. The job title is chosen last.

Insights

Further reading

All insights
Why do IT projects fail? A reading through the signs of drift

An IT project fails, under the convention adopted here, when it misses its deadline, its cost, its scope or the expected benefit beyond the variance its sponsor had accepted. Rather than a list of causes, Management Square offers a reading method here: the observable signs of drift at each stage of the project, what each one can reveal and the response it calls for.

Read the analysis
When to hold a project lessons-learned review, and when to forgo it

A project lessons-learned review is the examination, by those who took part in it, of what a project or a phase teaches for the future: end-of-project review, retrospective in an agile approach, post-incident review. Management Square offers a decision guide here: when to hold it, what to focus it on, whom to bring together, which conclusions to keep and to whom to entrust the follow-up, and when to forgo it.

Read the analysis
A programme's master schedule, built around decisions, dependencies and margins

A master schedule is, in common usage, the overall schedule of a programme or a large project, reduced to decision milestones, dependencies between projects and the margins that protect them. Management Square proposes here a construction in five stages, from scope to the update rule, and clarifies what separates it from a project's detailed schedule and who maintains it.

Read the analysis

FAQ

Frequently asked questions

Another question? Ask us

What is the difference between a product owner and a product manager?

The product owner (PO) is an accountability defined by the Scrum Guide: the person accountable for the value of the product and for managing the Product Backlog. Product manager (PM) is a job title, absent from that guide, which common usage gives to the person in charge of a product's trajectory: its target, its roadmap, its objectives. When both exist in an organisation, common usage gives the long horizon to the product manager and the order of the backlog to the product owner.

Who decides priorities, the product owner or the product manager?

The answer depends on the set-up chosen, and it is worth writing down. In the Scrum Guide, the Product Owner orders the Product Backlog and the entire organisation must respect their decisions. When a product manager sets the product's objectives, the product owner orders the backlog within those objectives. In our reading of the Guide, if the product manager can change that order themselves, it is they who exercise the Product Owner accountability.

Can the same person be both product owner and product manager?

Yes: product manager is a job title, product owner an accountability defined by Scrum, and an organisation can give them to the same person. The November 2020 Scrum Guide in fact gives the Product Owner alone the value of the product, the Product Goal and the Product Backlog. Combining them suits a product served by one team or a few; its limit is the time available to hold both the long horizon and the day-to-day work with the team.

Do you need one product owner per team?

The two reference texts do not answer in the same way. The Scrum Guide provides that several Scrum Teams working on the same product share the same Product Backlog and the same Product Owner. The SAFe framework website, read on 12 November 2026, presents the Product Owner, for most organisations moving to agile, as a full-time role in each agile team, attached to a Product Management function that prioritises the train's backlog (ART backlog). The choice depends on the number of teams and the framework chosen.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.