<aside> 💡 Ultimately when prioritising you are trying to make sure the item with the most value is delivered first. ‘Value’ can mean different things in different orgs so make sure you are clear on this first. Below are some methods that can be used to prioritise. This is a non-exhaustive list and just focuses in on some of the most used.

</aside>

Contents

MoSCoW Method

Must have: Non-negotiable product needs that are mandatory for the team. Should have: Important initiatives that are not vital but add significant value. Could have: Nice to have initiatives that will have a small impact if left out. Won't have/Would have: Initiatives that are not a priority for the specific time frame.

Questions to ask:

1. What will happen if this is not included in this specific release?
2. Is there a simpler way to accomplish this?
3. Will the product work without it?

RICE Scoring

Quantitative prioritisation technique. Designed to remove ‘gut instincts’. Scoring used below is was developed by Intercom who first coined RICE scoring.

RICE Model Sections

Reach: Designed by the team but can be number of customers e.g. 150 Customers

Impact: 3 = Massive Impact, 2 = High Impact, 1 = Medium Impact, 0.5 = Low Impact, 0.25 = Minimal Impact.

Confidence: 100% High Confidence, 80% Medium Confidence, 50% Low Confidence. If below 50% consider moonshot and move on.

Effort: Person Months e.g. 1 Week of planning, 1-2 Weeks of Design, 2-4 Weeks of Eng = Effort Score 2 Person Months