MoSCoW sorts requirements for a release or a time-box into four groups:
- Must have: without it, the release is pointless, illegal or unsafe. Test: "If this is missing, would we cancel the release?" If not, it is not a Must.
- Should have: important, but there is a workaround for a while.
- Could have: wanted, and the first thing to drop if time runs short.
- Won't have this time: agreed as out of this release. Writing it down stops the same request coming back every week.
The method comes from DSDM (now the Agile Business Consortium), which adds a useful rule: keep the Musts to about 60% of the effort, so the Shoulds and Coulds form a contingency. When everything is a Must, nothing is: the team has no room to absorb a surprise, and the date slips.
Prioritize with the people who own the value, against a clear goal for the release. Legal and regulatory requirements are usually Musts whatever anyone prefers.
MoSCoW, with Musts kept to about 60% of the effort.