Skip to content
Founders’ price Launch pricing for your first twelve months. 40 Playbooks, 40% discount for Founders. View the playbooks →

MoSCoW Prioritisation

TTool · MoSCoW Prioritisation

By , Editor · · What’s Next

Everyone's defending their own work. Nothing's coming off the list. The deadline isn't moving.

MoSCoW sorts the work into four buckets. Must have — or the thing fails. Should have — important, not vital. Could have — nice if there's room. Won't have — not this time. It comes from the Dynamic Systems Development Method, an agile framework that treated deadlines as real.

Four stacked priority bands labelled must (or the thing fails), should (important - not vital), could (nice if there's room), and won't (not this time), under the heading 'the won't have list is what saves you.'
Method visual — MoSCoW Prioritisation
A move inside a Playbook

“Someone senior is going to try to hijack the next meeting.”

Open the Playbook →