Blog‎ > ‎1. Scrum‎ > ‎3.Scrum Roles‎ > ‎

Scaled Product Owner


Scaling the Product Owner Role

Large Scrum Project consists of many small teams working together. Of course, one Product Owner cannot be the Product Owner for all the teams. Also rarely will a single Product Owner have all the knowledge about all business functions to be implemented or changed.

Generally, the following hierarchy is followed for large enterprise implementations.
Scaled Product Owner

Everyone asks me this question “But Product Owner is supposed to be ONE single person and not a committee, How can you have a hierarchy? Doesn’t it mean that you have a Product Owner committee?”

The answer to the question is that there is NO Product owner Committee that I am talking about. Each Product Owner is responsible for “The Product that he is responsible for”. Its not a group of people responsible for the Product.

In the above example there is a Product Owner for Accounts. The Product Owners who handle Savings Accounts vs Current Accounts (Business Accounts) work with the Accounts Product Owner. That means the “Accounts PO” is accountable for the entire product “Accounts”. The “Savings PO” is accountable for the “Savings Account” as a whole functionality and “Current Account PO” is accountable for “Current Account” as a whole functionality.

The Chief Product Owner is a role who is incharge of guiding the other Product Owners. This individual ensures that the needs and requirements are consistently communicated to the various teams and that the project-wide progress is optimized. This will also include facilitating collaborative discussion, decision making as well as having a final say if no consensus can be reached.

Sample Scrum Agile Video by Amit Kulkarni

Sample Training Video by Sateesh Kamat

 

Amit Kulkarni conducting Planning Poker Estimation Exercise

 

EPMC - Project Foundational Concepts by Sateesh Kamat