Back

The MoSCoW method for task prioritization

Sort project work into Must, Should, Could and Won't (this time). What each letter really means, the 60% rule, a worked example and a dypt setup.

The MoSCoW method for task prioritization

Plays from YouTube

On this page8 sections

The MoSCoW method sorts work into four groups: Must have, Should have, Could have and Won't have (this time). It was built for software projects with a fixed deadline, but it works just as well for a personal project, a house move or a busy week: anywhere you have more to do than time to do it.

This guide covers where MoSCoW comes from, what each letter really means (including the often-muddled W), a worked example, and how to set it up in dypt with tags.

Where the MoSCoW method comes from

MoSCoW is usually credited to Dai Clegg, who developed it at Oracle in the 1990s. It became the standard way to prioritise in DSDM, an agile project framework now looked after by the Agile Business Consortium.

The name is just the four letters M, S, C and W, with two o's added to make it easy to say. It has nothing to do with Moscow.

What each letter means

The definitions below follow the Agile Business Consortium's guide.

  • Must have. Without these, the project fails or can't go ahead. DSDM describes them as the minimum the project guarantees to deliver. Ask: "If this were left out, would we cancel or delay?" If the answer is no, it's not a Must.
  • Should have. Important but not vital. Leaving it out would be painful, but the result still works.
  • Could have. Wanted or nice to have, but less important. These are the first things to drop when time runs short.
  • Won't have this time. Things everyone agrees won't be done in this timeframe. They're not rejected for ever, just not now.

The W causes the most confusion. You'll sometimes see it written as "Would like to have", which makes it sound like a fifth level of nice-to-have. It isn't. The W is a decision: this is out of scope for now. Writing it down is useful, because it stops the same ideas creeping back in halfway through.

The rule that keeps it honest

MoSCoW only works if most of the work isn't a Must. DSDM's guidance is that Must haves should typically be no more than about 60% of the effort, with around 20% as Could haves that can be dropped if things overrun.

That buffer is the point. If everything is a Must, there's nothing to drop when the deadline gets close, and the method stops helping.

A worked example

Here's a made-up example: moving house in four weeks.

TaskGroupWhy
Book the removal vanMustNo van, no move
Redirect your postMustImportant letters would go missing
Pack the kitchenMustYou can't move without packing
Sell the old sofaShouldSaves moving it, but you could take it with you
Repaint the spare room before moving inCouldNice to have; easier when the room's empty
Re-tile the bathroomWon't (this time)A project for next year

Three Musts, one Should, one Could and one Won't. If week three goes badly, the repainting goes first, and nobody is surprised.

Common mistakes

  • Everything is a Must. Then nothing is. Push hard on each Must: would the project really fail without it?
  • Treating Won't as "maybe later". A Won't is a decision for this timeframe. Write it down so it doesn't sneak back in.
  • No timeframe. MoSCoW sorts work against a deadline or a time box. Without one, Should and Could blur together.
  • Never revisiting. Priorities change. Review the groups when something big changes, not just at the start.

How to do the MoSCoW method in dypt

dypt has four priority levels (High, Mid, Low and none), but MoSCoW is clearer with tags, because the letters mean something specific.

  1. Make a parent task for the project. For example, "Move house". Give it a deadline: MoSCoW needs a timeframe.
  2. Create four tags: must, should, could and wont. Add one to each task under the project.
  3. Filter by tag to see one group at a time. Start with must. When the Musts are done or under way, move to should.
  4. Keep the Won'ts. Don't delete them; leave them tagged wont so the decision is written down. Next time you plan, filter for wont to see what was parked.
  5. Optionally, match priority too. If you also want MoSCoW to show up when you sort by priority, set Musts to High, Shoulds to Mid and Coulds to Low.

If a Must feels too big to start, use dypt's AI task breakdown to split it into smaller steps. If you're working with others, you can share the project with them. You can read more about custom tags and priorities, deadlines and reminders on their feature pages.

Try it on your next project

Pick one project with a deadline. Sort every task into Must, Should, Could or Won't this time, then check that the Musts are well under two-thirds of the work. If they're not, push some down.

If you'd like the groups, the deadline and the breakdown in one place, try it in dypt, free to start.

Sources and further reading

Part 17 of 23

Do the thing

Productivity methods, one at a time: what each method is for, where it really comes from, and how to try it in dypt. Most parts go with an episode of our Do the thing videos.

  1. 1Task prioritization methods: how to choose the right one
  2. 2Eisenhower matrix: sort tasks by urgent and important
  3. 3The Ivy Lee method: write tomorrow's six tasks tonight
  4. 4'Eat That Frog': tackle your most daunting tasks first
  5. 5Eat the frog vs the Eisenhower matrix: which to use?
  6. 6The two-minute rule: do small jobs now, don't list them
  7. 7Parkinson's law: why a 10-minute job takes all afternoon
  8. 8The Pomodoro technique: one task, 25 minutes, a break
  9. 9Time blocking: how to actually find time for your work
  10. 10Pomodoro vs Time Blocking vs Timeboxing: Start, Plan or Stop?
  11. 11The 80/20 rule: find the few tasks that matter most
  12. 12Pickle Jar Theory: fit the big work into busy weeks first
  13. 13Most important tasks (MITs): do your top three first
  14. 14The 1-3-5 rule: plan one big job, three medium and five small
  15. 15MIT, Ivy Lee or 1-3-5: which prioritization method to use?
  16. 16ABC method for task prioritization: the ABCDE version
  17. 17The MoSCoW method for task prioritization
  18. 18Getting Things Done (GTD), plainly explained
  19. 19Don't break the chain: how to keep a new habit going
  20. 20The weekly review: give every project its next step
  21. 21Personal kanban: the WIP limit matters more than the board
  22. 22Task batching: group similar small jobs into one session
  23. 23Timeboxing: decide when to stop before you start
Dane Poyzer

Written by

Dane Poyzer

Chartered accountant turned developer, building the tools I always wished existed.