User Tools

Site Tools


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
how_does_multi-tiered_product_management_work [2020/06/02 14:22] – external edit 127.0.0.1how_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:
  
 {{ 5c32312e-812e-4dbe-ac67-34c5c6aa02d9.jpeg?500 |}} {{ 5c32312e-812e-4dbe-ac67-34c5c6aa02d9.jpeg?500 |}}
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/how_does_multi-tiered_product_management_work.txt · Last modified: 2025/03/14 13:55 by hans