Let’s Put The “Own” Back In Product Owner

I published this article a couple of years ago on LinkedIn. Thought I would post it here as well…

When I see a Scrum team struggling one of the first places I look is the Product Owner (PO) role and more often than not I find the problem or at least part of it. Too often teams and organizations fail to understand just how critical the PO role is to the success of the team and the product.

The PO role is not an an administrative role it is a leadership role. While all the roles on a team are important the PO role is probably the most essential. Other than for very small or simple products or services the PO role is a full-time gig and not something that should be handled by a group or committee.

To say the PO role is challenging would be an understatement. Along with deep domain expertise the role requires someone who is an excellent communicator, delegator, relationship builder, collaborator, influencer, and decision maker. All key skills to establishing and maintaining trust and respect with the team, the customers/stakeholders, and organizational leadership.

Most of all though, the PO must truly own the vision of the product or service and have strong conviction to bring that vision to life. That vision is what will allow the PO to make the tough decisions he or she will face on an ongoing basis…