The product owner is a key role in Scrum. But many organisations struggle to effectively apply it. This post wants to help you get it right by providing a concise overview of what it means to be the product owner.
As the name suggests, a product owner should own the product on behalf of the company. The individual is responsible for ensuring that a product creates value for its customers and users as well as the company providing it. You can think of the product owner as the person who champions the product, who facilitates the product decisions, and who has the final say about the product. I like to think of the product owner as an agile product manager, someone who looks after a product for an extended period of time and is responsible for achieving product success.
To fulfill this responsbilibity, a product owner has to connect with the users, collaborate with the development team, and understand how the company works. As the product owner, you should directly interact with the customers and users, the development team, and other key stakeholders, as the picture below shows.
I have circled the Scrum team, the unit consisting of product owner, ScrumMaster and development team in the picture above to indicate that the product owner should have a close and trustful relationship with the other Scrum team members: Scrum views the product owner as part of the wider Scrum team. This makes sense, as great products emerge when the product owner takes her market and business knowledge and collaborates with the development team.
In order to succeed, product owners require the right skillset: leadership, startegic, and tactical skills, as the following picture illustrates.
Leadership skills include empathy, vision, communication, decision-making, stakeholder management, and product ethics; strategic skills include product strategy and product roadmap, business model and financial forecast, KPIs, market research and validation, and product discovery; tactical skills, finally, include product backlog prioritisation and management, personas, user stories, product validation techniques, and technical understanding.
For more information, download my Product Owner Guide, a comprehensive yet concise summary of the role—just click on the image below:
Post a Comment or Ask a Question
38 Comments
The Product owner ultimately as the Voice of the Customer is responsible for the product and the prioritization of the backlog to deliver value early and frequently – But from working with the vision statement to the point where items are moved to the sprint backlog from the product backlog, it is a collaborative effort.
Thank you for your comment Mary. I would suggest that a product owner should be responsible for maximising the value a product creates, thereby ensuring that the product becomes or stays successful. I describe the collaboration between product owner and team as well as separate areas of responsibility in my article “Product Leadership in Scrum“. Hope this helps!
Managing a budget, being able to write usable user stories, crafting the vision, managing projects and a roadmap… I’ve never met someone being able to do it alone.
Shouldn’t we stop talking about Product Owner as a role, but rather as a function executed by different people (UX designer, Product Owner, Product Marketing Manager,…) , led by a Product Director / Senior Product Manager ?
Hi Sebastian, The suggestion Scrum makes is that product ownership is ultimately exercised by one person, the product owner. The product owner, however, should closely collaborate with a cross-functional team including a UX designer, developers, and testers. I have written more about single product ownership here: https://www.romanpichler.com/blog/the-single-product-owner/ It’s up to you to decide if a single product owner makes sense or not. What I do find crucial is that the people who create a product are empowered to make the necessary product decisions, for instance, which feedback is taken on board and which is not.
You forgot something…
With all these responsibilities, the Product Owner is also a chronically stressed individual, perhaps even dead.
I mean c’mon, give concrete examples of organisations beyond 1 simple product and < 20 employees where it is otherwise.
The overwhelming truth is that these roles rarely exist in one individual and worse still, it is dangerous to even have them in one individual. If they win the lottery and quit the organisation loses vision, support and product direction in one go.
I'm afraid to say that this is the type of theoretical dogma that does Scrum a disservice.
Hi Marc,
You are right to point out that product owners are sometimes overworked. One of the reasons is a lack of support from the team and the stakeholders, as I explain in my post “Avoiding Common Product Owner Mistakes”: https://www.romanpichler.com/blog/avoiding-common-product-owner-mistake/
While Scrum suggests that one individual ultimately owns the product, carrying out the visioning, product backlog grooming, and release planning work should be a collaborative effort – and not a solo act! Scrum suggests, for instance, that the team members reserve up to 10% of their availability per sprint to groom the product backlog and size its items.
When multiple teams are required to create a product, several product owners collaborate with one individual acting as the overall or chief product owner, as I explain in my post “Scaling the Product Owner”: https://www.romanpichler.com/blog/scaling-the-product-owner/
Hello Roman,
Your post is concise and so… helpful.
I’ve translated it into french :
http://www.fabrice-aimetti.fr/dotclear/index.php?post/2011/02/18/Le-Product-Owner-en-une-page
Regards,
Fabrice
Thanks Fabrice.
http://agilescout.com/infographic-what-is-a-product-owner-responsible-for/
You’ve been linked!
29 Trackbacks
The Product owner ultimately as the Voice of the Customer is responsible for the product and the prioritization of the backlog to deliver value early and frequently – But from working with the vision statement to the point where items are moved to the sprint backlog from the product backlog, it is a collaborative effort.
Thank you for your comment Mary. I would suggest that a product owner should be responsible for maximising the value a product creates, thereby ensuring that the product becomes or stays successful. I describe the collaboration between product owner and team as well as separate areas of responsibility in my article “Product Leadership in Scrum“. Hope this helps!
[…] It is written by a Roman Pichler, and I came across it through this article on his blog. […]
[…] the product owner leads this effort and carries out the necessary work together with a cross-functional team […]
[…] to share our top lean-agile tips/encouragements for for managers of requirements (i.e. the product owner role in agile […]
[…] tasked with creating the product should attend the canvas creation workshop: the product owner, the team developing and testing the product, and the ScrumMaster or coach […]
[…] a role that is focused on this effort that goes under-valued in many Scrum implementations. The Product Owner is the facilitator and gather of requirements and is there to synchronize all of the inputs into […]
[…] some product owners focus so much on the product details and the tactical level that other planning aspects are neglected […]
Managing a budget, being able to write usable user stories, crafting the vision, managing projects and a roadmap… I’ve never met someone being able to do it alone.
Shouldn’t we stop talking about Product Owner as a role, but rather as a function executed by different people (UX designer, Product Owner, Product Marketing Manager,…) , led by a Product Director / Senior Product Manager ?
Hi Sebastian, The suggestion Scrum makes is that product ownership is ultimately exercised by one person, the product owner. The product owner, however, should closely collaborate with a cross-functional team including a UX designer, developers, and testers. I have written more about single product ownership here: https://www.romanpichler.com/blog/the-single-product-owner/ It’s up to you to decide if a single product owner makes sense or not. What I do find crucial is that the people who create a product are empowered to make the necessary product decisions, for instance, which feedback is taken on board and which is not.
[…] and then there’s the development or Delivery team that does the work. In this case, the product owners of each team work together (in fact, in the picture to the right above, the prominent work area on […]
[…] to share our top LPD tips/encouragements for for managers of requirements (corresponds to the product owner role in agile […]
[…] “As the name suggests, a product owner should own the product on behalf of the company. You can think of the product owner as the individual who champions the product, who facilitates the product decisions, and who has the final say about the product.” — From https://www.romanpichler.com/blog/one-page-product-owner/ […]
[…] feature, but this is heavily skewed by longer times at the start of the project. In effect, as the product owner I know at the start of the day that the top for or five stories in our kanban backlog are likely […]
[…] needs to be addressed, the key features, and the value the product should create together with the product owner and the development team. We then explore and mark the areas of […]
What is a “product”?…
I got your point. But then I’m still a bit confused or wondered about PM & PO, should we still have PM in a scrum organization…. check the PO definition at http://www.scrum.org/Portals/0/Documents/Scrum%20Guides/Scrum_Guide.pdf, or http://www.romanp…
[…] help product owners and teams create new products […]
[…] roadmap [HT: RomanPichler] Related Posts You May Find Useful:Product Management LessonShould Developers Know the Business […]
[…] option for a business analyst is to take on the product owner role […]
[…] As product owners, we need a vision of where we want to take our product […]
[…] A single product owner is beneficial to enable effective decision-making. […]
[…] In an agile context, the product owner should manage the product roadmap. […]
[…] grooming the product backlog should be a collaborative effort that involves the product owner and the development team. […]
[…] The Product Owner on One Page (Roman Pichler) – This is a nice, simple drawing of a Product Owners key responsibilities in an agile environment. […]
[…] the product owner role can be challenging, as no two products are the same. […]
[…] as the product owner implies taking on many product management responsibilities including understanding the market, […]
[…] the product owner role can be challenging. The role is multi-faceted, has a wide range of responsibilities, and its […]
[…] the product owner role pragmatically: Spilt the role across several people or work with a product owner […]
[…] So the question is, how did the title “Product Owner” go from this high level general description as an overseer of the business interests for a given project, into what is a much larger singular role with broad strategic and tactical responsibilities that is described by the cartoon on this page. […]
You forgot something…
With all these responsibilities, the Product Owner is also a chronically stressed individual, perhaps even dead.
I mean c’mon, give concrete examples of organisations beyond 1 simple product and < 20 employees where it is otherwise.
The overwhelming truth is that these roles rarely exist in one individual and worse still, it is dangerous to even have them in one individual. If they win the lottery and quit the organisation loses vision, support and product direction in one go.
I'm afraid to say that this is the type of theoretical dogma that does Scrum a disservice.
Hi Marc,
You are right to point out that product owners are sometimes overworked. One of the reasons is a lack of support from the team and the stakeholders, as I explain in my post “Avoiding Common Product Owner Mistakes”: https://www.romanpichler.com/blog/avoiding-common-product-owner-mistake/
While Scrum suggests that one individual ultimately owns the product, carrying out the visioning, product backlog grooming, and release planning work should be a collaborative effort – and not a solo act! Scrum suggests, for instance, that the team members reserve up to 10% of their availability per sprint to groom the product backlog and size its items.
When multiple teams are required to create a product, several product owners collaborate with one individual acting as the overall or chief product owner, as I explain in my post “Scaling the Product Owner”: https://www.romanpichler.com/blog/scaling-the-product-owner/
[…] The product owner should lead the visioning work and involve the right people: the team members, the stakeholders, […]
[…] location to another to find an answer). Furthermore, Scrum emphasises the need for a dedicated Product Owner who can guide the team daily from a business perspective. All team members and customers are […]
Hello Roman,
Your post is concise and so… helpful.
I’ve translated it into french :
http://www.fabrice-aimetti.fr/dotclear/index.php?post/2011/02/18/Le-Product-Owner-en-une-page
Regards,
Fabrice
Thanks Fabrice.
[…] der Link zum Diagramm. Weitere Artikel zu diesem Thema: Product Backlog in […]
[…] been reading up heavily on Scrum as a development technique and came across this fantastic diagram. It gives a nice overview on one page of everything a Product Owner or Product Manager […]
http://agilescout.com/infographic-what-is-a-product-owner-responsible-for/
You’ve been linked!