Misunderstood Stances of the Product Owner

The Product Owner accountability is commonly misunderstood. Here are some of the most common misconceptions:

• A proxy for stakeholders: While the Product Owner represents the stakeholders’ interests, they are not simply a mouthpiece for them. The Product Owner is responsible for making strategic decisions about the product and setting priorities based on the customer’s and the business’s needs.
• Unilateral decision maker: While the Product Owner has the authority to make decisions about the product, they should collaborate with the Scrum Team and stakeholders to ensure that a broad range informs decisions of perspectives and expertise.
• User story writer:  While user stories can help define requirements and features, this is only one aspect of being a Product Owner, and writing user stories should be a relatively small part of what they do if they are used at all.
• Solely accountable for success: While the Product Owner plays a critical role in the product’s success, they cannot achieve it alone. The Product Owner must work closely with the rest of the Scrum team, stakeholders, and other people in the producing organisation to ensure that the product is developed and delivered successfully and has value for customers and users.
• Only works on product development: While the primary focus of the Product Owner is on product development, they may also be involved in other aspects of product management, such as sales and marketing, to ensure that the product is successful in the market.

The role of the Product Owner is complex and multifaceted and involves much more than simply writing user stories or representing stakeholders. A successful Product Owner must have a broad range of skills and be able to balance the needs of the customer, the business, and the Scrum Team to deliver a successful product.