Skip to content

Latest commit

 

History

History
85 lines (54 loc) · 7.01 KB

Product_Management_vs_Product_Ownership.md

File metadata and controls

85 lines (54 loc) · 7.01 KB

Product Manager vs Product Owner

Table of contents

What is a product manager?

A product manager is the person who identifies the customer need and the larger business objectives that a product or feature will fulfill, articulates what success looks like for a product, and rallies a team to turn that vision into a reality.

A product manager sits at the intersection of business, technology, and user experience. Product Managers need to balance all of those three needs and make hard decisions and trade-offs. Product Managers (PMs) are usually referred to as the "CEO of the product" because they set the goals, define success, help motivate teams, and are responsible for the outcome.

What are a Product Manager's responsibilities?

In larger organizations, PMs are embedded within teams of specialists. Researchers, analysts, and marketers help gather input, while developers and designers manage the day-to-day execution, draw up designs, test prototypes, and find bugs. These PMs have more help, but they also spend more time aligning the stakeholders behind a specific vision.

PMs at smaller organizations spend less time getting everyone to agree, but more time doing the hands-on work that comes with defining a vision and seeing it through.

In general, a good PM will spend their time on a handful of tasks such as:

  • Understanding and representing user needs.
  • Monitoring the market and developing competitive analyses.
  • Defining a vision or roadmap for a product
  • Aligning stakeholders around the vision for the product.
  • Prioritizing product features and capabilities.
  • Creating a cross-functional team to empower independent decision-making.

What is a Product Owner?

A product owner is a Scrum team role that's accountable for the product's outcome and responsible for maximizing its value.

As a member of the Scrum Team, the Product Owner provides clarity to the team about a product's vision and goal. All work is derived and prioritized based on the Product Goal in order to deliver value to all stakeholders including those within their organization and all users both inside and out. Product Owners (POs) identify, measure and maximize value throughout the entire product's lifecycle.

What are a Product Owner's responsibilities?

The PO is accountable for effective Product Backlog management, which includes:

  • Listening to customers and turning their problems and complaints into user stories that create actionable items. They prioritize these stories and then arrange them in the product backlog.
  • Building and setting production process priorities to make sure the development team knows specifically what thing to focus on in order of importance
  • The PO is present at all team meetings with other internal stakeholders such as the scrum master to make sure that the whole development process is following the product roadmap created by the PM.
  • They are the communication link between the customer and the development teams. The PO is the embodiment of the customer's voice
  • Giving constructive feedback on the ratified roadmap. This is a communication link between the PO and the PM.

The PO may do this work or delegate the responsibility to others on the Scrum Team. Regardless of who does the work, the PO remains accountable for it being accomplished and for the value delivered.

It is critical for the PO to earn the respect of the entire organization in order to get the support they need for the decisions they make. These decisions need to be transparent in the Product Backlog.

The PO is one person who represents the needs of many stakeholders in the Product Backlog. If someone in the organization wants a change in the Product Backlog, they need to discuss this with the PO and try to convince them. Ultimately, the PO makes that decision. The PO should also be getting feedback from customers on the product.

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

A PM is with the product from conception to launch. However, the PO role has a narrower focus when it comes to working with the development team.

The PM studies the customer's wants and needs, whereas the PO makes sure that product development is following the product roadmap. The PM decides what is going to be built or adapted and the PO makes sure the development team does just that.

Product Manager Product Owner
This role is all about the big picture for a product with the whole long-term project in mind. A role that looks at the smaller details rather than the big picture. Short-term focus.
The vision of the product. Making product vision into an actionable backlog.
Customer understanding. Advocate for the customer's needs.
Prioritize features. Highlights needs for the development of a team.
Product roadmap. Backlog, epics, and user stories.

Basically, PMs are strategic, while POs are more tactical. There are some similarities between both roles. For example, they guide the product through the development process and work with several of the same teams across the organization.

In some cases, a PO might take on some of the more strategic roles of a PM, and vice versa. But in a prototypical agile organization, the team will have both POs and PMs, each responsible for some variation of the functions listed above.

In that sense, a PO is a type of PM - more tactical, more internal-facing - who helps keep the product's progress on track in an agile organization.

It is important to note that there is often an overlap between PO's and PM's. In fact, they often get misnamed in start-up companies where a PM can take on the role of PO or vice versa. Product Management is a relatively new field, which is why many are trying to find their footing with the correct naming conventions.

Additional Resources