MoSCoW Prioritization

If you’re looking for a method to prioritize requirements, tasks, or goals, MoSCoW prioritization is the perfect solution. This method simplifies decision-making and allows you to make clear decisions quickly.

Note: MoSCoW prioritization is a versatile method that can be used for self-management and team process optimization.
If you decide to use MoSCoW prioritization with your team, make sure to involve everyone and provide opportunities for open discussion and feedback.

And this is how it works:

Step 1: First, collect all requirements, tasks and functions for the implementation of your goal, product or project on the sticky notes.

Step 2: At this stage, it’s important to critically evaluate each requirement and determine its true value for the project or product. This can help you prioritize and focus on the most important aspects.

You should ask yourself the following questions:

• What is the value of the requirement to me, to the company, or to the customer?
• What is the impact on the product or project goal if the requirement is not fulfilled?
• How much budget and time resources are needed for the requirement?

Step 3: Organize the requirements into the categories to get a clear idea of what needs to be worked on in the near future.

MUST: These requirements are absolutely necessary and cannot be left out. They are non-negotiable.
SHOULD: These requirements are important, but not as critical as the “MUST”. They can be deprioritized if time or resources are limited, but they should be scheduled as soon as possible.
COULD: These requirements are desirable but not necessary. They can be skipped if it is necessary to save time and resources.
NOT NECESSARY: These requirements are currently not prioritized for scheduling. They may be reviewed and considered at a later stage, but are not deemed necessary at currently.

Tip: It is recommended to periodically review and adjust the priorities and their weightings to ensure that the requirements remain relevant and up-to-date.

*MoSCoW [M•S•C•W = Must•Should•Could•Won’t] Dai Clegg von Oracle UK 1994