MoSCoW Prioritisation

MoSCoW prioritisation is one of the most important techniques in AgilePM. It allows teams to deliver on time by deciding, upfront, what is essential and what can be deferred. The technique is applied at both the project level (to prioritise overall requirements) and at the timebox level (to prioritise what gets done within a sprint).

The key insight is that by classifying requirements as Must/Should/Could/Won't, teams create built-in flexibility — if time runs short, Could-haves are dropped rather than the entire timebox being extended.

Key Points

• Must have: Non-negotiable requirements — project fails without them
• Should have: Important but not vital — workaround exists if dropped
• Could have: Desirable but lower priority — first to drop if time short
• Won't have: Not in this delivery — documented to set expectations
• Must haves should be <60% of total effort to allow flexibility
• Prioritisation should involve both business and technical stakeholders
• MoSCoW is applied at both project and timebox level
• Requirements can be re-prioritised between timeboxes as understanding grows

Key Terms & Definitions

Must Have

A requirement that is fundamental to the success of the project. If it is not delivered, the project is a failure.

Should Have

A requirement that is important but not vital. There may be an alternative or workaround if it is not delivered.

Could Have

A requirement that is desirable but not necessary. It will be included if time and resources allow.

Won't Have

A requirement that the team has agreed will not be delivered in this timebox, but may be considered for the future.