The document discusses the product owner role in Scrum. It describes the product owner as planning the product using an "onion" model with layers representing the product, releases, iterations, and stories. The product owner is responsible for organizing the backlog, specifying acceptance criteria, communicating goals, coordinating stakeholders, and maintaining the backlog. The product owner acts as a subject matter expert, end user advocate, customer advocate, and business advocate.

1. Scrum’s Product Owner Role Jeff Patton Agile Product Design [email_address]

2. The product owner role comes from the specific Agile process Scrum © 2006-2007 Jeff Patton, All rights reserved, www.agileproductdesign.com It’s called “the snowman model” (see the snowman?)

3. The product owner plans the product in layers © 2006-2007 Jeff Patton, All rights reserved, www.agileproductdesign.com

4. The product owner plans the product in layers © 2006-2007 Jeff Patton, All rights reserved, www.agileproductdesign.com Product or Project What business objectives will the product fulfill? Product Charter Elevator Pitch Release How can we release value incrementally? What subset of business objectives will each release achieve? What user constituencies will the release serve? What general capabilities ( big stories ) will the release offer? Release plan Iteration What specifically will we build? ( user stories ) How will this iteration move us toward release objectives? Iteration Plan Story (Backlog Item) What user or stakeholder need will the story serve? How will it specifically look and behave? How will I determine if it’s completed? Story Details Acceptance Tests

5. The Planning Onion can grow to include product portfolios and business strategy © 2006-2007 Jeff Patton, All rights reserved, www.agileproductdesign.com Product or Project What business objectives will the product fulfill? Product Charter Elevator Pitch Release How can we release value incrementally? What subset of business objectives will each release achieve? What user constituencies will the release serve? What general capabilities ( big stories ) will the release offer? Release plan Iteration What specifically will we build? ( user stories ) How will this iteration move us toward release objectives? Iteration Plan Story (Backlog Item) What user or stakeholder need will the story serve? How will it specifically look and behave? How will I determine if it’s completed? Story Details Acceptance Tests Product or Project Release Iteration Story

6. The Planning Onion can grow to include product portfolios and business strategy © 2006-2007 Jeff Patton, All rights reserved, www.agileproductdesign.com © 2006-2007 Jeff Patton, All rights reserved, www.agileproductdesign.com Product or Project Release Iteration Story

7. The Planning Onion can grow to include product portfolios and business strategy © 2006-2007 Jeff Patton, All rights reserved, www.agileproductdesign.com Product Portfolio Business Strategy © 2006-2007 Jeff Patton, All rights reserved, www.agileproductdesign.com Product or Project Release Iteration Story