Gartner Blog Network


How to Staff the Product Owner Role

by Deacon D.K. Wan  |  March 26, 2018  |  Submit a Comment

The Product Owner is the sole person responsible for managing the Product Backlog, and maximizing the value of the product resulting from work of the Development Team.     As agile delivery methods become mainstream and more organizations move to the product delivery model, the role of product owner is becoming increasingly important — but also harder to fill.

 

How to Staff the Product Owner Role

ID: G00337955
Analyst(s): David Norton | Deacon D.K Wan

 
Product Owners Must Care About the Full Application Life Cycle

337955_0002

 

Product owner is a high-profile role that requires a variety of “soft” skills and demonstrable business experience. Application leaders responsible for agile product delivery must therefore select product owners carefully to maximize business value and achieve desired outcomes.
Learn how to

  • Ensure Product Owners Know Their Duties and Relationships and Communicate These to Other Stakeholders
  • Expect Product Owners to Become Customer Champions and Entrepreneurs
  • Require Product Owners to Care About the Entire Application Life Cycle
  • Ensure Product Owners and All Stakeholders Understand Each Other
  • Require Product Owners to Empathize With Customers and Show Entrepreneurship
  • Match Product Owners to the Products They Will Deliver

Category: 

Deacon D.K. Wan
Senior Director, Analysts, Research & Advisory
2 years at Gartner
24 years IT Industry

Deacon D.K Wan is the Senior Director, Analyst at Gartner Applications and Product Leadership. Experts in digital innovations, product management, partnership, payments,mobile & e-commerce,BD. Read Full Bio




Leave a Reply

Your email address will not be published. Required fields are marked *

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.