The MoSCoW method is a prioritization technique used in management, business analysis, project management, and software development to reach a common understanding with stakeholders on the importance of each requirement. The term MoSCoW is an acronym derived from the first letter of each of four prioritization categories: Must have, Should have, Could have, and Won’t have¹.

Prioritization Categories

1. Must have: These requirements are critical to the current delivery timebox for it to be considered a success. If even one Must have requirement is not included, the project delivery should be considered a failure. MUST can also be considered an acronym for the Minimum Usable Subset¹.

2. Should have: These requirements are important but not necessary for delivery in the current timebox. They can be as important as Must have requirements but are often not as time-critical or can be satisfied in another way¹.

3. Could have: These requirements are desirable but not necessary. They could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit¹.

4. Won’t have (this time): These requirements are the least critical, lowest-payback items, or not appropriate at that time. They are not planned into the schedule for the next delivery timebox but may be reconsidered for inclusion in a later timebox¹.