Skip to content
Planet RoadmapPlanet Roadmap
Sign InGet Started
Glossary
Prioritization

What is MoSCoW Method?

The MoSCoW Method is a prioritization framework used to reach a common understanding with stakeholders on the importance of project requirements. It divides tasks into four categories: Must have, Should have, Could have, and Won't have (this time). This classification helps teams focus on delivering the most critical value first while managing limited resources.

When to use it

Teams should use the MoSCoW Method during sprint planning or roadmap development to resolve conflicts over feature priority. It is particularly effective when working with stakeholders who perceive all requests as high priority, as it forces a distinction between non-negotiables and nice-to-haves. This approach solves the problem of scope creep by explicitly defining what will not be included in a specific timeframe.

Example

A SaaS team prioritizing 12 features for a Q3 release might identify 'User Authentication' and 'Data Encryption' as Must-haves for security compliance. They categorize 'Bulk CSV Export' as a Should-have, which is important but not vital for the initial launch. 'Custom Profile Themes' are labeled as Could-haves, while 'Legacy System Integration' is designated as a Won't-have for this quarter to ensure the team hits their primary deadline.

How Planet Roadmap helps with MoSCoW Method

Planet Roadmap features a Kanban view where you can create custom tags or columns for Must, Should, and Could categories to visualize your priorities. You can also use the sprint board to organize your backlog and drag items into active iterations based on their MoSCoW status.

Try Planet Roadmap free

FAQ

How do you distinguish between a 'Must have' and a 'Should have'?
A Must-have is a non-negotiable requirement; without it, the project is considered a failure or potentially illegal. A Should-have is painful to leave out, but the product remains viable and functional for the end user without it.
What percentage of the budget should go to 'Must have' items?
A common rule of thumb is to limit Must-have items to no more than 60% of the total effort or budget. This provides a necessary buffer to ensure that if the project runs over, you can drop Could-haves or Should-haves without compromising the core delivery.

Related terms

RICE ScoreICE ScoreKano ModelWeighted ScoringValue vs Effort MatrixProduct BacklogSprint PlanningMinimum Viable Product (MVP)

Read more

Build your roadmap with Planet Roadmap

One workspace for feedback, roadmap, project management, and OKRs — flat-rate pricing, no credit card required.

Try Planet Roadmap Free