From the Scrum Guide: “A Product Owner orders the work for a complex problem into a Product Backlog.”
Ordering work…
From Cambridge Dictionary: “order: to arrange a group of people or things in a list from first to last.”
In this post, we explore ‘ordering’ in Scrum as arranging work in a sequence—deciding what comes first in the Product Backlog. This differs from prioritization, which focuses on importance without necessarily dictating sequence.
According to the Cambridge Dictionary, prioritizing is “to decide which of a group of things are the most important so that you can deal with them first.” Unlike ordering, prioritization allows for multiple items to share the same level of importance, whereas ordering requires a clear sequence.
While prioritization is about deciding which items are the most important, ordering involves arranging those items in a specific sequence—what comes first, second, and so on. In an ordered list, no two items can share the same position.
What is the first thing the Developers should be working on to maximize the value of the product?
What should a Product Owner take into account when arranging Product Backlog items?
I see three categories of criteria:
Value: The higher the potential ROI, the sooner the item might need to be addressed.
Size: Smaller items might be ordered higher to deliver value quickly, while larger items may require more refinement before being ready.
Risk: Addressing high-risk items early helps mitigate uncertainties and informs subsequent decisions.
How do you approach ordering in your Scrum practice? What criteria do you find most impactful for arranging Product Backlog items?
I’d love to hear your thoughts in the comments below!
I hope you find value in these short articles and if you are looking for more clarifications, feel free to take contact.
Don't want to miss any of these blog posts? Have the “The Scrum Guide Explored” series weekly in your mailbox.
Wishing you an inspiring read and a wonderful journey.
Scrum on!
