<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

Comment

All of the below methods require top level information. Make sure you know at least these three things:

What problem are we solving?

Who are we solving it for?

What will be the impact if we solve this problem (or don’t)?

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