TK - Product Owner

The Product Owner (PO) is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. (source: Scrum Guide)

Product Owner (PO) is undoubtedly the "voice of the customer". PO owns the product end to end and is responsible for the overall product delivery. It is important to understand the characteristics or expertise of the Product Owner.

PO has the most challenging role of wearing multiple hats throughout the product development journey.

  • Communicator

  • Subject Matter Expert

  • End User Advocate

  • Business Advocate

  • Decision Maker

A Product Owner plays a crucial role in disseminating the vision and intent of the product, its detailed features, design and the single person to maximize the return on investment of product.

PO is tasked with conflicting goals, opinions and make decisive final call. For all practical purposes PO is the Owner of the Product Backlog. The end to end responsibility of managing, prioritizing and deciding what goes in and out of the backlog lies on the Product Owner.

The Product Owner is also accountable for effective Product Backlog management, which includes:

  • Developing and explicitly communicating the Product Goal;

  • Creating and clearly communicating Product Backlog items;

  • Ensuring that the Product Backlog is transparent, visible and understood;

  • Ordering the Product Backlog in such a way that it optimizes the value of work done by the development team;

  • Expressing the Product Backlog Items in detail;

  • Making sure that the Product Backlog raises transparency to the extent that it is clear what the Scrum team is going to work on next;

  • Raising the transparency of Product Backlog to a level where stakeholders can see how value is being added to the Product;

  • Helping Development Team with Product Backlog Items (PBI) refinement;

  • and,

  • Another important responsibility of the Product Owner is to define the "Acceptance Criteria" and ensure that they are met.

The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable.

Important note:

The Product Owner is one person, not a committee. The Product Owner may represent the needs of many stakeholders in the Product Backlog.

Those wanting to change the Product Backlog can do so by trying to convince the Product Owner.


Drone project example see: https://tcmarin.atlassian.net/wiki/spaces/DDMP/pages/494305351