Product Ownership Group

From go-ELSE
Revision as of 00:58, 24 January 2024 by Ppugliese (talk | contribs) (Created page with "Where possible, even at scale there should be a single Product Owner being accountable for a product development and for achieving sustained end value. However, the experience of the agile community shows that there is a limit in the amount of Teams a single Product Owner can serve. Beyond that limit, there is the need of having a group of people sharing the role as a Product Ownership Group. There are severa...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Where possible, even at scale there should be a single Product Owner being accountable for a product development and for achieving sustained end value.

However, the experience of the agile community shows that there is a limit in the amount of Teams a single Product Owner can serve. Beyond that limit, there is the need of having a group of people sharing the role as a Product Ownership Group. There are several possible configurations for such a group, however there are two important key success factors:

  1. they share a collective accountability
  2. the number of people in this group should be kept to a minimum.