MoSCoW Prioritization

MoSCoW is a prioritization framework that categorizes features into four buckets: Must Have (non-negotiable for release), Should Have (important but not critical), Could Have (nice-to-have, cut first), and Won't Have (explicitly out of scope this time). The name is an acronym — the 'o's are added for pronunciation. It was developed by Dai Clegg at Oracle and is widely used in Agile and DSDM project management.

MoSCoW is categorical (four buckets) while RICE is numerical (produces a score). MoSCoW is faster and more intuitive — great for workshops and stakeholder alignment. RICE is more precise — better for comparing 20+ features objectively. Use MoSCoW for sprint-level planning and scope discussions. Use RICE for quarterly roadmap prioritization. Many teams use both: RICE to rank the backlog, then MoSCoW to scope individual releases.

The standard guideline is: Must Have should be no more than 60% of the total effort. If everything is a Must Have, nothing is — you've just created a list, not a prioritization. A healthy distribution looks like: Must Have (60% of effort), Should Have (20%), Could Have (20%), Won't Have (varies). The discipline is in saying 'this is important but not a Must.'

MoSCoW works best in three situations: (1) Sprint planning — deciding what goes into a time-boxed release, (2) Scope negotiation — when stakeholders want everything and you need to draw a line, (3) MVP definition — deciding what's essential for a first release vs. what can wait. It's less useful for long-term roadmap planning where RICE or outcome-based frameworks provide more nuance.

Apply the 'release test': if we launch without this feature, does the release fail? If users can't complete the core workflow, it's a Must. If the workflow works but is inconvenient, it's a Should. When stakeholders disagree, use user data: check your voting board for demand signals, or look at support ticket volume. Data resolves opinion-based conflicts faster than debate.

Absolutely — and you should. A feature voting board gives you real demand signals that inform categorization. A feature with 200 votes and 15 support tickets about it is clearly a Must Have. A feature with 5 votes is a Could Have at best. Tools like Features.Vote make this connection natural: vote counts inform your MoSCoW decisions, and the public roadmap shows users what category their requests are in.