MoSCoW

last edited by: Igor Zdorovyak on Mar 8, 2017 12:22 PM

login/register to edit this page

Contents
1 Applications
2 Procedures
3 Instructions
4 Criticism of MoSCoW method

MoSCoW is a prioritization technique used to reach a common understanding with stakeholders on the relative importance they place on the delivery of each requirement. It is also referred to as MoSCoW prioritization or MoSCoW analysis.

It is an acronym taken from each of four prioritization categories:

Must have
Should have
Could have
Would like but won't get

Applications

Used to prioritize requirements and deliver the most essential and urgent business needs early. This is essential when delivery timescales are crunching project development time.

The MoSCoW technique is usually used in business analysis, project management, and software development.

Procedures

Must have - critical to the project's success.
Should have - Important, but not necessary for delivery in the current schedule timeframes.
Could have - Desirable requirements but no necessary.
Won't have - Requirements that are least essential and will not be released.

Instructions

Elicit requirements
Arrange for stakeholders to meet
Go through the entire unordered requirements list and classify each into one of the four categories above.
Release the list for further analysis
Get formal signoff on the final list from the sponsor

Criticism of MoSCoW method

Some feel that by classifying a requirement as "nice to have" it make it no longer a requirement, but more of a nicety. Therefore it no longer fits the scope of the requirements document.