MoSCoW method

Also called: must, should, could, would(MoSCoW)

The MoSCow method is a principle widely used within product development, software development and business analysis to establish priorities. The requirements of a project (think of a product's features) are classified into one of the following categories in a moscow analysis:

• Must-have: Required to speak of a workable product;
• Should-have: High priority, but not required for a usable product;
• Could-have: Option taken only if there is time to spare;
• Would-have: Not a priority, could possibly be reconsidered in the future (aka: won't-have).

The o's in MoSCoW are only meant to make the abbreviation pronounceable and have no other meaning.

Assigning such priorities to requirements helps keep projects manageable. Work can be done faster toward a completion date. Leaving less important features out (temporarily or otherwise) also makes developing and supporting a project easier.

Focusing on a product's "key requirements" can also simplify its marketability. For example, must-haves can be not only features required to use a product, but also an essential unique selling point from which a product derives its raison d'être.