Agile Zone is brought to you in partnership with:

Mike is a certified PMP project manager and a certified ScrumMaster. Mike was involved with the creation of the DSDM Agile Project Leader certification, holds this certification at the Foundation, Practitioner, and Examiner levels. Mike was named an honorary member of the DSDM consortium and served on the board of APLN and the Lean Software and Systems Consortium. He currently co-leads the PMI Agile Community of Practice. Mike is a DZone MVB and is not an employee of DZone and has posted 147 posts at DZone. You can read more from them at their website. View Full User Profile

Why a Product Owner Team?

  • submit to reddit
The Product Owner Team is a construct used in many larger agile implementations to deal with the challenges of the Scrum Product Owner at scale. The specific makeup of the product team is highly dependent on the unique needs of the organization, and thus there doesn’t seem to be much consensus around how this team should be implemented.

That said… collectively, the people assigned to this team share the role of the Scrum Product Owner. To understand the role of a Product Owner team, let’s look at the role of Scrum Product Owner:

1. Create the product backlog
2. Prioritize the product backlog
3. Elaborate the requirements
4. Communicate the product vision
5. Represent external stakeholders
6. Participate in Scrum meetings
7. Inspect sprint outcomes
8. Change direction as necessary
9. Communicate progress
10. Terminate the sprint or release

While I might have one person that serves as the primary interface to the team, we are recognizing that the PO is a job that sometimes requires more than one person to do well.  Considering the Product Owner team from a slightly different perspective…. they serve as an enabler of the Scrum team (or teams) that the Product Owner might support. They are responsible for translating the needs of the business into user stories that are independent, negotiable, valuable, estimateable, small, and testable.

These user stories are ready to be consumed by the sprint teams with minimal discovery during the course of the sprint. This team is responsible for making the key decisions that the Scrum teams are not empowered to make by themselves… usually decisions where requirements dependencies span Scrum teams or where we have architectural dependencies (cross-cutting concerns) between teams.  One of my primary goals in implementing a Product Owner team is to increase clarity and reduce thrashing that often happens in larger, more complex product environments.

I’ve been advocating for Product Owner teams for a few years now.  Next post I’ll explore some of the roles and job titles that usually show up on these teams and how they play together on a complex product. 
Published at DZone with permission of Mike Cottmeyer, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)



Dus Jar replied on Thu, 2011/07/14 - 5:58am

Do you think we should also add PO as one who should also a. Define Value to be achieved and Sprint goals before the backlog Cheers.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.