Skip to content
Prioritization5 min readLast updated

MoSCoW Prioritization: Method, Rules & Examples

When your backlog is overflowing and every feature feels important, you need a structured way to decide what matters most. The MoSCoW method is one of the simplest and most widely used prioritization frameworks. It forces teams to have honest conversations about what is truly essential versus what is merely desirable, making it a great starting point for teams new to formal prioritization.

The Four Categories

MoSCoW stands for Must Have, Should Have, Could Have, and Won't Have. Must Have items are non-negotiable requirements without which the product or release fails. Should Have items are important but the product can launch without them. Could Have items are nice to include if time and resources allow. Won't Have items are explicitly out of scope for now.

  • Must Have: Critical for the release to be viable.
  • Should Have: Important but not a dealbreaker if delayed.
  • Could Have: Desirable if there is remaining capacity.
  • Won't Have: Acknowledged but explicitly deferred.

How to Run a MoSCoW Session

Gather your product team, key stakeholders, and engineering leads. Present each feature or initiative and ask the group to assign it to one of the four categories. The most productive discussions happen around the boundary between Must Have and Should Have. If everything is a Must Have, the exercise has failed. A good rule of thumb is that Must Haves should represent no more than 60 percent of available effort.

Planet Roadmap lets you tag features with priority levels, making it easy to apply MoSCoW categories to your backlog and filter your roadmap view by priority tier.

When MoSCoW Works Best

MoSCoW is most effective for scoping a specific release or sprint rather than long-term strategic planning. It works well when you have a fixed timebox and need to decide what fits. It is less useful for comparing features with very different levels of complexity because it does not account for effort.

Limitations to Keep in Mind

MoSCoW does not provide a rank order within each category. Two Must Have items might have very different levels of urgency, and MoSCoW will not help you distinguish between them. It also relies heavily on group judgment, which can be influenced by the loudest voice in the room. Pair MoSCoW with data-driven approaches for stronger results.

Try the free tool
Related templates

Related terms

Frequently asked questions

What does MoSCoW stand for?
Must have, Should have, Could have, and Won’t have (this time). The lowercase o’s just make the acronym pronounceable.
How many items should be 'Must have'?
Keep Musts to roughly 60% or less of total effort. If everything is a Must, the method has failed — Musts are only the items without which the release has no value.
Is MoSCoW better than RICE?
They solve different problems. MoSCoW is a fast, qualitative way to agree on scope for a release; RICE is a quantitative way to rank a large backlog. Many teams use both.
When should you use MoSCoW prioritization?
Use MoSCoW when you have a fixed timebox — a release, sprint, or deadline — and need the team and stakeholders to agree quickly on what fits. It is less suited to long-term strategy or to comparing features with very different effort levels, since it ignores cost.
What is the purpose of the Won't Have category?
Won't Have makes deferral explicit so it is documented rather than silently dropped or forgotten. Naming what is out of scope this time protects the timebox, sets stakeholder expectations, and gives you a ready-made shortlist to revisit in the next planning cycle.

Related reading

Liked this? Get the weekly digest.

Tuesday mornings. One deep read, one tool, one template. See what an issue looks like →

Ready to start collecting feedback?

Try Planet Roadmap free — no credit card required.

Get Started for Free