The scenario is all too similar for product managers: there are a million feature requests for development and many if no more stakeholders with conflicting agendas about which should be implemented. The solution – objectively determining what’s most important – isn’t always so easy to achieve.

For product companies, the development of the wrong feature doesn’t just waste valuable company resources, it jeopardizes the entire product (and, by default, the company).

That's why we've added 2 more prioritization techniques to Hygger: RICE and ICE.

RICE Prioritization

RICE score model is one of the most simple and convenient models for product manager’s needs. You have 4 criteria which help you to evaluate each feature:

  • Reach - How many people will your feature impact in a specific period of time and how many of them will notice the changes?
  • Impact reflects what contribution does the feature give to the product. How will the project impact your customers?
  • Confidence shows how I'm sure about all my estimates - both about impact and effort (how much my estimations look like a truth).
  • Effort is estimated as a number of “person-months”, weeks or hours, depending on needs. It is the work that one team member can do in a specific month.

To use it you should create a Backlog board and choose the RICE prioritization type. Give a mark to each feature and open the Scoring Table. 

You sort features and push the winners to Kanban/Sprint board for developing them using Push or Push all actions.

Read more about RICE prioritization when you have time.

ICE Prioritization

ICE scoring was intended to prioritize growth experiments. But now the ICE is used for features prioritization as well. The score is calculated in the following way:  

  • Impact demonstrates how the feature will effect on the product
  • Confidence shows your assurance of your evaluation. It is also about ease of implementation in some way.
  • Ease is about the easiness of implementation. It is an estimation of how much effort and resources are required to implement this idea.

These criteria are rated on a relative scale of 1–10. 

It works the same way as RICE: you evaluate features, then select the winners from the scoring table and push them to Kanban or Sprint board for development.  

Read more about ICE prioritization.

Hygger Speed and due date

We significantly speeded up the process of a task pop up opening and add "Due Date" to the quick task actions. More time on project development!

Did this answer your question?