Agile & Co: The 23 rules for a Product Owner

The role of the Product owner is the more difficult to endorse but also to understand.

The following 23 commandments will help you to understand what to do and what not to do when you are product owner

As a Product owner ...

... hold the vision for the product on behalf of the business, the customer, and the user.
... represent the interests of the business to the team.
... represent the product and the team to the business.
... communicate with stakeholders regularly.
... do not hold the role of scrum master.
... do not do implement work.
... write user stories and help others write user stories.
... understand the business value of each user story.
... assign numeric business value to each user story.
... prioritize the user stories into a strictly ordered backlog.
... identify acceptance criteria for each story.
... collaborate with the rest of the team to create the team's definition of done.
... accept or reject completed work, determining whether it has met the acceptance criteria.
... arbitrate conflicting requirements from stakeholders.
... do not tell the team how to do the work.
... provide the information that the team needs to estimate each story.
... make yourself available to answer the team's question about requirements and business value.
... do not estimate stories - that's the team's purview.
... make the call in the rare instances when a sprint needs to be terminated early.
... clarify requirements for the team.
... lead the first part of the sprint planning meeting
... lead the story time meetings
... gather feedback from stakeholders at the sprint review.

Courtesy of SM

Agile & Co