When to use it
A useful fit
Use it when the time or capacity available is constrained and stakeholders can agree meaningful trade-offs.
Know the limits
Do not use it to call everything mandatory. If the minimum viable scope exceeds capacity, change the scope, date or resources explicitly.
How to use it
- Agree the decision owner and the test for an essential requirement.
- Prioritise against a specific increment and examine effort as well as item count.
- Record exclusions, acceptance conditions and the process for changing priorities.
Worked example
A permit service must accept applications and issue a receipt before launch. A saved-search feature is useful but can wait. The team records it outside the first increment and tests whether users can complete the essential workflow without it.
Illustrative scenario by fannarmaximus; not an official exam question.
Common pitfalls
A low-effort optional item does not compensate for an oversized essential requirement.
Attribution & sources
Dai Clegg, with Richard Barker, is credited for MoSCoW; the Agile Business Consortium documents its use in DSDM. This example is original.
The citations below identify authoritative references for this topic. They do not imply endorsement or reproduce the bodies’ competence lists.
- Clegg, D. & Barker, R. (1994). CASE Method Fast-Track: A RAD Approach. Wokingham: Addison-Wesley. ISBN 9780201624328.
- Agile Business Consortium. "MoSCoW Prioritisation". In DSDM Project Framework Handbook (online edition; the framework was first printed in 2014). https://www.agilebusiness.org/dsdm-project-framework/moscow-prioritisation.html, accessed 26 September 2026.