Each product has its own product owner, however these product owners belong to a structure with a higher level manager who discusses roadmap and priorities with stakeholders, but the detail of the backlog of each single product is managed by the specific product owner.
The Product Owner Manual is a short ebook available for free from ScrumSense. It discusses in a practiceoriented way the roles and techniques used by a product owner in Scrum teams, including the story writing principles and how to perform release planning. Scrum Inc. 's Chief Product Owner, Alex Brown, is in the midst of putting together a presentation on a modular way to scale scrum. He has noticed that when projects scaleup, one of the first issues organizations must confront is how to manage a Product Backlog across multiple teams.
Within the inner circle above, lies the Scrum Team. This includes the Product Owner, ScrumMaster and the Team. Within this boundary there should be no barriers to communication. This team is collectively held accountable for the success of the product, and there should be an open dialogue between all its members.
Therefore, if you have more than one team working on the same product, the product owner(s) will be the same for each team of said product. Since each product should have its own product owner(s), teams working on different products could have different product owner(s). Product owners, stakeholders, or customers can negotiate to end the Scrum project if they feel added value of the remaining product backlog items is too low to continue.
At the end of any sprint, the product increment will contain the highest value features, and be potentially shippable software complete with documentation. The Scrum Team really needs the person who is the Product Owner for that team to be fully committed to the Scrum Team and not have any distraction with membership in any other teams. Of course, the Product Owner for a Scrum Team may belong to other groups and communities within an organization.
The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are selforganizing and crossfunctional. Selforganizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Crossfunctional Jul 10, 2017 Multiple Development Teams, each with a Scrum Master, can draw from a single Product Backlog that must be owned by exactly one PO.
Although Scrum Masters and Product Owners can work for multiple teams, only the PO has this relationship with the Product Backlog.
This picture shows the same person might be the product owner for more than one Scrum team at the same time. Even if the concept of the lonely Product Owner that can discuss all topics and take all the decisions is appealing and could provide a better source of input for Scrum teams, this is however not always possible in the real world.
Mar 20, 2017 As part of the Scrum Tapas video series, Professional Scrum Trainer, Charles Bradley discusses ways that a Product Owner can spread their knowledge across multiple