Scrums Product Owner Role Jeff Patton Agile Product

The product owner role comes from the specific Agile process Scrum It’s called “the

The product owner plans the product in layers © 2006 -2007 Jeff Patton, All

The product owner plans the product in layers Release Product or Project How can

The Planning Onion can grow to include product portfolios and business strategy Product or

The Planning Onion can grow to include product portfolios and business strategy Business Strategy

The Product Owner Is a: Subject Matter Expert Understand the domain well enough to

• Communicate Business Goals, Customer Goals, End User Goals • Coordinate involvement of

Sprint 0 Sprint 1 • planning • data gathering • design for iteration 1

Slides: 10

Download presentation

Scrum’s Product Owner Role Jeff Patton Agile Product Design jpatton@acm. org

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

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

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

The Product Owner Is a: Subject Matter Expert Understand the domain well enough to envision a product Answer technical questions on the domain for those creating the product End User Advocate Describe the product with understanding of users and use, and a product that best serves both Customer Advocate Understand the needs of the business buying the product and select a mix of features valuable to the customer Business Advocate Understand the needs of the organization paying for the software’s construction and select a mix of features that serve their goals Communicator Capable of communicating vision and intent – deferring detailed feature and design decisions to be made just in time Decision Maker Given a variety of conflicting goals and opinions, be the final decision maker for hard product decisions The Product Owner role is generally filled by a single person supported by a collaborative team © 2006 -2007 Jeff Patton, All rights reserved, www. agileproductdesign. com 8

• Communicate Business Goals, Customer Goals, End User Goals • Coordinate involvement of SMEs, users, and business stakeholders • Coordinate with other product owners to insure coherence of product and releases Product Owner Responsibilities Participate daily Evaluate product at end of Sprint and add or remove stories from backlog as necessary Be available to answer questions and clarify details on user stories Verify stories are done based on acceptance criteria Create and maintain the product backlog Organize the backlog into incremental releases Specify objective acceptance criteria for stories © 2006 -2007 Jeff Patton, All rights reserved, www. agileproductdesign. com 9

Sprint 0 Sprint 1 • planning • data gathering • design for iteration 1 features – high technical requirements, low user requirements • gather user input for iteration 3 features • design iteration 2 features • support iteration 1 development es tu r fe a ed implement iteration 1 features support dev n Development Team Sprint 3 • gather user input for iteration 4 features • design iteration 3 features • support iteration 2 development • validate iteration 1 features gn si in de d g e un in ur o st at s f te fe g ty bu ili + ab us g si de support dev re u at fe • development environment setup • architectural “spikes” Sprint 2 co d Product Owner Team Design and Coded Features Pass Back and Forth Between Tracks implement iteration 2 features fix iteration 1 bugs if any • gather user input for iteration 5 features • design iteration 4 features • support iteration 3 development • validate iteration 2 features implement iteration 3 features fix iteration 2 bugs if any time © 2006 -2007 Jeff Patton, All rights reserved, www. agileproductdesign. com 10