3 fun powerful prioritization techniques

"Amazing how fire exposes our priorities” says Sherlock, also if it’s to translate the Pareto principle to Product, we could say that “80% of the product value comes from 20% of product backlog items “ ... then smart prioritization is the key? Here are 3 of the most popular prioritization techniques:

   The 100$ test also called Cumulative Voting is a pretty simple and straightforward technique.  All participants are given a finite amount of imaginary units (usually 100 dollars). Each of them should divide the amount among the given options (user stories, tasks, requirements). After that, you can calculate the total units for each option and order them accordingly.

   Priority Poker identical with planning poker at Product level, played by all stakeholders, POs, designers, domain experts and perhaps even users. The moderator will also need to prepare the list of tasks to prioritize and a set of priority cards to provide to each player. The number of cards in this set depends on how many levels of priority are useful to use. the moderator reads a piece of functionality (user story). Each participant chooses the card that they think is the most appropriate ranking for that task and places the card face down on the table. When all participants have made their choice, all the cards are turned over at the same time. The differences are discussed and the game goes on until the estimates are around the same level.

   MoSCoW analysis is the prioritization technique that is recommended for business analysts in the IIBA BABOK. According to this method, a list of requirements or user stories should be categorized into the following 4 groups: Must, Should, Could and Won't. After classification into the 4 groups, the requirements are ranked in order of preference within each category.

Don’t let “fire expose” your priorities ;)