A number of agile brands downplay the need for business analysis and requirements management on agile projects, putting large store in the role of the Product Owner.  This paper tackles some of the problems this misconception can result in and shows how effective product ownership almost always requires a team with a variety of skills and backgrounds to be effective.

Product Ownership requires clarity of vision, alignment with organizational strategy, understanding of the development process and the ability to communicate with a wide variety of stakeholders across all levels both inside and outside the organization.  The complexity of the role is most often more than a single person can (or should) cope with – effective product ownership requires a teamwork approach covering a variety of skills and knowledge.

 
 

Outline/structure of the Session

This interactive tutorial has participants explore aspects of the Product Owner role and identify the common challenges associated with the role.

The presenter then explores various project types and how they impact on project activities, and introduces the concept of Product Ownership as a team activity needing multiple capabilities and skills, which may require multiple people to collaborate to deliver the value needed for the team. 

The participants discuss the implications of this concept and how it could apply in their own organisation.

The talk then explores the "shape" of a healthy backlog and how it is important to treat the backlog as a funnel rather than a lengthy list of user stories.

It then explores the concept of tracking value delivered as well as velocity and shows the shape of a healthy value curve.

Participants discuss how this can be applied in their own organisations.

It then presents the audience with a set of tools they can use in their own organisations to identify and present value in an initiative.

  • Purpose Alignment model
  • Value stream mapping
  • Vision box
  • Sliders

Learning Outcome

  • The Product Owner role is good, but flawed
  • Project environments are complex and varied
  • Product Ownership needs a team with diverse skills and viewpoints
  • Put value first
  • A Backlog is more (and less) than a long list of user stories
  • There are tools and techniques which can help

Target Audience

Product Owners, Business Analysts, Customer Representatives, Product Managers, Project Managers

Requirements

Ideally the participants will be seated in tables in groups so they can easily participate in the discussion aspects of the session

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal