a·gen·tic a·gil·i·ty

Product Owners are not a myth

TL;DR; Explains the Product Owner role in Scrum, common challenges with proxies, and how support teams like Business Analysts can help manage large product backlogs effectively.

Published on
5 minute read
Image
https://nkdagility.com/resources/pgJ89XqQPZe
Subscribe

Product Owners are not a myth Steven Borg brought “ 5 Reasons Why a Product Owner Team Might Be a Good Idea ” to my attention which in turn lead me to read “ Is Scrum a –ism that doesn’t work for real? ”, and for me there seams to be a certain amount of “missing the point” and I wanted to try to find it.


Lets start with a definition of “Product Owner” from the Scrum Guide:

The Product Owner

The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes:

The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.

The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a backlog item’s priority must convince the Product Owner. For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner’s decisions are visible in the content and ordering of the Product Backlog. No one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn’t allowed to act on what anyone else says.

- The Scrum Guide

Being a Product Owner is a management role that does not involve managing people, they are instead managing the “what” that the Development Team are building. They don’t actually have to physically maintain the backlog, or even order it. They are however completely responsible for the backlogs content, order and understanding.

Why is everyone finding this so difficult to find?

When I am working with organisation on Scrum Adoptions I find it very easy to identify who the Product Owner should be with more difficulty involved in getting that person to accept that responsibility. I usually let the company lead themselves to the correct understanding of how that should happen as they are the ones that are best placed to figure it out.

We do Scrum but we use a Proxy Product Owner from IT because the Product Owner does not have time to be available for the team so the Proxy makes the decisions for the Product Owner and only gets their input when it is a big decision. Product Owners are not a myth Bad ScrumBut – Proxy PO’s never work out

I occasionally end up with a Proxy Product Owner and while this is defiantly a “ScrumBut” that results in the businesses order not being reflected in the backlog it is all too common. While, like all “ScrumBut” this has a negative result, as long as everyone understands the negative result and accepts it transparently then at least we can move on. The organisation will figure out evenly why it is not recommended but sometimes things need to learned rather than told.

Why would you not have a Product Owner team?

I don’t think that any part of Scrum negates the possibility of having a team of people who work for the Product Owner, in fact it positively encourages it. Just because the Scrum Guide does not explicitly say that something is true does not make it false. This is one of the reasons that many non-prescribed things have been stripped out of the Scrum Guide 2011 in the first place.

I can think of many circumstances where you may have both Project Managers and Business Analysts that work for the product Owner and provide some of the extra capacity that they may need because their backlog is too big.

We do Scrum but our Product Owner can’t understand and order the entire backlog because it contains over 900 items so the Product Owner has a team of Business Analysts to help him bring the important ones to surface Product Owners are not a myth Good ScrumBut - Although 900 items is too much overhead

My current customer has one product with over 900 items in their backlog. This would be impossible for a Product Owner to fully understand by themselves. They would need minions that can analyse that list and surface the most relevant items for the Product Owners consideration and ordering at the top of the backlog. Does this sound slightly like a Business Analyst roll to anyone else?

Although the Product Owner has accountability and responsibility for the “what” that the team is  creating they will often need help. This help can come in many forms. It may be the Development Team that helps the Product Owner in small organisations, or a more formal dedicated team that helps them at the enterprise level.

How does your Product Owner organise their time?

Smart Classifications

Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.

Subscribe

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Genus Breeding Ltd Logo

Genus Breeding Ltd

Healthgrades Logo

Healthgrades

Jack Links Logo

Jack Links

Brandes Investment Partners L.P. Logo

Brandes Investment Partners L.P.

Capita Secure Information Solutions Ltd Logo

Capita Secure Information Solutions Ltd

MacDonald Humfrey (Automation) Ltd. Logo

MacDonald Humfrey (Automation) Ltd.

Epic Games Logo

Epic Games

Philips Logo

Philips

Xceptor - Process and Data Automation Logo

Xceptor - Process and Data Automation

New Signature Logo

New Signature

Lean SA Logo

Lean SA

Graham & Brown Logo

Graham & Brown

CR2

Qualco Logo

Qualco

Microsoft Logo

Microsoft

Kongsberg Maritime Logo

Kongsberg Maritime

ProgramUtvikling Logo

ProgramUtvikling

Sage Logo

Sage

Ghana Police Service Logo

Ghana Police Service

Washington Department of Enterprise Services Logo

Washington Department of Enterprise Services

Royal Air Force Logo

Royal Air Force

New Hampshire Supreme Court Logo

New Hampshire Supreme Court

Department of Work and Pensions (UK) Logo

Department of Work and Pensions (UK)

Nottingham County Council Logo

Nottingham County Council

Xceptor - Process and Data Automation Logo

Xceptor - Process and Data Automation

Milliman Logo

Milliman

Genus Breeding Ltd Logo

Genus Breeding Ltd

CR2

Trayport Logo

Trayport

Teleplan Logo

Teleplan