MoSCoW Prioritization
MoSCoW is a prioritization technique that categorizes requirements into four groups: Must have, Should have, Could have, and Won't have (this time), helping teams focus on delivering the most critical items first.
Know it well enough for the exam? Questions on MoSCoW Prioritization are scenario-based, not definitional.
Practice it freeExplanation
MoSCoW prioritization helps teams and stakeholders reach consensus on which requirements are essential versus optional. Must-have items are non-negotiable requirements without which the product will not function or the project will be considered a failure. Should-have items are important but not critical, and the product can work without them temporarily. Could-have items are desirable enhancements that are included only if time and resources permit. Won't-have items are explicitly excluded from the current scope but may be considered in the future.
The technique is especially useful during release planning and Sprint Planning when the team needs to determine which items to include within a fixed timebox or budget. It creates clear expectations among stakeholders about what will and will not be delivered.
MoSCoW originated from the Dynamic Systems Development Method (DSDM) but is widely used across agile approaches. It provides a simpler categorization than numerical priority rankings and helps teams avoid the trap of treating everything as high priority.
Key Points
- •Must have: critical, non-negotiable requirements
- •Should have: important but not critical; delivery can be delayed if needed
- •Could have: desirable enhancements included only if time allows
- •Won't have: explicitly excluded from current scope
Exam Tip
MoSCoW is useful when stakeholders struggle to differentiate priorities. The key insight is that Won't Have does not mean never; it means not this time.
Frequently Asked Questions
Related Topics
Product Backlog
The product backlog is an ordered list of everything that is known to be needed in the product, serving as the single source of requirements and the primary artifact for managing scope in agile projects.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Release Planning
Release Planning is an agile practice where the team and Product Owner determine the scope, timing, and goals for the next product release by mapping backlog items across future iterations based on team velocity.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Part of
Agile & Hybrid
Practice MoSCoW Prioritization
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.