MoSCoW Prioritization Template for Prioritization

RICE produces a numeric score that ranks features on a continuous scale. MoSCoW produces categorical buckets that define scope boundaries. RICE answers "what order should we build these in?" MoSCoW answers "what is in scope and what is out?" Many teams use both: MoSCoW to set the release boundary, then [RICE](/tools/rice-calculator) to sequence the items within Must Have and Should Have. For a detailed comparison, see [RICE vs ICE vs MoSCoW](/compare/rice-vs-ice-vs-moscow).

This is the most common failure mode. Push back by defining Must Have as "the release is useless without this." Not "important." Not "high priority." Useless. Then walk through each item and ask: "If this feature is missing on launch day, do we cancel the launch?" Most items do not pass that test. If stakeholders still resist, show the effort math. If Must Haves exceed 100% of capacity, something must move.

It works better for time-boxed releases than for ongoing backlogs. For continuous delivery, a ranked list (RICE or weighted scoring) is more practical because the categories blur when there is no fixed deadline. Use MoSCoW when you have a specific ship date and need to define what is in vs. out.

"Won't Have (this time)" means explicitly excluded from this release but acknowledged as a valid future request. It is not a rejection. It is a deferral with a clear rationale. This distinction matters because it validates the stakeholder's request while protecting the current scope.

Once per release or planning cycle. For quarterly planning, run it at the start of each quarter. For a specific launch, run it once during scoping and then revisit only if a major constraint changes (timeline moves, team size changes, new competitor launches). Avoid re-running mid-sprint. Constant re-prioritization undermines team confidence and velocity. ---