Resources > Articles

Product Ownership: From Roadmaps to Backlogs

Post Author
  • John Milburn is CEO of Practical Growth Strategies LLC, where he and his team help companies to apply and implement market-driven principles. Prior to this, he was an instructor at Pragmatic Institute and has held executive and individual contributor roles in development, sales, and product management from startups to Fortune 100 companies.

Product Ownership: From Roadmaps to Backlogs

Who owns the product? For a long time, most technology firms delivered products in a waterfall method, a fairly straightforward way to define, build, test and deliver products. Product management, development and product marketing roles and titles were clearly defined and ownership was fairly clearly understood.

But as the majority of development organizations moved to iterative development methodologies—such as agile and scrum—new titles, deliverables and processes emerged. It’s true that these changes often result in improved team interaction, greater visibility of project progress, greater flexibility to adjust to change, and more inclusive, open organizations. But there’s often a downside too: The new processes introduce resource and expectation gaps, causing confusion about ownership and accountability.

With this shift, organizations see two significant challenges:

1.  New roles are introduced without changes in staffing. These roles are fairly well defined and are important in the new processes, but they don’t come free. To be effective, they usually demand additional time and new skills. Yet, existing personnel are often asked to cover their old roles while taking on new ones. Specifically, product managers are also asked to be product owners; project managers are also asked to be scrum masters; business analysts are asked to track development velocity; and user-experience designers are required to spend more time in the office and less time with actual users.

strong>2. More time is spent on internal meetings than on the market. This increased emphasis on process often results in companies losing touch with the market and becoming more inside-out in their thinking. Pragmatic Institute emphasizes that nothing important happens inside the office (NIHITO), but internal demands and new processes (e.g., daily stand-ups) move many organizations even farther from the market.

One way to reduce this confusion and ensure we don’t lose touch with the market is to clarify ownership and expectations by identifying key activities, outputs and deliverables, and then selecting the most suitable person to own each of them. Let’s focus on outputs and skills, not titles. This helps us answer questions like:

  • Can the business analyst act in the role of product owner?
  • Do we need a project manager and a scrum master?
  • What are the “handoffs” between each group, and who approves them?

ownership thumb

This partial list of release activities on the following page will help you get started. Sit down with the cross-functional team, review each item in detail and assign a primary owner for the function. Download >

By following these steps, organizations can more clearly articulate the expectations of each role. Leadership will not only become more clear about ownership and accountability, but it will be better informed about where teams are spending their time and can make the necessary tradeoffs to ensure there is still time in the market.

Author

  • John Milburn is CEO of Practical Growth Strategies LLC, where he and his team help companies to apply and implement market-driven principles. Prior to this, he was an instructor at Pragmatic Institute and has held executive and individual contributor roles in development, sales, and product management from startups to Fortune 100 companies.

Author:

Other Resources in this Series

Most Recent

Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.
Article

Use Scenarios are Stories That Provide Context

The problem with today’s user stories is that they aren’t interesting. And they aren’t stories. The solution is use scenarios. It’s a narrative. It explains the problem in the form of a real-life story.
Article

Benefits of Bundle Pricing

Bundle pricing is simply a strategy where services or products are packaged together for one (often reduced) price rather than priced separately. This article covers some benefits of bundle pricing followed by a system for getting started.
Article

A Quick Guide to Value-Based Pricing

Value-based pricing begins with knowing the customer’s willingness to pay based on the perceived value of your product. You can charge less than a customer’s willingness to pay, and they feel like they’ve received an
Article

What Is Captive Product Pricing 

If you’re looking for a simple answer, it’s this: captive product pricing is when consumers make a one-time purchase (usually a lower-priced core product) but are required to purchase accessories for the main product to

OTHER ArticleS

Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.
Article

Use Scenarios are Stories That Provide Context

The problem with today’s user stories is that they aren’t interesting. And they aren’t stories. The solution is use scenarios. It’s a narrative. It explains the problem in the form of a real-life story.

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Subscribe

Subscribe

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

First Name*
Last Name*
Email Address*
Phone
Company
Job Title
Location
How can we help you?
Preferred method of contact
Privacy Policy*
Map Your Message to Its Audience with the Communication Compass
Map Your Message to Its Audience with the Communication Compass
Ensure your message hits the mark. This eBook helps you visually map communication styles so you can tailor your design story to a stakeholder or business partner.

Download Ebook

Demystifying Data Projects: A Guide for Business Leaders
While data science is a competitive advantage, data isn’t magic. Learn how to make magic happen by partnering more effectively with data professionals. This eBook delves into types of data projects, sample questions, tools and methods, key points and cautions—so stakeholders like you can initiate data projects with real business impact.

Download Ebook

Define Ebook Thumbnail
What’s the difference between a successful data analysis project and one that falls flat? 

Before you begin working with the data, you need to understand what you’re solving for. Gathering context and aligning around goals with your stakeholders from the outset will help you avoid disconnects and deliver actionable insights. Discover the most vital questions to ask before embarking on a data analysis project in our in-depth guide, “Define: Laying the Foundation for Successful Data Analysis.”

Download Ebook

Download Now