Glossary Term
MoSCoW Method
A prioritization technique that sorts requirements into Must have, Should have, Could have, and Won't have for this release. It forces clear tradeoffs instead of treating everything as equally urgent.
Example: A team has eight weeks to launch. Login and payments are Musts, email receipts are a Should, dark mode is a Could, and the admin dashboard is a Won't for this release. When week six slips, everyone already knows what gets cut first.
How to prioritise features with MoSCoW
Share it