The MOSCOW Method
MoSCoW prioritization, also known as the MoSCoW method or MoSCoW analysis, is a popular prioritization technique for managing requirements. The method is commonly used to help key stakeholders understand the significance of initiatives.
Developed by Dai Clegg in 1994 for use in Rapid Application Development (RAD), it was first used extensively with the agile project delivery framework Dynamic Systems Development Method (DSDM) from 2002.
Ultimately, the method can help you know what you must do first, what you should do later and what you do not need to do. The capital letters of the MoSCoW acronym correspond to four categories –
M for Must Have (VITAL) – these tasks are indispensable to the success of the project; they should therefore be carried out first and this is non-negotiable.
S for Should Have (ESSENTIAL) – these tasks are important but not vital; they may be painful to leave out, but the solution is still viable, but unlike the ‘Must Haves’, they can deferred in time.
C for Could Have (COMFORT) – these are wanted or desirable tasks but are less important; they have minimal impact if left out
W for Won’t Have but would like in the future (LUXURY) –: these are secondary tasks that we would like to carry out one day, but which we leave aside for now, due to lack of budget and/or lack of time.
Instructions
List the elements (tasks, projects, features) you would like to prioritize
Start by listing all the tasks to carry out; make sure all stakeholders are represented when you do this.
Once your list is ready, sort and categorise each of the elements listed by using the MoSCoW method.
Everybody should participate in this discussion and it will be necessary to find a good balance between the expectations and demands of each stakeholder.
Validate the suitability of the classification
If you end up with a large number of tasks in the first two categories (“Must Have” and “Should Have”), make sure that the workload is feasible and that the deadlines, the budget and the capacities of your resources are respected.
If this is not the case, sort the “Must Haves” again by ensuring that the tasks really are essential to the success of the project.
Management of priorities is essential. You can use the MoSCoW method all the time – once a week, at each new iteration or everyday so that each member of the team knows their priorities for the day. If you are late, whether unforeseen or because of a problem, do not hesitate to take another look at your priorities.
