Introduction
Throughout my project and program management career, I have worked with various methodologies, each offering valuable frameworks for decision-making, execution, and governance. Having obtained certifications in PMI’s PMBOK, Agile methodologies, and other recognized frameworks, I appreciate the strengths and applications of each. However, one method that has stood out for its universal applicability is MoSCoW prioritization, which I mastered during my AgilePM certification.
MoSCoW is not just for Agile teams managing product backlogs; it is a robust prioritization framework that can be applied across waterfall, hybrid, and strategic portfolio management approaches. Whether used to determine key project deliverables, allocate resources, or prioritize projects at the Program Management Office (PMO) or Steering Committee (SteerCo) level, MoSCoW provides a structured way to ensure that effort is focused where it brings the highest value.
This article explores how MoSCoW can be used effectively in project management, providing a recommended percentage split for effort allocation, guidance on facilitating MoSCoW workshops, and real-world-inspired case studies for prioritizing projects at an organizational level.
What is MoSCoW Prioritization?
MoSCoW is a simple yet powerful prioritization technique used to categorize deliverables, requirements, or projects into four distinct levels of importance:
- Must Have (60%) – Critical to project success; without these, the project fails or is fundamentally compromised.
- Should Have (20%) – Highly desirable but not essential for immediate success; can be deferred if necessary.
- Could Have (20%) – Nice-to-have items that enhance the outcome but do not impact the core objectives.
- Won’t Have (this time) – Items agreed to be out of scope for the current phase but may be revisited later.
This 60-20-20 split is recommended in AgilePM as a best practice for ensuring that Must Have items are delivered while allowing flexibility for other priorities. However, the exact split can be adjusted based on strategic needs in a portfolio or program management context.
Prioritizing Project Scope and Deliverables
Project managers and teams can use MoSCoW to identify critical features or workstreams that can be adjusted or postponed. By aligning stakeholders on what is non-negotiable, teams can ensure on-time, on-budget delivery while maintaining agility to adapt to changes.
Allocating Resources Efficiently
MoSCoW helps teams focus effort where it matters most. Instead of spreading resources thin across all areas, the method directs attention to high-value work, ensuring key deliverables are completed first.
Managing Risk and Scope Creep
By clearly defining what is and isn’t in scope (Must vs. Won’t Have), MoSCoW prevents scope creep—one of the biggest challenges in project execution. It allows proactive risk management, ensuring critical elements are not sacrificed due to distractions.
Engaging Stakeholders and Setting Expectations
MoSCoW fosters alignment between business leaders, PMOs, and delivery teams. It provides a transparent and collaborative framework for decision-making, ensuring that all stakeholders have a shared understanding of project priorities.
How To: Facilitating MoSCoW Prioritization
Structured facilitation is key to applying MoSCoW effectively. Here’s a recommended approach for conducting a MoSCoW prioritization workshop:
Defining the Scope of Prioritization
- Are you prioritizing project deliverables or entire projects?
- What constraints exist (budget, time, regulatory requirements)?
Gathering the Right Stakeholders
- Include executive sponsors, product owners, and PMO representatives.
- Ensure alignment on the business objectives before starting.
Using a Collaborative Whiteboarding Approach
- Digital tools (Miro, MURAL, Microsoft Whiteboard) for virtual teams.
- Physical boards and sticky notes for in-person workshops.
Establishing the MoSCoW Categories
- Ask participants to list all items/projects and categorize them collaboratively.
- Challenge every “Must Have” to ensure it is truly non-negotiable.
Assigning Percentage Weighting
- Ensure Must Have items do not exceed 60% of the available effort or budget.
- Balance Should and Could Haves to allow flexibility in execution.
Finalizing, Documenting, and Communicating the Outcome
- Create a clear record of agreed priorities.
- Share results with all stakeholders to set expectations and ensure accountability.
Case Study 1: MoSCoW at the Program Management Office (PMO)
Scenario: A pharmaceutical company’s PMO is planning its project portfolio for the upcoming year. Ten significant projects are proposed, but only five can be funded due to budget constraints.
Step 1: Categorizing Projects Using MoSCoW
| Project Name | MoSCoW Category | Effort Allocation (%) | Justification |
| Regulatory Compliance System Upgrade | Must Have | 30% | Required by law; non-compliance leads to penalties. |
| New Product Development (Cancer Drug) | Must Have | 30% | Strategic priority; high market potential. |
| ERP System Modernization | Should Have | 15% | Improves efficiency, but the legacy system is still functional. |
| Digital Sales Transformation | Should Have | 5% | Expands digital channels but is not mission-critical. |
| AI-Based Drug Discovery | Could Have | 10% | High potential but uncertain ROI. |
| Supply Chain Optimization | Could Have | 10% | Improves logistics but not an urgent need. |
| Employee Training Platform | Won’t Have | 0% | Can be postponed to next year. |
Step 2: Decision and Execution Plan
The PMO approves the Must Have projects, retains some Should Have efforts, and allocates limited resources to Could Have initiatives.
Case Study 2: ERP Implementation and Requirements Prioritization
Scenario: A global manufacturing company is implementing a new ERP system. Fit/Gap analysis has identified several required customizations. Still, the IT budget limits how many can be developed in the first phase.
Step 1: Categorizing ERP Customization Requests
| Requirement | MoSCoW Category | Effort Allocation (%) | Justification |
| Integration with financial reporting | Must Have | 35% | Required for compliance and financial audits. |
| Automated inventory tracking | Must Have | 25% | Essential for supply chain visibility. |
| Custom approval workflows | Should Have | 10% | Improves process efficiency but can be handled manually initially. |
| Local language customization | Should Have | 5% | Helps adoption in multiple regions, but the standard English version works. |
| Supplier portal customization | Could Have | 10% | Enhances vendor collaboration but can be delayed. |
| AI-driven demand forecasting | Could Have | 10% | Adds predictive capabilities but not immediately necessary. |
| Legacy system data migration automation | Won’t Have | 0% | Too costly; manual migration planned instead. |
Step 2: Decision and Execution Plan
The IT team and business stakeholders agree on developing all Must Have features first, with Should Have and Could Have elements phased into later updates based on funding availability.
Conclusion
MoSCoW is an adaptable prioritization framework that extends far beyond Agile software development. Whether applied to project scope, strategic planning, or portfolio management, it helps teams focus on what truly matters, ensuring resources are allocated efficiently and effectively.
Mastering and applying MoSCoW in various contexts, PMOs, Steering Committees, and project managers can drive better decision-making, enhance stakeholder alignment, and deliver impactful results. Regardless of your project management methodology—Agile, Waterfall, or Hybrid—MoSCoW remains a powerful tool for managing priorities in a structured yet flexible way.