The Product Owner on One Page

Article Comments

1. Arran L. Hartgroves said on 18 Dec 10 05:10:
   I'm trying to get this role fully recognised in my organisation. It's surprising how many teams have product owners who only collaborate/elaborate with requirements. Getting the full role and responsibilities (and time commitments) is a hard sell, and I've noticed other roles e.g. BA adopting these activities due to ideal PO's being too busy. I might write about how component, non-user facing teams can get team members such as architects to adopt more of the PO role (within the technical community, their time is often easier to get and as they set the vision often where I work, they seemed a good choice). Would you agree with this?
2. Arran L. Hartgroves said on 18 Dec 10 05:10:
   I'm trying to get this role fully recognised in my organisation. It's surprising how many teams have product owners who only collaborate/elaborate with requirements. Getting the full role and responsibilities (and time commitments) is a hard sell, and I've noticed other roles e.g. BA adopting these activities due to ideal PO's being too busy. I might write about how component, non-user facing teams can get team members such as architects to adopt more of the PO role (within the technical community, their time is often easier to get and as they set the vision often where I work, they seemed a good choice). Would you agree with this?
3. Roman Pichler said on 20 Dec 10 04:03:
   Hi Arran, Fully establishing the product owner role is a challenging process for most organisations I have worked with. It takes time and support from the individuals playing the role and the leadership team. It sounds like your organisation may benefit from having product owners who take care of the strategic and market-facing activities as well as the tactical, development-facing ones. With regards to component teams, an architect or senior developer may be best suited to play the role as you suggest. But before you go down this route, consider employing feature instead of component teams. The former tend to be preferable for a number of reasons. For instance, they simplify product backlog grooming and product owner collaboration. Speaking of which: If you employ multiple teams, form a hierarchy of collaborating product owners one overall or chief product owner.