MoSCoW Technique

The MoSCoW technique is a prioritization framework used to rank portfolio, program, or project components, as well as requirements, risks, features, or other product information. The name "MoSCoW" stands for "Must have," "Should have," "Could have," and "Won't have."

In business analysis and product delivery, the framework helps teams prioritize requirements based on relative importance. The four categories are defined as follows:

• Must have: Requirements or features that are critical to success and must be included in the final product. These represent the minimum acceptable criteria for the product to be considered complete.
• Should have: Important requirements or features that are not essential but still provide significant value. These can be deferred if necessary, but they are desirable because they improve the product's value and usefulness.
• Could have: Desirable requirements or features that would be nice to include but are not essential to success. If time and resources permit, these items can be added.
• Won't have: Requirements or features that are not important or feasible for the current effort and will not be included in this iteration. These are typically deferred to a later phase or treated as out of scope.

MoSCoW is especially common in Agile and DSDM environments where teams need a fast, shared way to decide what absolutely must be delivered versus what can move later without undermining the release.

Another commonly used prioritization scheme is multicriteria weighted analysis.