The product's conductor. Neither developer nor manager, but a bit of both at the same time.
What exactly is a Product Owner?
The Product Owner (PO) is the person responsible for the product backlog within a Scrum team. Their role? Maximising the value delivered by the development team by making sure the right things are built in the right order.
They bridge business (stakeholders, customers) and the technical team. Concretely, they translate business needs into user stories that developers can understand.
The term comes from the Scrum Guide, written by Ken Schwaber and Jeff Sutherland. In that framework, the Product Owner is the single person accountable for the product's value. Not a committee, not a pair: one person who carries the vision and owns the decisions.
Day-to-day responsibilities
A Product Owner's daily life is varied. Here are the main missions that shape their days:
- Manage and prioritise the product backlog: this is the backbone of the role. The PO orders the backlog items based on business value, risk and technical dependencies.
- Write and refine user stories: every need must be formulated clearly, with precise acceptance criteria. The PO writes or co-writes these stories, then refines them with the team during refinement sessions. They are also the one who presents them during Planning Poker sessions so the team can estimate complexity.
- Define acceptance criteria: how do you know when a feature is "done"? The PO sets the validation conditions.
- Validate or reject deliveries at the end of the sprint: during the Sprint Review, the PO accepts or rejects the increments delivered by the team.
- Be available to answer the team's questions: an absent or unreachable PO means a blocked team. Responsiveness is essential.
- Communicate the product vision: the PO regularly shares the roadmap, quarterly objectives and product strategy with the team and stakeholders.
What a Product Owner is NOT
The PO isn't a project manager in the traditional sense. They don't manage developers, don't plan HR resources, and don't give orders to the team. They define the what; the team decides the how.
Nor are they just a ticket writer. The PO doesn't merely feed a backlog: they carry a vision, take strategic decisions and say no when needed.
Key takeaway: A good PO knows how to say no. It's even one of their most valuable skills: refusing a feature that doesn't create real value.
Product Owner vs Product Manager: the great confusion
These two roles are often confused, sometimes even merged in some organisations. Yet they cover different scopes.
The Product Manager (PM) focuses on long-term product strategy. They analyse the market, identify opportunities, define the overall vision, and work on the 6-12 month roadmap. Their main counterparts: leadership, marketing teams and customers.
The Product Owner operates at the development team level. They translate the strategy into actionable items, manage the backlog sprint by sprint, and make sure the team delivers value at every iteration. Their main counterpart: the Scrum team.
In small organisations, the same person often wears both hats. In larger organisations, the PM defines the "why" and the high-level "what", and the PO breaks that down into user stories and sprint-by-sprint priorities.
| Criterion | Product Manager | Product Owner |
|---|---|---|
| Horizon | Long term (6-12 months) | Short term (1-4 sprints) |
| Focus | Strategy, market, business model | Backlog, user stories, sprint |
| Counterparts | Leadership, marketing, customers | Scrum team, Scrum Master |
| Framework | Variable | Scrum |
The essential qualities
A good Product Owner combines varied skills:
- A clear and shared product vision: the PO must know where the product is going and be able to explain it simply to anyone.
- A sharp sense of priorities: not everything can be done at the same time. Knowing how to prioritise means knowing how to let go.
- Ability to communicate with techs AND non-techs: the PO is a constant translator between two worlds that don't always speak the same language.
- Availability and responsiveness: an unanswered question for three days means a developer blocked for three days.
- Courage to decide and own their choices: the PO makes decisions every day, sometimes unpopular ones. You have to own them.
- User empathy: understanding users' real problems, not only the ones imagined in a meeting room.
- Analytical mindset: knowing how to read product metrics (retention rate, NPS, conversion rate) to drive decisions.
How do you become a Product Owner?
There is no single path to becoming a PO. The role attracts very diverse profiles:
From development: experienced developers who want to get closer to the business. Their strength: they understand technical constraints and can evaluate the feasibility of a request.
From the business side: project managers, business analysts or functional consultants who migrate to agility. Their strength: they know the business domain inside out.
From design: UX designers who broaden their scope toward product management. Their strength: user empathy is already in their DNA.
From a dedicated education: more and more schools and trainings offer Product Management curricula (Master's in Product, specialised bootcamps).
In all cases, hands-on experience is irreplaceable. A good PO is shaped by working with Scrum teams, making prioritisation mistakes, and learning how to say no to the right people.
Certifications: PSPO, CSPO and the others
Several certifications validate Product Owner skills:
PSPO (Professional Scrum Product Owner) by Scrum.org. Three levels (PSPO I, II, III), taken online as timed multiple-choice exams. No mandatory training: you can take the exam directly. PSPO I is the most widespread and validates the fundamentals.
CSPO (Certified Scrum Product Owner) by Scrum Alliance. Requires a two-day training with a certified trainer. Less technical than the PSPO, more focused on understanding the role in an organisational context. Must be renewed every two years.
SAFe POPM (Product Owner/Product Manager) by Scaled Agile. Geared toward organisations using the SAFe framework. Covers both roles (PO and PM) in a scaled context.
Certifications open doors, but they don't replace experience. A certified PO without hands-on practice is still a theoretical PO.
How much does a Product Owner earn?
Salaries vary widely with experience, location and industry. Here are the common ranges in France (2025):
- Junior (0-2 years): EUR 38,000 to 45,000 gross/year
- Mid-level (3-5 years): EUR 45,000 to 55,000 gross/year
- Senior (5+ years): EUR 55,000 to 70,000 gross/year
- Lead PO / Head of Product: EUR 65,000 to 85,000 gross/year
In Paris and in tech, salaries are 10 to 20% higher. As a freelancer, the daily rate for an experienced Product Owner sits between EUR 500 and 800/day.
The most lucrative sectors are fintech, healthtech and SaaS software vendors.
The Product Owner's tools
A PO spends their days across several tools:
- Jira / Linear / Azure DevOps: backlog management and sprint tracking. The PO's daily cockpit.
- Confluence / Notion: product documentation, functional specifications, Sprint Review write-ups.
- Figma / Miro: collaboration with designers on mockups and user journeys.
- Mixpanel / Amplitude / Google Analytics: tracking product metrics to make data-driven decisions.
- Planning Poker: for estimation sessions with the team. Our online tool lets you start a session in one click, ideal for remote teams.
- Slack / Teams: daily communication with the team and stakeholders.
The Product Owner in SAFe
In the SAFe (Scaled Agile Framework) framework, the Product Owner's role is slightly different from the one described in the Scrum Guide.
In SAFe, the PO operates at the Team Level and focuses on writing stories and managing the Team Backlog. The product vision and roadmap are carried by the Product Manager, who operates at the Program Level and manages the Program Backlog.
This clear separation can frustrate POs used to having a holistic product view. In exchange, it helps structure work better in large organisations with several teams working on the same product.
The PO in SAFe also takes part in PI Planning (Program Increment Planning), large-scale planning ceremonies that bring together all the teams of a single train (Agile Release Train).
A typical Product Owner day
To better understand the role, here is what a regular day might look like:
9:00 — Review of messages and tickets raised by support. A critical bug? Straight to the top of the backlog.
9:30 — Daily standup with the team. The PO listens, clarifies blocking points and confirms the day's priorities.
10:00 — Refinement session. The team discovers the upcoming user stories, asks questions, identifies risks. The PO adjusts acceptance criteria in real time.
11:30 — Sync with the marketing stakeholder. They want a new feature for next month's campaign. The PO evaluates the request: is it aligned with the product vision? What impact on the current sprint?
14:00 — Metrics analysis. The conversion rate on the new sign-up flow dropped 12%. The PO digs into the data, formulates a hypothesis and writes an investigation ticket.
15:30 — Planning Poker session to estimate the stories of the next sprint. The team debates a ticket estimated between 5 and 13: a sign it should be split.
17:00 — Roadmap updates and preparation of tomorrow's Sprint Review.
The Product Owner is often described as the product's "mini-CEO". The comparison has its limits, but it captures the breadth of the role well: vision, decision, communication and responsibility.
