The MoSCoW method is a prioritization technique used by teams and their interest holders to classify requirements, tasks, ideas, or features into four categories:
- M – Must have: critical, non-negotiable requirements
- S – Should have: important but not vital; can be saved for later
- C – Could have: nice to have, but low impact or optional
- W – Won’t have (now): agreed to be out of scope for now
This is a collaborative method to negotiate priorities and narrow down your team’s focus.
Best Practices
Involve interest holders early. This will ensure everyone has shared understanding on priorities before any work begins.
Limit must-haves. If everything is a priority, then nothing is! These should only include truly essential items.
Define each category clearly. Don’t let “should” or “could” creep into “must”.
Basic Steps
1. List items in need of prioritization. What tasks, ideas, or requirements do you need clarity on?
2. Assign each item to a category. Invite participants to discuss their perspectives. Once a consensus is reached, include a short description on why it falls within the chosen category.
3. Validate priorities with key interest holders. This can help ensure buy- in and support as you move forward in your project.
4. Deliver “musts” first. Be sure to estimate effort and adjust scope based on time and resource constraints. Implement “shoulds” and “coulds” as time allows.
5. Review periodically. As the project evolves, you may need to adjust your priorities.
Benefits
- Clarifies expectations so your team knows what’s essential versus optional
- Defines the scope and what will be intentionally excluded from the project
- Adapts easily to different teams and their needs
Our Recommended Resources
Use the MoSCoW method when you have limited time or resources and need to discuss your team’s current priorities. It’s also a great tool to use during sprint planning or requirement gathering.