July 27, 2021
0 min read

Product Backlog prioritization techniques & tips

Product Backlog prioritization techniques & tips.png

An Agile project only runs smoothly when the Backlog is in order. Smart software development teams know that a well-groomed and prioritized Backlog allows them to plan iterations well. In this way, they can communicate within the team and with stakeholders. 

First, let’s define our terms. What exactly do we mean by Product Backlog? The Product Backlog is a prioritized list of work a software development team needs to complete to finish the current Sprint. Priority items appear at the top of the list. The team sets their own pace, they tackle items from the Backlog as they have time to complete them.

Read more in Sprint Backlog vs Product Backlog to learn the main differences.

Why do teams prioritize their Backlogs? Why not just randomly complete tasks until they finish the Backlog? For a team to deliver their project, some items on the Backlog might rely on other items to function. Or the team might need to complete certain tasks first for the customers’ needs. Sometimes Product Owners might need certain tasks completed in order to show them to stakeholders.

How do you Prioritize a Backlog?

Below we have some tips to help you prioritize your Project Backlog.

  1. Sort and categorize the items on the Backlog. Make a note of which items have high and low priority, and which bugs need fixing. The team should also label Backlog items (tasks, stories, epics) according to the amount of work required to complete them.

  2. Tackle the high-priority tasks first, save less important tasks for later.

  3. Score your Backlog items according to factors important to your team. Chose metrics like customer value, ROI (Return on Investment), or interdependencies.

  4. Low-priority items can move to a separate list, making the Backlog list shorter and easier to understand. Teams can create a “new features” or “great ideas” list.

  5. Refine and re-evaluate your Product Backlog. The Product Backlog lives and breathes, teams should regularly make sure the priority items still remain the most important.

  6. Finally, once the team has prioritized their Product Backlog, begin at the top of the list and work down. Prioritization only works if the team actually follows up on their commitments.

Who should prioritize the Backlog?

Product Owners should prioritize the Backlog with input from the software development team and stakeholdlers. Product Owners should order the Backlog with an eye on which items need attention sooner and which items can wait.

Savvy Agile teams rely on many Backlog Prioritization techniques. Let’s take a look at the most useful ones.


RICE stands for Reach, Impact, Confidence, and Effort. When measuring Reach, teams look to quantify the number of customers who will use the feature benefit from the Backlog item. Whenever Possible, this number should come from actual data, not a guess. Impact asks the team to make an educated guess about how likely the feature in the Backlog will impact an individual user. Confidence measures the team’s confidence in their estimates. Effort measures the amount of work and time the team will need to devote to the Backlog item to complete it.

Pros of RICE

  • Puts users at the center

  • Relies on data and sold metrics

  • Comprehensive

Cons of RICE

  • Time-consuming

  • Math-heavy

  • Data-driven, without a lot of data teams might have to make many guesses

2. Opportunity scoring

Opportunity scoring relies on two graphs to rank the Backlog items. First, they use a satisfaction graph, ranking how users like a feature. Then they use an importance graph, measuring how much users value a feature. In examining the two charts teams identify what frustrates their users and what their users want.

Pros of opportunity scoring

  • Focuses on ROI (Return on investment)

  • Works for many different types of Backlogs

  • Helps find gaps between user need and value provided

Cons of opportunity scoring

  • Teams need to have an existing product, doesn’t work for new features

  • Narrow in scope

3. Kano model

Japanese researcher Noiraki Kano created the Kano model in the 1980s. The Kano model measures user satisfaction to prioritize the Backlog. Using Kano, the team scores Backlog items by several criteria: Must-be, attractive, one-dimensional, indifferent and reverse. Must-be features are those that customers need for the product to function. Customers see one-dimensional features as important and desirable. Attractive features add value and satisfaction. Indifferent features have small or no value to customers. Reverse features have a negative impact on customers.

Pros of Kano

  • Ranks features by their value

  • Customer-centered

  • Gives easy insight into strengths and weaknesses of a feature

Cons of Kano

  • Analyzes only customer opinions, not costs or effort

  • Kano doesn’t detail resource requirements

4. MoSCoW prioritization

Agile teams use MoSCoW because MoSCoW is simple and easy to use. The acronym stands for Must, should, could and would. MoSCoW allows teams to determine the relative importance of Backlog items. Must means any Backlog item required for a product to function. Should stands for items that have high value to the customer. Could Backlog items are small fixes and features. Would items have the lowest importance and can be added to a future Backlog if the team doesn’t have time.

Pros of MoSCoW

  • Easy to use

  • Not too technical or mathematical

  • Fast 

Cons of MoSCoW

  • Zoomed-in view, not an overview

  • Not sequenced

5. Value vs Complexity Matrix

This Matrix works well because it maps out Backlog items according to their worth and their difficulty. Value vs Complexity Matrix uses four quadrants to plot these scores. Teams tackle items with high value and low complexity first.

Pros of Value vs Complexity Matrix

  • Simple, easy to understand

  • Works well to spot easy wins 

  • Not math- or analysis-heavy

Cons of Value vs Complexity

  • Tends to allow for subjective judgment

  • Doesn’t work well for large Backlog lists

Story mapping

Jeff Patton developed Story mapping to add another dimension to Product Backlog prioritization. Story mapping shows more detail than a Product Backlog list. Patton proposes plotting the sequence of the user journey on a horizontal axis. Then we plot the importance on a vertical axis. We group related stories. Agile teams like story mapping for its ease-of-use and transparency. Story mapping gives the team and stakeholders a holistic and rich view of the customer journey.

Pros of story mapping

  • Shows complex relationships between different Backlog items

  • Flexible

  • Gives a full, holistic view of the customer’s journey

Cons of story mapping

  • Story maps may become complex

ICE scoring

ICE scoring uses a formula to score Backlog items. ICE stands for Impact, confidence and ease. Impact measures the effect of the change. Confidence measures how certain the team feels about their impact score. Ease shows the teams’ opinion about the difficulty of completion. Teams give each part of ICE, Impact, confidence and ease a score from 1-10.

Pros of ICE scoring

  • Good for sorting out the best and most important Backlog items

  • Shows which tasks might need the same resources to complete

Cons of ICE scoring

  • Possibly subjective

  • Scores might differ widely between different team members

Learn more from our insights

DALL·E 2024-05-22 20.55.08 - A detailed and high-quality DSLR photo of a person using a laptop to shop online, showing personalized product recommendations on the screen. The back.webp
May 16, 2024

Key AI Trends in E-commerce and Overview of AI integrations for E-commerce Platforms in 2024

Transform your e-commerce platform with AI tools for personalization, analytics, chatbots, search, and fraud detection. Boost sales and improve customer experiences.

eIDAS mark.png
May 09, 2024

Digital Identity and Payment Services in the EU in 2024: Key Updates

eIDAS 2.0 and PSD3 are set to enhance how digital identities and payment services are managed across the European Union in 2024. Here’s an overview of how each framework contributes to the digital landscape of the EU, what to expect, and how to prepare.

eIDAS 2 in fintech and open banking EU market.png
May 06, 2024

What is eIDAS 2.0 and EU Digital Identity Wallet and how will it change the EU digital market

Learn how eIDAS 2.0 and the EU Digital Identity Wallet will transform digital transactions and identity management across the European Union.

best large language models for ERP systems.png
March 31, 2024

Language Models Best Suited for Integration into ERPs

Four prominent large language models stand out for their compatibility and effectiveness in ERP system processes and automation. See what they are.

PSD3 in open banking Blocshop.png
April 23, 2024

PSD2 vs. PSD3: The Evolution of Payment Services Regulation

What is PSD3 in open banking? See how PSD3 compares to PSD2 and what should banks and fintech businesses do to ensure regulatory compliance in the EU market.

April 14, 2024

Enhancing ERP Systems with AI Chatbots

Explore how AI chatbots can transform ERP systems, enhancing efficiency, decision-making, and user interaction.

eIDAS in fintech and open banking EU market.png
April 29, 2024

eIDAS: The regulation helping secure Europe's digital future

See how eIDAS enhances EU digital transactions with secure identity verification, supporting e-commerce and public services across Europe.

hybrid ERPs.png
March 21, 2024

Hybrid ERP: An Innovative Approach to Enterprise Resource Planning

Hybrid ERP is a blend of cloud and on-premise solutions. With expertise in both, Blocshop is uniquely positioned to help you with hybrid ERP development and implementation.

0-4 cover.png
October 03, 2023

IT Staffing: Individual Hiring vs. Specialized Developer Teams

Should you hire individual developers or go for a specialized, custom-built developer team?

July 17, 2023

ChatGPT-3.5: An Overview and Limitations

In this article, we'll take a closer look at the capabilities and limitations of ChatGPT-3.5, providing you with a comprehensive overview of what it can do and what its boundaries are. So, let's delve into the inner workings of this large language model.

gpt4 vs gpt3-5 and the key differnces.png
June 15, 2023

A Deep Dive into GPT-4 vs GPT-3.5 Differences and Ability to Revolutionize Software Development

There are key differences between ChatGPT-3.5 and ChatGPT-4 that software developers and companies procuring software solutions alike should be aware of. Let's see how these differences affect the output generated by these models on specific examples.

May 09, 2023

AI-powered software development: What CTOs need to know in 2023

As technology continues to evolve at a rapid pace in 2023 and beyond, CTOs must stay ahead of the curve by utilizing predictive analytics, automated testing processes, and deployment solutions.

May 05, 2023

How Artificial Intelligence is changing web development

AI technology is now being used in many different industries, including web development. It’s important to understand the impact that AI can have on web development as it can help companies to create more efficient and user-friendly websites.

May 05, 2023

How AI-powered software development is changing the role of the CTO

As AI-powered software development becomes increasingly commonplace, CTOs must prepare themselves to take on a new set of responsibilities that require more than just technical know-how.

April 17, 2023

How to build a minimum viable product (MVP)

The MVP is the version of a new product that allows Blocshop and your team to collect the maximum amount of validated learning about customers with the least amount of effort. The essence of your core idea is delivered as a barebones solution. The solutions is, however, sufficient for usage by early adopters. As a product, it has tangible qulities that express a look and feel.

March 21, 2023

10 AI tools for developers you should know about in 2023

For developers, programmers, and data scientists, AI coding solutions can free up thinking time, allowing such professionals to focus on the fundamentals of their projects, and complete such projects much faster.

February 14, 2023

17 Ideas for Web Apps in 2023

Gazillions of web apps and ideas for web apps are floating around the metaverse - so creating one that properly represents a unique brand is a huge challenge. Our list provides a number of areas of simple app ideas to help businesses transform their online presence through a web app.

Top 15 micro-SaaS ideas for your startup in 2023.png
December 06, 2021

Top 15 micro-SaaS ideas for your startup in 2022

What exactly do we mean by micro SaaS? Micro Saas solutions use a web browser or mobile app interface. Micro SaaS solutions usually come about through the effort of an individual or very small team. It aims to solve precise problems. Micro SaaS projects have small budgets and overhead. Customers use Micro SaaS solutions on a monthly or yearly subscription basis. Micro SaaS projects target a small niche of the consumer market.

Software engineer hourly rates in 2021 (based on experience and location).png
November 22, 2021

Software engineer hourly rates in 2022 (based on experience and location)

Region influences salary more than any other factor. Taxes rates, cost of living, and government benefit programs affect the rates software developers charge. Software developers in the USA  and Canada earn more than software developers in other countries.

The best programming languages for app development in 2022.png
November 15, 2021

The best programming languages for app development in 2022

Software developers usually have three main ways to create an app. They can choose to code a native app, a hybrid app or a progressive web app. Developers create native apps to function on one specific platform, usually either iOS or Android. They create these apps using Swift or Objective C for iOS. For Android they use C++, Kotlin or several other languages.