Differences

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

--- how_does_multi-tiered_product_management_work [2018/11/01 06:06] – created hpsamios
+++ how_does_multi-tiered_product_management_work [2018/11/01 10:23] – hpsamios
@@ Line 1: / Line 1: @@
 ====== How Does Multi-tiered Product Management Work? ======
+**WARNING: Work in Progress**
 Or “What is the difference between a Product Manager and a Product Owner?”
@@ Line 11: / Line 13: @@
 Before we get started, let’s make one thing perfectly clear. This is a discussion on how people should collaborate as they work the problem of deciding what value we can / should deliver next. This is not a reporting structure.
-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.
+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 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 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:
 {{ :wiki:5c32312e-812e-4dbe-ac67-34c5c6aa02d9.jpeg?500 |}}
-This is one way of positioning the differences in role (note: I am not talking about the different ceremonies different levels attend).
+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.
-{{tag>FAQ ProductOwner ProductManger Scaling SAFe}}
+{{tag>FAQ ProductOwner ProductManger Scaling SAFe WIP}}