Ordering the Product Backlog

A Product Backlog contains different types of work from new feature development to defect management. The way that a Product Owner should order these types of items is by considering the value it brings to the customer. Not every feature needs to be built and not every defect should be fixed if they are not important to the customer. A Product Owner orders a Product Backlog in any way they think will maximize the value of the product. They take various factors into consideration when ordering the Product Backlog such as business value, risk, return on investment (ROI), dependencies and impact.

 

Resources:

Publication
In the past, the Scrum Guide consistently used the word "priority" for the Product Backlog or noted that the Product Backlog was “prioritized.” While the Product Backlog must be ordered, ordering by priority is only one many techniques — and rarely the best one at that.
4.7 from 28 ratings
Video
In this video, you'll learn four different factors that influence the order of a Product Backlog. You'll also learn more about the topic by walking through a scenario with a Scrum Team who is ordering their Product Backlog as a part of Product Backlog refinement. (5:45 Minutes)
4.7 from 13 ratings
Blog Post
Picture for Mary Iqbal Mary Iqbal
In this article, we will explore some complimentary practices which the Product Owner might use to as an input when deciding how to order the Product Backlog.
5 from 7 ratings
August 28, 2023

What did you think about this content?

Included In

Learning Series
Product Backlog Management is the act of adjusting and ordering items on the Product Backlog so that the Scrum Team can deliver the most valuable product possible. This learning series explores Product Backlog Management.