MoSCoW in one table
| Category | Meaning (ProductPlan) |
|---|---|
| Must have | Non-negotiable needs that are mandatory |
| Should have | Important, not vital, but adds significant value |
| Could have | Nice to have; small impact if left out |
| Won't have (this time) | Not a priority for this time frame |
ProductPlan credits the method to Dai Clegg, created while he worked at Oracle (ProductPlan).
Side by side
| Eisenhower matrix | MoSCoW | |
|---|---|---|
| Sorts | Tasks | Features, requirements, scope |
| Question | Urgent? Important? | How essential is it to this release? |
| Who | One person | Usually a team and stakeholders |
| Time frame | Today, this week | A release, a sprint, a project |
Using both
MoSCoW decides the scope of a project; once the Musts are set, the tasks that deliver them get sorted daily in the Eisenhower matrix. Musts with a near deadline land in quadrant 1; the rest in quadrant 2.
| Urgent | Not urgent | |
|---|---|---|
| Important | 1. Do it now Deadlines today, crises, problems that get worse if you wait | 2. Schedule it Planning, learning, health, relationships, long-term projects |
| Not important | 3. Delegate or shrink it Interruptions, many messages and meetings, other people's priorities | 4. Drop it Mindless scrolling, busywork, tasks nobody would miss |
Cronos, by Gambit Studio, is built around this: you drop each task into one of the four quadrants of a priority matrix by urgency and importance, on iPhone or iPad, so the important work stays in front and what can be delegated or dropped is in plain sight.