MoSCoW is a prioritisation technique used to reach a common understanding with stakeholders on the importance of delivering each requirement.

MoSCoW stands for:

• Must have: These are the non-negotiable requirements. If these aren't delivered, the project is considered a failure.
• Should have: These are important requirements that should be included if possible, but the project can still succeed without them.
• Could have: These are desirable requirements that can be included if time and resources allow, but they're not essential.
• Won't have: These are requirements that are not planned for this iteration or release. They may be considered in the future.

It's a simple but powerful framework that helps you to:

1. Focus on the most critical requirements.
2. Manage stakeholder expectations.
3. Make informed decisions about resource allocation.
4. Deliver value quickly and efficiently.

This PDF and Google Sheet resource provides a structured template for conducting your own MoSCoW prioritisation exercise. It includes two extra fields, Overview and Rationale, to provide additional context and justification for each prioritisation decision. This ensures that you and your team are aligned on the reasons why something is considered a "Must have" or a "Won't have".

Here's why it's great: the template also gets you to consider the Overview and the Rationale. The Overview of the task, and the Rationale for why it sits in one of the areas of the MoSCoW method. It's about more than just saying what is important, but actually backing it up.

Download the Template

Choose either the PDF or Google Sheet version. The Google Sheet is ideal for team collaboration.

List Your Requirements

Start by listing all the requirements for your project or product. Be as comprehensive as possible.

Prioritise Each Requirement

Work through each requirement and assign it to one of the four MoSCoW categories: Must have, Should have, Could have, or Won't have.

• Must have: These are the absolutely essential requirements. If these aren't delivered, the project will fail.
• Should have: These are important requirements that you should try to include, but the project can still succeed without them.
• Could have: These are desirable requirements that you can include if time and resources allow, but they're not critical.
• Won't have: These are requirements that you're not planning to include in this iteration or release.

Add Overview and Rationale

For each requirement, provide a brief overview of what it entails and a clear rationale for why you've assigned it to that particular MoSCoW category.

Validate Your Prioritisation

Review your prioritisation with your team and stakeholders. Do they agree with your assessment? Are there any requirements that need to be re-categorised?

Use Your Prioritisation

Use your MoSCoW prioritisation to guide your decision-making and resource allocation. Focus your efforts on delivering the "Must have" requirements first, followed by the "Should have" requirements, and so on.

Be honest with yourself and your team. Don't be afraid to say "Won't have" to a requirement that's not truly essential.

Involve your stakeholders in the prioritisation process. This will help to ensure that everyone is aligned on the priorities.

Focus on delivering value quickly. Prioritise the requirements that will deliver the biggest impact in the shortest amount of time.

Regularly review and update your prioritisation as your project evolves. Priorities may change as you learn more and as the market shifts.

And remember, MoSCoW prioritisation is just a tool. It's not a substitute for good judgment and communication.