MoSCoW prioritisation is a structured decision-making framework that forces teams to sort features, requirements, or ideas into four categories: Must Have, Should Have, Could Have, and Won't Have. The method is used widely in agile product development and design to create clarity about what is essential versus what is desirable, and to make the trade-offs involved in scope decisions explicit and visible. It is particularly effective for aligning diverse stakeholder groups around a shared understanding of priorities without requiring consensus on every individual item.
What It Is
The four MoSCoW categories each carry a distinct meaning. Must Haves are non-negotiable requirements without which the product cannot function or would fail to meet its core purpose. Should Haves are important but not critical: the product would be significantly less useful without them but could be launched or delivered without them. Could Haves are desirable features that would enhance the product if time and resources permit. Won't Haves are explicitly out of scope for the current phase, though they may be reconsidered in future. The act of placing each item into one of these categories forces explicit discussion about value, dependency, and feasibility.
How to Run It
Prepare a list of all features, requirements, or ideas to be prioritised. Present each item to the group and ask participants to place it in one of the four categories. Work through Must Haves first to establish the irreducible core. Challenge any item proposed as a Must Have: if the product could technically function without it, it is probably a Should Have or a Could Have. After all items are categorised, review the Must Haves collectively to ensure the scope is feasible within the available time and resources. Adjust as needed.
When to Use It
MoSCoW is most useful during project scoping and sprint planning, when a team needs to define what will and will not be included in a release or a project phase. It is also valuable in stakeholder workshops where different groups have different priorities: the explicit categorisation process creates a forum for negotiation that is more productive than an open-ended conversation about what is important. Use it iteratively across the life of a project rather than as a one-time exercise.
Tips for Success
Watch for category inflation: when everything is a Must Have, the framework loses its value. Challenge the team to be ruthless about the Must Have category, aiming for no more than forty to sixty percent of the total list. Be explicit that Won't Have does not mean 'never': it means not in this phase. This distinction reduces the resistance that arises when stakeholders feel their priorities are being permanently dismissed rather than deferred.
