Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace:
how_does_multi-tiered_product_management_work

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
how_does_multi-tiered_product_management_work [2018/11/01 06:28] – hpsamioshow_does_multi-tiered_product_management_work [2025/03/14 13:55] (current) – hans
Line 2: Line 2:
  
 Or “What is the difference between a Product Manager and a Product Owner?” Or “What is the difference between a Product Manager and a Product Owner?”
- 
-====== Premise ====== 
  
 When people are working a large scale implementation of agile and they see definitions of the role of Product Owner and the role of a Product Manager (and the various other potential layers of working “content” priorities), they cannot help but feel confused. After all, they also seem to say “there is a backlog that needs to be prioritized” and that they “should work with customers”. How do we position the various roles? When people are working a large scale implementation of agile and they see definitions of the role of Product Owner and the role of a Product Manager (and the various other potential layers of working “content” priorities), they cannot help but feel confused. After all, they also seem to say “there is a backlog that needs to be prioritized” and that they “should work with customers”. How do we position the various roles?
Line 13: Line 11:
 But what you do find is that (for large implementation) you might need various levels of structure as there is too much to do for one person. For example if you are working as a Product Owner with a team, then to do this well will require full time work. In this case if the what you are delivering (eg Product, Solution, whatever) can be worked by a single team, then the Product Owner can work directly with customers, work the roadmap, etc. (Note: I am not talking about the different ceremonies different levels attend) But what you do find is that (for large implementation) you might need various levels of structure as there is too much to do for one person. For example if you are working as a Product Owner with a team, then to do this well will require full time work. In this case if the what you are delivering (eg Product, Solution, whatever) can be worked by a single team, then the Product Owner can work directly with customers, work the roadmap, etc. (Note: I am not talking about the different ceremonies different levels attend)
  
-But if the value you are delivering takes more than a couple of Teams, say 35 teams to deliver a soluton (OK, “35” was the number of teams I had when I first did an agile transformation) then a single Product Owner will not be able to take this one - you will need a team. Further you will need need to work at different levels to get a complete understanding of the requirements and priority. Take a look at:+But if the value you are delivering takes more than a couple of Teams, say 35 teams to deliver a soluton (OK, “35” was the number of teams I had when I first did an agile transformation) then a single Product Owner will not be able to take this on - you will need a team. Further you will need need to work at different levels to get a complete understanding of the requirements and priority. Take a look at:
  
-{{ :wiki:5c32312e-812e-4dbe-ac67-34c5c6aa02d9.jpeg?500 |}}+{{ 5c32312e-812e-4dbe-ac67-34c5c6aa02d9.jpeg?500 |}}
  
 This is one way of positioning the differences in role. You can see that there are a couple of axis here and that there are different involvements based on what your focus is and the impact you will have: This is one way of positioning the differences in role. You can see that there are a couple of axis here and that there are different involvements based on what your focus is and the impact you will have:
  
-  * A Product Owner will be more Team focused than Customer focused, making sure the Team really understands what the backlog and working through issues as they discover these, when they work with a customer it will often be a real end-user of the product so that direct feedback can happen as the work is completed, and the general time horizon that Product Owner worries about is about 2 weeks (and perhaps a couple extra out from that). The Product Owner's "currency" is the User Story. The Product Owner does their work in the context of the work Product Management.+  * A Product Owner will be more Team focused than Customer focused, making sure the Team really understands what the backlog and working through issues as they discover these, when they work with a customer it will often be a real end-user of the product so that direct feedback can happen as the work is completed, and the general time horizon that Product Owner worries about is about 2 weeks (and perhaps a couple extra out from that). The Product Owner's "currency" is the User Story. The Product Owner does their work in the context of the Product Management view of Features. 
 +  * A Product Manager is more Customer focused than a Product Owner. Like the Product Owner the Product Manager makes sure the Train (Team-of-teams) really understands what the program backlog and working through issues as they discover these, when they work with a customer it will often be a higher level than the real end-user of the product aimed at getting that direct feedback  as the work is completed. The general time horizon that Product Manager worries about is about a quarter and the roadmap that represents the next couple of quarter. The Product Manager's "currency" is the Feature. The Product Manager works with Product Owners to understand the Features so they can bring that work to the Team. The Product Manager does their work in the context of the Business Owner view of Epics. 
 +  * A Business Owner is mostly Customer focused and more business focused. In many contexts we want our Business Owners to be more entrepreneurial, to really take responsibility for the vision of the product or solution being developed. What this means is that they must be very customer focused as "no useful innovation happens in (your) office". They create an environment where the Trains and Teams are expected and trusted to do the right thing, because they have all the information they need to make good decisions in their context. The general time horizon of a Business Owner is about a year and they can represent and defend the roadmap that results from the Trains and Teams. The Business Owner's current is the Epic. The Business Owners work with Product Management on the total view of the Epics. 
 + 
 +====== Want to Know More? ======
  
 +  * [[what_are_the_characteristics_of_a_great_product_owner|What Are The Characteristics of a Great Product Owner?]]
 +  * [[http://www.hanssamios.com/dokuwiki/powerful_pictures#how_should_we_break_down_requirements|How Should We Break Down Requirements]]
  
  
-{{tag>FAQ ProductOwner ProductManger Scaling SAFe}}+{{tag>FAQ ProductOwner ProductManger Scaling SAFe WIP}}
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/how_does_multi-tiered_product_management_work.1541078897.txt.gz · Last modified: 2020/06/02 14:21 (external edit)