How to prioritize product Backlog in Scrum using a 100-point approach?

It’s important to prioritize your product backlog to make sure it doesn’t become an open-ended list where everyone has random ideas about your product. Your to-do list needs to be structured, organized, and prioritized to identify the most strategically important things for your team to do. In this article, I introduce the 100 Points method for product backlog refinement activities.

What is the percentage method?

How does the 100-point method work?

Here is an example of a 100/100 point approach to developing new e-commerce sites:

Imagine a group of people trying to prioritize five items.

  • 100 points per person.
  • One person can decide that each project is equally important and assign 20 items to each project.
  • Or, they consider project 1 more important than project 2, project 2 is more important than project 3, and so on. As a result, their votes were allocated on a weighted basis, with 40 votes obtained in case 1, 30 votes in case 2, 15 votes in case 3, and so on, until all votes had been allocated.
  • All ballot papers are then added together to determine the final vote for each item, resulting in a priority list.


We must weigh the pros and cons in making priority decisions. The more points one gets, the less points the other gets. Does this democratic voting process guarantee quality decisions? It really depends on the quality and intelligence of the team.

Because the 100-point method provides a fixed sum, it needs the correct precedence order to be considered valid. Otherwise, some validation procedures will be necessary, but this may be worth the effort and can also be done with some software tools.

IT professional