Radically Honest Blog

Product Backlog: Who Is Accountable for Ordering It?

The product backlog is a critical component of product development. It is a melting pot of feature requests, improvements, and ambitious ideas waiting to be transformed into reality. 

It captures everything from immediate feature requests to long-term enhancements and even those blue-sky ideas that might redefine the product’s future. 

However, with this diverse array of items vying for attention, a crucial question frequently arises: Who holds the reins when it comes to ordering the product backlog?

This article aims to shed light on this pivotal aspect of product management. 

We will dive into the typical roles and responsibilities associated with backlog management and discover the central figures responsible for this.

What is the Product Backlog?

A way too simplistic depiction of the product backlog
A way too simplistic depiction of the product backlog

Before diving into who steers the ship of backlog prioritization, it’s crucial to understand what a product backlog actually is. 

The product backlog is essentially a dynamic list that details everything needed for a product’s development.

It’s the master to-do list of a product development project, encompassing everything from the ‘we absolutely need this’  features, to pesky bug fixes and infrastructure changes, to other improvements, even the ‘wouldn’t it be cool if’  wish-list items.

The backlog is like the central nervous system for your product. It is a living document, not set in stone, and it’s important to regularly review and revise it. 

Here are some of the things you will find on it: 

  • Feature Requests: The bread and butter of the backlog. These are the shiny new features that everyone, from your customers to that guy in marketing, thinks will revolutionize the product. Spoiler: not all of them will.
  • Bug Fixes: The digital equivalent of playing whack-a-mole. As soon as you squash one, another pops up. It’s the endless cycle that keeps the devs on their toes (and sometimes up at night).
  • Technical Debt: Ah, the skeletons in your codebase closet. These are the tasks you know you should tackle but keep putting off for “future sprints.” Future You is not going to be happy.
  • User Stories: Bite-sized chunks of user desires, often reading like a wish list to Santa from your users. They’re deceptively simple but crucial for keeping the team focused on real people instead of hypotheticals.
  • Research and Discovery: These are your “What if?” tasks. Sometimes they lead to game-changing features, and other times, well, let’s just say not every idea is a winner.
  • Infrastructure Improvements: The less glamorous but oh-so-important updates. Think of them as the plumbing work of your product – not exciting but essential for keeping everything running smoothly.
  • Compliance and Regulatory: The necessary evil, especially if you fancy keeping the business legal and not on the front page for the wrong reasons.
  • Performance Enhancements: Because who doesn’t love a product that actually works faster and better? It’s like giving your product a shot of espresso.
  • Documentation: Often the unsung hero of the backlog. It’s about as exciting as watching paint dry, but when you need it, you’ll be glad it’s there.
  • Design and UX Improvements: The chance to put some lipstick on your product. Sometimes a little facelift is all you need to keep users from running to your competitors.
  • Wish-list Items: The “wouldn’t it be nice” category. These are the low-priority dreams that you’ll get to right after you invent the 25-hour day.

The product backlog is more than just a list; it’s a strategic tool that guides the development team on what to work on next. It helps to ensure that the team is always focused and working on the most important tasks. 

Who is Responsible for the Product Backlog?

When you’re sortingthrough the complex world of product development, it’s easy to get confused about who exactly has the authority and responsibility for the product backlog. 

It’s less of a solo act and more of a tag-team effort. 

Let’s look at where the responsibility falls: 

Product Owner

This is your main player. 

The PO is like the captain of a ship, navigating through the stormy seas of market demands and customer feedback. 

They call the shots on what gets worked on and in what order. Think of them as a juggler, but instead of balls, they’re tossing around tasks, priorities, and the occasional fire drill. 

It’s their job to keep the backlog in shipshape, ensuring it’s transparent and makes sense not just to them but to the whole crew.

Key responsibilities of the Product Owner include:

  • Defining and articulating product goals and vision.
  • Creating and clearly describing backlog items.
  • Prioritizing the items to optimize the value of the work done by the development team.
  • Ensuring that the backlog is transparent, visible, and understood by all stakeholders.

They’re the ones who have to decode the market’s cryptic messages, figure out what customers actually want (versus what they say they want), and align all this with the company’s big-picture goals.


Stakeholders, including customers, business managers, and others with an interest in the product, also play a crucial role in the backlog’s formation. 

These folks aren’t steering the ship, but they sure like to shout directions from the shore. 

They provide the essential intel – market trends, user needs, and sometimes, a reality check. 

They don’t micromanage the backlog, but their input can sway decisions. It’s a bit like having a backseat driver who occasionally knows a shortcut you don’t.

Stakeholders contribute by:

  • Providing insights into market trends and customer needs.
  • Suggesting new features or improvements based on their unique perspective.
  • Helping to validate and refine backlog items to ensure they align with user and business needs.

While stakeholders do not have direct control over  the backlog, their input is vital in shaping its content and ensuring that the product remains relevant and competitive.

Scrum Master

Enter the Scrum Master, the agile maestro, if you will. Their job? To make sure the team stays connected to agile practices. 

They don’t play an instrument (or manage the backlog directly), but boy, do they make sure everyone’s in tune and playing in harmony. 

The Scrum Master supports the Product Owner by:

  • Ensuring that the backlog refinement process is efficient and productive.
  • Helping to remove obstacles that may hinder the team’s ability to work effectively on backlog items.
  • Coaching the Product Owner and the team on Scrum practices, including effective backlog management.

Development Team

Last but not least, there’s the development team. These are the real MVPs who actually bring the product to life. 

These folks are the ones deep in the trenches, turning backlog items into reality. They are the knowledgeable ones giving you the real talk on how long things will take and how complex they really are. 

They’re like master craftsmen, turning blueprints (backlog items) into magnificent structures (features).

They provide estimates and feedback on the complexity and feasibility of backlog items.

Their role in backlog management includes:

  • Estimating the effort and time required to complete backlog items.
  • Providing technical insight and feedback on proposed features and changes.
  • Helping to clarify requirements and details of backlog items during backlog refinement sessions.

While the Product Owner may be the captain of the backlog ship, it’s a vessel that needs the whole crew to navigate. 

Everyone from the stakeholders to the devs plays a part in making sure the ship sails smoothly. It’s a group effort where everyone’s expertise ensures that the backlog becomes a strategic tool that guides the team toward building a successful, customer-centric product.

The PM’s Hot Take

Let’s get one thing straight about the product backlog. It’s not some kingdom ruled by the Product Owner. It’s more like a bustling town hall where everyone gets a say. The product owner holds the gavel and makes the final decisions, but all voices - the stakeholders, the scrum masters, and the development teams get heard. 

Stakeholders throw in their market insights, developers give their two cents on what’s technically feasible, and the Scrum Master… well, they’re there to make sure it doesn’t turn into a free-for-all.

The best backlogs are born from a diversity of thought. Every voice, from the greenest intern to the most jaded developer, brings something valuable to the table. Embrace the chaos, welcome the input, and use it to craft something that really resonates.


Alright, let’s land this plane. 

Managing a product backlog isn’t just a one-person show with the Product Owner at the helm. It’s more like a team sport where everyone from developers to stakeholders plays a part. Think of it as a group project where everyone needs to pull their weight.

This team effort is the secret sauce for success in Agile. The Product Owner might seem like the team captain, but it’s the collective input that scores the goals.

Feeling a bit out of your depth? Fibery’s got your back

Psst... Wanna try Fibery? 👀

Infinitely flexible product discovery & development platform.