Every project starts with more ideas than time. Stakeholders want new features, users ask for improvements, and the team spots technical work that needs doing. Sooner or later, someone has to answer a hard question: what are we actually going to deliver, and what can wait?
The MoSCoW method is one of the most widely used tools for answering that question. It is easy to explain, works for projects of any size, and creates a shared language for negotiating scope. In this article, you will learn what each category means, how to run a MoSCoW session, and the mistakes that make the technique fail.
Where the Name Comes From
The technique was created by Dai Clegg in the 1990s and became closely associated with DSDM (Dynamic Systems Development Method), one of the early agile frameworks. The name has nothing to do with Russia: it is an acronym built from four categories, with the lowercase “o”s added only to make it pronounceable.
| Letter | Category | What it means | Test question |
|---|---|---|---|
| M | Must have | Non-negotiable for this delivery | Is the release pointless or unsafe without it? |
| S | Should have | Important, but a workaround exists | Would it hurt to delay it, but not fatally? |
| C | Could have | Nice to have if time allows | Would anyone notice if it slipped? |
| W | Won’t have (this time) | Explicitly out of scope for now | Have we agreed to park it? |
The Four Categories in Detail
Must have
These are the requirements without which the delivery fails. If any one of them is missing, the product does not work, is not legal, or does not solve the core problem. A useful test is to ask: “If this isn’t ready, would we still release?” If the honest answer is no, it is a Must.
Should have
Should items add significant value, but the release can survive without them for a while, usually thanks to a manual process or a temporary workaround. They are typically the first things to be added once the Musts are safe.
Could have
Could items improve the experience but have a smaller impact. They act as a buffer: if the project runs late or something unexpected happens, these are dropped first without damaging the main outcome.
Won’t have (this time)
This category is often skipped, but it is one of the most valuable. Writing down what you are not doing prevents scope creep, avoids repeated debates, and keeps good ideas on record for a future phase. “Won’t” means “not in this timeframe”, not “never”.
A Practical Example: A Gym Booking App
Imagine a small gym that wants an app so members can book classes. The first version must launch before the new year. A MoSCoW breakdown might look like this:
- Must: member login, class timetable, booking and cancellation, and a list of bookings for instructors.
- Should: automatic reminders and a waitlist for full classes. Until they exist, staff can send reminders and manage waitlists by hand.
- Could: instructor profiles, a favorites list and a dark mode.
- Won’t (this release): in-app payments and wearable device integration.
With this list, everyone knows what launch day requires and what is a bonus. If development hits a snag, the team already knows what to cut.
How to Run a MoSCoW Session
- Set the objective and timebox. Prioritization only makes sense against a clear goal, such as “launch version one by March”.
- Collect all requirements. Gather input from stakeholders, users and the delivery team without filtering yet.
- Agree on criteria first. Decide together what makes something a Must: legal obligations, safety, core user value, technical dependencies.
- Categorize collaboratively. Discuss each item with the people affected. Prioritization imposed by one person rarely sticks.
- Check the effort balance. Estimate the work and make sure the Musts fit comfortably within the available time.
- Publish the result. Share the list openly, including the Won’ts.
- Revisit regularly. Priorities shift; review the list at each iteration or milestone.
How Much Should Be a “Must”?
DSDM guidance commonly recommends keeping Must items to no more than about 60% of the total planned effort, with the remainder split between Should and Could. The reasoning is straightforward: if everything is mandatory, there is no contingency, and any delay threatens the entire delivery. Could items, in particular, function as a reserve you can sacrifice to protect what matters most.
Strengths and Limitations
| Strengths | Limitations |
|---|---|
| Simple enough for non-technical stakeholders | Does not rank items within a category |
| Forces explicit conversations about value | Can become political without agreed criteria |
| Makes out-of-scope items visible | Does not account for cost or effort by itself |
| Fits well with fixed deadlines | Needs frequent review when requirements change quickly |
Because of these limitations, teams often pair MoSCoW with effort estimates or a value-versus-complexity matrix to decide the order of work inside each group.
Common Mistakes to Avoid
- Labeling almost everything as Must. If 90% of items are mandatory, no real prioritization has happened.
- Ignoring the Won’t category. Without it, rejected ideas come back in every meeting.
- Prioritizing alone. Decisions made without stakeholders tend to be challenged later.
- Treating the list as fixed. A Could today can become a Must tomorrow because of new regulations or market changes.
- Confusing urgency with importance. A request marked “ASAP” is not automatically essential to the goal.
Conclusion
The MoSCoW method turns an overwhelming wish list into a realistic delivery plan. By separating what is essential, important, nice to have and deliberately postponed, teams gain focus, stakeholders know what to expect, and tough trade-offs are recorded transparently instead of being argued over again and again.
If you want to strengthen your skills in scope management, agile practices and planning, explore the free project management courses on Cursa, which you can take at your own pace and finish with a certificate.
























