The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable. The word delegate mentioned above is open for interpretation now.
When do we say that the Product Owner may delegate, then to whom does he/she delegate this? The agile world has created a few roles like "Business Analyst, and "Proxy Product Owner" for this delegation.
There is now a defined clarity on what Business Analyst gets delegated, which is understanding the elements of the system and then internalizing them into the team's requirements which is responsible for creating the Product.
An emerging terminology to make the Product Owner's presence felt at every level of the Product Lifecycle is "Proxy Product Owner", I am not sure who did invent this terminology. The dictionary meaning of "Proxy" states - "the authority to represent someone else, especially in voting."
The synonyms of the "Proxy" are - Representative, delegate, agent, etc. So, with the above information, we can define "A proxy product owner as representing the role of the product owner without actually being that person themselves."
Scrum doesn't have the role of "Proxy Product Owner." The Proxy Product Owner role came into existence because of the complex corporate hierarchy and job titles. The existence of these roles is also a result of being in charge of making the decisions and controlling people working on the Product instead of managing the Product Lifecycle.
Ultimately, some destructive behaviors can come of this role – the worst of a power play by the person the proxy is operating for. The Proxy Product Owner role sometimes also gets concluded as a middleman role between the people making decisions about a product and developing it.
The decision-making lies with the Product Owner. Proxy Product Owner is not usually helpful in Product Development and is considered dysfunctional in the Organization developing the Products. The role of a product owner exists to maximize the value of the Product, keeping Product backlog Management simple.
Getting a person to represent the Product Owner, making a powerless admin role, and delaying the decision-making to make the product a success.
A Business Analyst may help understand and internalize system elements into team requirements, supporting the Product Owner's tasks.
A Proxy Product Owner represents the Product Owner without being the Product Owner themselves, typically due to complex corporate hierarchies.
No, Scrum does not officially recognize the role of Proxy Product Owner; it has emerged due to corporate structures and job titles.
The Proxy Product Owner role can lead to delayed decision-making, power plays, and a lack of clear accountability, which may hinder product development.
Sign up for Agilemania Newsletter
Stay updated with the latest Agile & Scrum trends.
Sumeet Madan
With a remarkable 18-year tenure in software engineering, agile training, coaching, and consulting, Sumeet's expertise is unparalleled. As a certified Professional Scrum Trainer (PST) from Scrum.org and a distinguished SAFe® Practice Consultant (SPC), Sumeet brings a wealth of knowledge and skill to every project, making a lasting impact on organizations seeking to embrace Agile methodologies.
