MoSCoW Plan: Must, Should, Could, Won't (With Example)
8 min read ยท 2026-10-23
A MoSCoW plan is a project or release plan that puts every requirement into one of four groups: Must have, Should have, Could have or Won't have this time. The deadline stays fixed and the scope can change. If time runs short, everyone already knows which work is protected and which work gets dropped.
This guide is about the MoSCoW prioritization method. It is not about the 1935 General Plan for the city of Moscow. You get the official DSDM definitions, a quick test to spot a real Must have, the effort split that keeps a plan safe, a full example with estimates, and a way to turn your categories into a roadmap with phases.
The roadmap at a glance
Goal: Build a MoSCoW plan for one release or quarter that fits your team's capacity and keeps a safety margin. Duration: 2 weeks of scoping, then the delivery period (often one quarter)
Frame the time box (Days 1 to 2)
Set the fixed deadline, the team's capacity and the goal behind every MoSCoW decision.
- Confirm the deadline and make sure it really cannot move.
- Count the team's capacity in person-weeks, minus holidays and support duties.
- Write one sentence that describes success for this release.
- Name one person who makes the final call when people disagree about a category.
Milestone: A written goal, deadline, capacity figure and named decision-maker.
Collect and estimate requirements (Days 3 to 5)
Put every candidate requirement into one list, in a format that makes items easy to compare.
- Gather requests from stakeholders, the backlog, user research and legal or compliance obligations.
- Write each one as a short requirement with acceptance criteria.
- Ask engineering and design for a rough effort estimate on each item.
- Mark the dependencies between items.
Milestone: One estimated list of requirements, with dependencies marked.
Categorize with stakeholders (Days 6 to 8)
Put every requirement into Must, Should, Could or Won't, using tests the whole group has agreed on.
- Start every item as Won't have, so moving it up needs a reason.
- Run the Must test on every proposed Must.
- Ask whether a workaround exists. This separates Shoulds from Coulds.
- Write down the reason for each Must.
- Send unresolved disputes to the decision-maker. Don't settle them halfway.
Milestone: Every item has a category, and every Must has a written reason.
Balance against capacity (Days 9 to 10)
Check that the scope fits the time box and still leaves a buffer.
- Add up the Must effort and keep it at 60 percent of capacity or less.
- Keep about 20 percent of capacity for Coulds as contingency.
- Move Musts down if they go over the limit. Rewrite the goal if needed.
- Schedule Musts first and Coulds last.
Milestone: A balanced scope signed off by the decision-maker.
Deliver and defend the scope (The delivery period)
Use the categories to make fast tradeoffs when estimates slip.
- Check progress on the Musts every week.
- When work runs over, drop Coulds first, then Shoulds.
- If someone adds a new Must, remove existing work of the same effort.
- Review the Won't list at the end and use it for the next planning cycle.
Milestone: All Musts shipped on the deadline, with a record of what was traded away.
What the MoSCoW method means
The MoSCoW method comes from the DSDM agile framework. The capital letters stand for the four categories. The two lowercase o's mean nothing. They are only there to make the word easy to say.
DSDM gives each category a precise meaning. The definitions below follow the "What is MoSCoW Prioritization?" page from the Agile Business Consortium, the organization behind DSDM. Use them in place of vague labels like "high" or "low" priority.
The method only works with a fixed time box. Without a deadline, nothing forces a tradeoff, and every item slowly drifts toward Must.
- Must have: part of the Minimum Usable Subset, the set of requirements the project guarantees to deliver. DSDM spells it with a capital T at the end, "Minimum Usable SubseT", so the first letters spell MUST. Without these requirements, the release has no point.
- Should have: important but not vital. The release still works without it, even if leaving it out hurts.
- Could have: wanted or desirable, but leaving it out has less impact. These are the first items to drop.
- Won't have this time: agreed to be out of scope for this time box. It is not rejected forever.
How to tell a Must have from a Should have
DSDM gives a blunt test: if this requirement is not delivered, would you cancel the project? If the honest answer is no, it is not a Must. Then look for a workaround. If one exists, even a manual and painful one, the item is a Should have or a Could have.
The difference between Should and Could is how much it hurts to leave the item out. If leaving it out causes real pain or forces an awkward workaround, it is a Should. If it causes a small loss that most users would barely notice, it is a Could.
Here is the test applied to real requirements.
- Tax handling on invoices: in this example, assume the law requires it. There is no workaround, so it is a Must.
- Emails for failed payments: support can contact customers by hand for a few weeks, so it is a Should.
- Usage charts: customers can ask for a report, and few would notice they are missing, so it is a Could.
- Multi-currency billing: nobody needs it for this launch, so it is a Won't have this time.
The 60 percent rule, worked through
DSDM recommends that Must haves take no more than 60 percent of the total effort. Could haves take about 20 percent and act as the safety margin. Should haves fill the rest. If estimates turn out too optimistic, the team drops Coulds, then Shoulds, and still delivers every Must on time.
Take a team of 5 people with an 8-week release. That makes 40 person-weeks of capacity. Musts can use up to 24 person-weeks. About 8 person-weeks go to Coulds, and Shoulds get the other 8. If your Musts add up to 30 person-weeks, the plan is broken before it starts. Move something down, or move the deadline.
Write the rule into the plan so nobody argues about it later. A plan that is 100 percent Musts has no room to absorb a delay.
A complete MoSCoW plan example
A team is launching a self-serve billing portal. They have 40 person-weeks. The numbers in brackets below are estimates in person-weeks.
Musts stay under the 60 percent limit, and Coulds give a 20 percent buffer. In week 5, the payment method update runs over because of a problem with the payment provider integration. The team drops usage charts and dark theme, keeps plan changes, and moves failed payment emails to a quick follow-up release. The launch date holds. Nobody is surprised, because everyone agreed in advance which items were at risk.
- Must have (20, 50 percent): view invoices (4), update payment method (6), download receipts (3), tax handling (7).
- Should have (12, 30 percent): plan upgrades and downgrades (6), failed payment emails (4), invoice search (2).
- Could have (8, 20 percent): usage charts (5), dark theme (2), CSV export (1).
- Won't have this time: multi-currency, reseller billing, mobile app. The team will review them at the next quarterly planning.
From MoSCoW prioritization to a roadmap
Placing MoSCoW categories on a roadmap turns your list into a timeline. MoSCoW decides what goes in. The roadmap decides when. Put Musts and their dependencies in the first phases. Put Shoulds in the middle and Coulds at the end, where you can cut them without affecting anything else.
For a long-term roadmap, choose the themes or outcomes first. Then run MoSCoW on each release inside them. The method protects deadlines well, but it does not set your strategy.
A simple layout looks like this.
- Phase 1: Musts that other work depends on, such as tax handling and invoice data.
- Phase 2: the remaining Musts, then the Shoulds with the most value.
- Phase 3: the other Shoulds, then Coulds if time is left.
- Parking lot: Won't haves, each with a review date.
Handling stakeholders who want everything as a Must
People quickly learn that only Musts get built, so they label everything a Must. Starting every item at Won't reverses this: you have to justify putting an item in, not keeping it out. Reading each Must's reason out loud during the review also helps, because weak reasons sound weak.
MoSCoW sorts items into groups but has no built-in way to rank them, so the result depends on who is in the room. To keep it fair, invite every stakeholder group to the categorization session, apply the Must test the same way to everyone, and let the named decision-maker settle ties. Never resolve a dispute by calling something "a soft Must."
MoSCoW vs RICE, Kano and value versus effort
MoSCoW puts items into groups but does not rank them inside a group. If you have 6 Shoulds and room for 3, you need a second tool.
Use MoSCoW to protect the deadline, and a scoring method to order the work inside each category.
- RICE scores each item on Reach, Impact, Confidence and Effort. Use it to rank items inside a category.
- Kano sorts features by how they affect customer satisfaction: basic needs, performance features and delighters. Use it to understand what users expect.
- Value versus effort is a quick two-axis grid. Use it when you need an answer in one meeting.
Common mistakes to avoid
- Labeling most items as Must removes the buffer. Cap Musts at 60 percent of effort.
- Categorizing before estimating effort makes the 60 percent rule impossible to check. Estimate first.
- Running MoSCoW without a fixed deadline makes the categories meaningless. Set the time box before anything else.
- Treating Won't as rejected forever upsets stakeholders. Give each Won't a review date.
- Starting Coulds before the Musts are safe puts the launch at risk. Schedule by category.
- Leaving disputes open stalls the plan. Name one decision-maker on day one.
Frequently asked questions
What is a MoSCoW plan?
A MoSCoW plan is a release or project plan where every requirement is labeled Must have, Should have, Could have or Won't have this time. The deadline is fixed and the scope can change. When work runs late, the lower categories are dropped first.
What does MoSCoW stand for in the MoSCoW method?
It stands for Must have, Should have, Could have and Won't have this time. The lowercase o's mean nothing and only make the acronym easy to say. It comes from the DSDM agile framework.
How much effort should go to Must haves in MoSCoW prioritization?
DSDM recommends that Musts take no more than 60 percent of the effort, with Could haves at about 20 percent as contingency. Should haves fill the rest. The buffer lets you deliver every Must even when estimates slip.
Can you use MoSCoW in a sprint?
Yes. Keep the same rules at a smaller scale. Sort the sprint backlog into the four groups, keep Musts within the 60 percent limit, and drop Coulds first if the sprint runs over.