Skip to main content

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company.

This usually happens by delivering and optimizing product features.

Product Manager

Product Owner

The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap.

The product owner is responsible for maximizing the value of the product by creating and managing the product backlog.

This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.    

Product Manager and Product Owner's work on below vacuum.



Product manager focus on:

  • Business Strategy
  • Long term Product Vision
  • Long term Product Strategy
  • Product Roadmap
  • Alignment with Product Owner
Product owner focus on:

  • Release Plan (Product Backlog ie: Epic)
  • Sprint Plan (Sprint Backlog ie: User Story)
  • Daily Scrum
  • Provide feedback to Product Manager

While the product manager has a highly strategic role and is accountable for the whole product lifecycle and customer-facing.
Product manager decides what products to build next.
Product Manager should spend half their time talking to customers, and half working with the product owner. 

The role of the product owner entails a more narrow focus and closer work with the development team.
Product owner helps the development team to build the products as per the goal set by the product owner.
Product Owner should spend half their time talking to product manager and customers, and half working with the team. 

In many large organizations that follow Scrum, product owners are very much part of the engineering department rather than the product department.
They may be called "product owners" but it might be more accurate to describe them as "product backlog owners" or "product backlog keepers".

In bigger companies, the product manager stands a level higher than the product owner and serves as a connector between the organization and the outside world.
This is why it's sometimes so hard to draw a line between the two positions or jobs.


Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .
Post a Comment
Read more