A prioritization framework that classifies features or requirements into four tiers: Must Have (non-negotiable for launch), Should Have (important but not critical), Could Have (desirable if time permits), and Won't Have this time (explicitly deferred). MoSCoW gives product and design teams a shared vocabulary for scope negotiation and prevents every feature from being labeled equally essential.
Common contexts
- Facilitating a scope alignment session between design, product, and engineering before a fixed-deadline release
- Using MoSCoW to make explicit which features are being deferred, preventing them from quietly re-entering scope mid-sprint
- Applying MoSCoW to a research plan to decide which questions must be answered before design begins versus which can be validated later
Use when
Use MoSCoW at the start of a project phase when scope is unclear and multiple stakeholders have competing priorities — the explicit categorization forces alignment conversations that otherwise surface as conflicts during build.
Avoid when
Don't let stakeholders classify features without providing rationale — a 'Must Have' label without user evidence or business justification is just an opinion, and the framework loses its value when everyone fights to put everything in the top tier.
The most useful output of a MoSCoW session is the 'Won't Have' list — explicit deferral is the only way to prevent scope creep from treating every cut as a temporary decision.
Real-world examples
- Booking.com sprint teams use MoSCoW during backlog grooming to separate core booking functionality (Must Have) from advanced filter options (Should Have) and experimental features (Won't Have this sprint).
- A healthcare startup used MoSCoW to cut their MVP scope by 60%: complex symptom tracking was moved to Won't Have, freeing engineering for the Must-Have medication reminder that drove initial retention.
- GOV.UK Design System team processes 200+ open component requests through a MoSCoW filter each quarter, ensuring core accessibility-critical components ship before decorative variant requests.