USE PRIORITIZATION TECHNIQUES FOR SETTING TASKS
Task prioritization helps you understand what should be done first to convey the maximum value of the project to the customer and earn more money for the company.
Each organization has its allocation of resources. There are teams with shared and limited resources: several managers can involve designers, programmers, and analysts in the development of the same team. In this case, the fight for them begins: at general meetings, you need to quickly and reliably justify why exactly your feature should be taken and implemented first, and not your colleagues'.
There are several helpful techniques for correct task prioritization.
The most popular are:
1. ICE Score
2. RICE Score
The ICE score includes three elements.
1. I- Impact.
Impact shows how much the idea will positively affect the indicator you are trying to improve;
2. C- Confidence.
Confidence shows how much you trust the impact estimates and ease of implementation. To determine this indicator, answer the question: how confident you are that this feature will lead to the improvement described in Impact, and will be as easy to perform as described in Ease;
3. E- Ease.
Ease shows how much effort and resources will be required to implement this idea. This indicator is usually measured in person-weeks. The easier the task, the higher the number.
To determine the ease of implementation, answer the following questions: how long will it take? How many people will be involved? It is also necessary to take into account the work of all departments: development, design, marketing.
How is the ICE score calculated?
After placing the indicators, all 3 indicators are added and divided by 3. After practicing this prioritization technique with all the tasks, those that are more priority at the moment are identified.
The RICE score is another method of prioritizing product ideas and features.
The framework includes 4 factors:
Reach is measured in the number of people/events per time period. That might be "customers per quarter" or "transactions per month". As much as possible, use real measurements from metrics instead of pulling numbers from the head.
As with the ICE score, in RICE there is such an indicator as Impact. In RICE, Impact is accessed on a three-point scale. 3 for "massive impact", 2 for "high", 1 for "medium", 0.5 for "low", and finally 0.25 for "minimal". These numbers get multiplied into the final score to scale it up or down.
As with the ICE score, this indicator determines how confident you are that this feature will lead to the improvement described in Impact, and how much effort should be made. The main difference from the ICE score is that it is estimated in percentages: 100% is "high confidence", 80% is "medium", 50% is "low". Be honest with yourself: how much support do you really have for your estimates?
To move quickly and have an impact with the least amount of effort, estimate the total amount of time a project will require from all members of your team: product, design, and engineering. Effort is estimated as a number of "person-months" – the work that one team member can do in a month. For instance, project 1 will take about a week of planning, 1-2 weeks of design, and 2-4 weeks of engineering time. I'll give it an effort score of 2 person-months.
How is the RICE score calculated?
Multiply "Reach", "Impact", "Confidence" and divide into "Effort". Once the initial scoring is done, sort your list and re-evaluate. Are there projects where the score seems too high or too low? If so, reconsider your estimates and make changes, or accept that your gut instinct may be wrong.
Practice both prioritization techniques and choose the most convenient for you :)