MoSCoW method: explanation, examples and practical use
The MoSCoW method is one of the most widely used prioritisation techniques in software development and project management. By dividing requirements into four clear categories (Must, Should, Could and Won't), stakeholders, developers and product owners gain a shared understanding of what really matters. In this article, we explain how MoSCoW works, where it comes from, and how you can apply it straight away in your own projects.
From Clegg to everyday practice: where does MoSCoW come from?
The MoSCoW method was developed in 1994 by Dai Clegg, then a consultant at Oracle UK. Clegg was looking for a way to classify requirements quickly and unambiguously in software projects with tight deadlines. The method was first formally described as part of the Dynamic Systems Development Method (DSDM), an early agile framework that became particularly popular in the United Kingdom and the Benelux.
The acronym MoSCoW stands for Must have, Should have, Could have and Won't have (this time). The lowercase "o"s in the acronym exist purely to make the word pronounceable and have no meaning of their own. The addition of "this time" to Won't is deliberate: it indicates that a requirement is not rejected permanently, but consciously deferred to a later iteration.
In the Netherlands, MoSCoW has become a standard in requirements engineering and project management. The method is widely used in government contracts, enterprise projects and start-up MVPs. Its popularity comes not from complexity but from simplicity: four categories, understandable to both technical teams and business stakeholders, with no training or tooling required.
Whereas methods such as RICE or Weighted Shortest Job First (WSJF) require specific scores and formulas, MoSCoW uses a qualitative classification that anyone in a meeting can apply. That makes it ideally suited to situations where speed and agreement matter more than mathematical precision, such as kickoff workshops, sprint planning sessions and scope negotiations with stakeholders.
The four categories explained: Must, Should, Could and Won't
Each requirement gets exactly one of the four labels. The strength lies in the clarity: there is no middle option, no "almost-must" or "high could". That forces teams to make real choices.
Without this, the project fails
Must have requirements are non-negotiable. If they are missing, the project delivers no usable result. Think of legal requirements, core functionality without which the product does not work, or contractually agreed deliverables. A requirement is only a Must if the answer to the question "can the product go live without this?" is an unambiguous "no". In practice, in app development, Musts include a working authentication system, the ability to process payments in a web shop, or GDPR compliance when handling personal data.
Important, but not blocking
Should have requirements are valuable and almost always get delivered, but the product can temporarily do without them. There is usually a workaround. An example: advanced search filters in a product catalogue. The catalogue works without them, but the user experience improves considerably when they are there. Should haves are typically planned in the first sprints after the MVP is delivered. They bridge the gap between "it works" and "it works well".
Nice to have, not a hard requirement
Could-have requirements improve the experience but aren't essential to the project's success. They're the first items to go when budget or schedule comes under pressure. Think of a dark mode, animations on page transitions, or an optional integration with a third party. Could haves act as a buffer in the schedule: if the team moves faster than expected, they get picked up after all. That way, developers never sit idle when a project goes smoothly.
Deliberately parked, not forgotten
Won't have is the most underrated category. It isn't a rejection, but a deliberate scope decision: "we know this is valuable, but we're not doing it now." By explicitly placing requirements under Won't, you prevent scope creep: the gradual expansion of a project that undermines deadlines and budgets. It's also a communication tool for stakeholders: their wish has been heard and documented, but doesn't fit the current release. In a later iteration or version, a Won't can be reconsidered.
MoSCoW in practice: a requirements session step by step
Applying MoSCoW isn't a bureaucratic process. In most cases a single workshop session with the right stakeholders is enough. Below we describe a proven approach that we regularly use in consultancy engagements and project kick-offs.
-
1Gather the requirements
Collect all known wishes, requirements and ideas, without judgement. This can be done through interviews, existing documentation, user stories or a brainstorming session. Each item gets a short, unambiguous description. Resist the temptation to filter already: in this phase, quantity matters more than quality.
-
2Bring the stakeholders together
MoSCoW works best when different perspectives are represented: product owners, end users, technical leads and business stakeholders. Without business input, you get a technically biased prioritisation; without technical insight, unfeasible items get labelled as musts.
-
3Categorise together
Go through each requirement and ask the key question: "Can the product go live without this?" If the answer is "yes", it isn't a must. Next: "Would users be significantly hindered if it were missing?" If "yes", it's a should, otherwise a could. Items the group says "we'll do that next time" go to won't. Preferably use a visual aid: a whiteboard, sticky notes or a digital MoSCoW tool.
-
4Check the balance
A common rule of thumb is that must haves shouldn't take up more than around 60% of the total effort. The reasoning: if all the must haves together already consume the available budget and time, there's no room for setbacks. The should and could categories act as breathing room in the schedule. If the balance is skewed, reconsider whether certain musts are truly blocking.
-
5Adjust iteratively
MoSCoW isn't a one-off exercise. At every sprint review, scope change or new stakeholder input, you recalibrate the distribution. A should can be promoted to a must if user feedback calls for it; a must can be downgraded to a could if the market changes. The document evolves with the project.
Common mistakes in MoSCoW prioritisation
MoSCoW is simple in theory, but in practice we regularly see patterns that undermine its effectiveness. Learn to recognise these pitfalls before they hit your project.
-
Labelling everything as a Must
The most common mistake. Stakeholders feel pressure to position their requirements as indispensable. The result: a list where everything is "critical" and the team has no direction. If everything is a priority, nothing is. Set a maximum for must haves (for example 60% of planned capacity) and hold the group to it.
-
Ignoring or omitting Won't
Teams that skip the Won't category lose their best weapon against scope creep. Without an explicit "no" list, wishes quietly slip into the scope. Document Won't items as carefully as musts — they are your line of defence when stakeholders introduce new requirements halfway through the project.
-
Filling it in once and never updating it
A MoSCoW split agreed at the kickoff and never touched again soon reflects an outdated reality. Markets change, user feedback comes in, technical feasibility becomes clearer. Schedule regular moments (sprint reviews, phase closures) to recalibrate the split.
-
Prioritising too technically without business stakeholders
When only the development team runs the MoSCoW session, you end up with a prioritisation that is technically sound but commercially blind. The business sees different musts than developers do. A feature that is technically trivial can be commercially critical — and vice versa. Make sure both perspectives are at the table.
-
No differentiation within categories
MoSCoW gives you four buckets, but within each bucket everything is treated as equal. That works for a manageable feature list, but becomes problematic with large backlogs containing dozens of should haves. In that case, consider a secondary ranking within the categories, or combine MoSCoW with a numerical method for fine-grained prioritisation.
MoSCoW vs other prioritisation methods
MoSCoW is not the only way to prioritise requirements. Depending on the context — team size, backlog size, product maturity — a different method may be a better fit. Below, we compare MoSCoW with three commonly used alternatives.
| Aspect | MoSCoW | RICE scoring | Kano model | WSJF (SAFe) |
|---|---|---|---|---|
| Core | Qualitative classification into 4 categories | Numerical score: Reach x Impact x Confidence / Effort | Customer satisfaction model: basic, performance, delighter | Cost of Delay divided by job size |
| Complexity | Low — understandable for everyone | Medium — requires data-based estimates per factor | High — requires user research | High — requires knowledge of the SAFe framework |
| Best for | MVP definition, scope definition, workshops | Large product backlogs, data-driven teams | UX-driven product development | Enterprise agile, portfolio-level prioritisation |
| Weakness | No nuance within categories; subjective | False precision due to unreliable estimates | Requires time-intensive research | Overhead; of little use for small teams |
| When to choose | Need for quick consensus, mixed stakeholders | Large backlog, quantitative culture | Product-market fit phase, UX focus | Multiple agile teams, enterprise context |
Combining them can be valuable
In practice, these methods are not mutually exclusive. A common combination: start with MoSCoW for the rough split during a workshop, then use RICE scoring to determine the order within the should and could categories. That way you combine the accessibility of MoSCoW with the precision of a numerical model.
Applying MoSCoW in agile software development
MoSCoW fits seamlessly into an agile way of working. When setting up a product backlog, the method helps you fill the first sprints with must haves, followed by should haves in later iterations. The could haves form a reserve for sprints that run faster than expected, while won't haves are explicitly kept out of the current release.
In app development projects, we often use MoSCoW during the discovery phase to agree an MVP definition together with the client. The key question is: what must the first version of the application be able to do, at a minimum, to deliver value to users? Anything beyond the answer to that question is, by definition, not a must.
This approach prevents one of the most costly mistakes in software projects: building too much in the first release. An overloaded MVP translates into longer lead times, higher costs and delayed feedback from real users. MoSCoW provides the tool to have that conversation clearly.
Practical applications per phase
Sprint planning: user stories are tagged with their MoSCoW label. The sprint commitment covers all musts and as many shoulds as possible. Coulds are only included if the velocity forecast leaves room.
Scope negotiation: when a deadline is under pressure, MoSCoW gives you something solid to hold on to. The musts are protected; the shoulds and coulds are redistributed across later releases. Without MoSCoW labels, that discussion turns into a clash of opinions — with MoSCoW, it becomes a factual conversation.
Stakeholder communication: a one-page MoSCoW overview communicates more than a backlog of a hundred user stories. It gives executives and clients an instant view of what they will get, what will probably be included, and what has been explicitly excluded.
Want to try MoSCoW straight away on your own requirements? Use our interactive MoSCoW tool to categorise items and assess the distribution visually.
Frequently asked questions about the MoSCoW method
What does MoSCoW stand for?
MoSCoW is an acronym for Must have, Should have, Could have and Won't have (this time). The lowercase "o"s were added to make the word pronounceable and have no meaning of their own. The method was devised in 1994 by Dai Clegg at Oracle UK as part of the DSDM framework.
When do you use the MoSCoW method?
MoSCoW is most valuable when defining project scope, defining an MVP, or determining release content. The method works particularly well in situations where multiple stakeholders need to agree on priorities, such as kickoff workshops, sprint planning sessions or scope negotiations.
What is the difference between Should and Could?
A should have is important and will be delivered if the project runs normally — it has a noticeable impact on the user experience or business value. A could have is desirable but not impactful enough to create a firm expectation. The difference lies in the consequence of leaving it out: with a should, the user will notice; with a could, they probably won't straight away.
Can you still add Won't have items later?
Yes, that is exactly the point of the "this time" addition. Won't have does not mean "never", but "not in this release or iteration". With every subsequent planning cycle, won't haves can be reassessed. Some are promoted to could or should; others stay deliberately parked because the priorities don't change.
How do you prevent everything from becoming a Must have?
Set a capacity ceiling in advance: together, the must haves should not take up more than roughly 60% of the available project capacity. Force participants to answer the key question: "Will the project fail if this is missing?" That phrasing often leads to a more honest classification. An independent facilitator can help keep stakeholders focused.
Is MoSCoW suitable for large enterprise projects?
MoSCoW works well as a top-level prioritisation method, even at enterprise scale. For the detailed ordering of a backlog of hundreds of user stories it can be too coarse — in that case, consider combining it with RICE scoring or WSJF for fine-grained ranking. The strength of MoSCoW lies in quickly creating agreement at a strategic level, not in micromanaging individual tasks.
Which tools are available for MoSCoW prioritisation?
Besides physical methods (sticky notes, whiteboards), there are various digital tools. Appfront offers a free online MoSCoW tool that lets you categorise items straight away and assess the distribution visually. In addition, project management tools such as Jira, Azure DevOps and Notion support custom labels that you can use to assign MoSCoW tags to user stories.
Start your project with clear priorities
A well-prioritised project delivers results faster, stays within budget and avoids mid-project disagreements. We help you structure requirements and build software that does what it needs to do — from app development to consultancy.
The MoSCoW method is often used to sharpen the scope of an MVP; see also our guide to what an MVP is.