Customer Valued Prioritization

This is simply keeping the product backlog prioritised based on delivering maximum value to the customer. As new items are added to the backlog they are compared to current items on the backlog in terms of business value so when the team planning on next iteration they choose items on top of the backlog. This is an on-going process throughout the project.

>> More information Customer Valued Prioritisation from Scrum Study


MoSCoW is derived from the first letters of the following:

  • Must Have
  • Should Have
  • Could Have
  • Would like to Have

It is highly effective and straightforward for getting the business to convey their priorities.

>> More information MoSCoW from All About Agile

Simple Schemes

On of the simplest schemes is to label stories Priority 1, 2, 3 or high, medium and low. This is a very straightforward method but loses its effectiveness when too many items are marked high priority. A good way to govern this is to have defined ground rules what determines a priority 1, 2, 3.

>> More information on Simple Schemes from Leading Answers

Monopoly Money

The stakeholders are provided monopoly money equal to the projects budgets and asked to distribute the budget amongst the project features.  Monopoly money technique works best when prioritising features as if prioritising the entire backlog the stakeholders might omit documentation or other tasks they don’t see the immediate value in.

>> More information on Monopoly Money

100-Point Method

The 100-Point method was developed by Dean Leffingwell and Don Widrig for use cases. The stakeholders are provided 100 points which they can distribute amongst features. They can distribute any way they want even put 100 on one feature if it is their one and only priority.

>> More information 100-Point Method from the Modern Analyst

Kano Analysis

This technique categorises features into 4 categories:

  • Delighters/Exciters
  • Satisfiers
  • Dissatisfiers
  • Indifferent

This will help convey the features that bring the most customer satisfaction. Please see below image for reference.

>> More information Kano Analysis by Tyner Blain

Dot Voting or Multi-Voting

Each stakeholder gets a predetermined number of votes/dots and which they distribute amongst features. A good rule of thumb for assigning votes is 20% of total items for example if 50 items would be 50 x 0.2 = 10 so each person would have 10 votes.

>> More information Dot Voting from Dotmocracy

Requirements Reviews

This is another name for backlog grooming or refining the backlog. Always remember the customer is responsible for setting the priorities and making sure the backlog is up to date. The delivery team is responsible for estimating the work so the business can effectively prioritise the work based on cost-benefit analysis.

>> More information Requirements Reviews from Bridging the Gap

Minimal Viable Product (MVP)

When planning releases of a product the releases need to deliver value to the business. For this reason, the MVP needs to be defined identifying what features need to be included to make the product functional and then plan releases around the MVP. MVP is also called MMF minimum marketable feature which the product is complete enough it brings value but yet still small enough that it is clear that it is not complete.

>> More information on MVP

Relative Prioritisation/Ranking

Regardless of how the backlog is prioritised the end goal is to understand the stakeholder priorities of the features. With relative prioritisation, it simply organises features by number 1,23 etc. This makes it easier to define a minimum viable product by simply say 1-6 need to be done to create the MVP. When new items are added to the list late on in development they will need to replace a current item in the MVP list or move down the priority of the item from 5 to 6. This helps give the team a clear understanding of what needs to be done to complete the project.

> More information on Relative Prioritisation from Process Impact

This article is part of the our 100 Agile Tools & Techniques epic article based off the PMI list of recommended techniques and tools in their PMI-ACP certification syllabus. 

Shane Drumm

Shane is an Agile Project Manager who specialises in digital web projects. He has worked with numerous distributed teams in Asia, Europe, US and Australia. In his spare time, enjoy travelling, cycling, digital start-up ventures and hustling to help other business owners with their digital presence. Find out more about Shane on and please reach out and connect with Shane on LinkedIn.


Recent Posts

Virtual Icebreakers for Introverts

Before we discuss icebreakers for introverts you need to remember introverts don't like participating in… Read More

3 days ago

Agile Quarterly Planning with Distributed Teams

Remote Quarterly Planning with 3 Timezones & 9 Squads...sounds fun right? During COVID my company… Read More

2 weeks ago

How to Facilitate a Virtual Silent Meeting Today

Silent Meetings are my go-to technique for facilitating Zoom meetings remotely. First started by Jezz… Read More

3 weeks ago

Ice Breakers for Zoom Virtual Drinks Meeting

As the world is working for home and leaders are looking for innovative ways to… Read More

3 weeks ago

Ultimate Agile Toolbox for Traditional Project Managers

We have listed every Agile project management tool and technique to help traditional project managers… Read More

1 month ago

5 Meetings to Try with Remote Agile Teams

In 2020 the IT industry has swiftly switched to working from home. Agile Coaches and… Read More

2 months ago