MoSCoW method explained
It is most useful on a fixed deadline. Must-haves define the smallest release that works; everything else is negotiable.
The "Won't have" list matters too. Writing it down stops scope from quietly creeping back in.
Try it today
- List every feature or task for the release.
- Label each one M, S, C or W, and keep Must-haves to a minority.
- Plan the Must-haves first and treat the rest as optional.
Where it comes from
Dai Clegg developed MoSCoW at Oracle in 1994 for rapid application development projects. It later became a core technique of the DSDM agile framework.
Frequently asked questions
- What is the MoSCoW method?
- The MoSCoW method sorts requirements into Must have, Should have, Could have and Won't have (this time), so a team knows what to cut when time runs short.
- Where does the MoSCoW method come from?
- Dai Clegg developed MoSCoW at Oracle in 1994 for rapid application development projects. It later became a core technique of the DSDM agile framework.
- How do I start with the MoSCoW method?
- List every feature or task for the release. Label each one M, S, C or W, and keep Must-haves to a minority. Plan the Must-haves first and treat the rest as optional.
- Which tools help with the MoSCoW method?
- Tools in our directory that help include Linear, Trello, Notion, ClickUp. Each has its own page with pricing, pros and cons.
