4

I am developing a SaaS app using Scrum and wondering if there are any best practices when it comes to having multiple "Product Owners". This is because I am working with some "users" who will help balance requirement from potential users. Just wondering if this will ever work out.

So far it has been extremely taxing since each "Product Owner" seem to have an epic list of cards.

Improve this question
1
  • 3
    One Product Owner per project. Period.
    – Todd A. Jacobs ♦
    Sep 22 '14 at 15:14
5

Per the Scrum Guide Page 5:

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 Product Backlog item’s priority must address the Product Owner.

Improve this answer
1
  • I totally agree, except when the product is big enough to require something more like the Scaled Agile Framework or some such to manage. Then you typically have Product Owners empowered to make decisions inside a sub-set of the overall product.
    – Andrew Clear
    Sep 23 '14 at 22:46
2

Agreed, you will certainly have multiple stakeholders from in and out of the organization, but only one Product Owner -- whose role calls for her to represent and prioritize based on these various interests.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.