II.
Methodology overview
Reference · livemethodology:MoSCoW-prioritization
MoSCoW Prioritization overview
A prioritization technique that classifies requirements into four categories: Must have (non-negotiable for the release), Should have (important but not critical), Could have (desirable if time permits), and Won't have (explicitly out of scope this time). Used within timeboxed iterations to manage scope and set clear stakeholder expectations about delivery guarantees.
Attributes
displayName
MoSCoW Prioritization
description
A prioritization technique that classifies requirements into four categories:
Must have (non-negotiable for the release), Should have (important but not
critical), Could have (desirable if time permits), and Won't have (explicitly
out of scope this time). Used within timeboxed iterations to manage scope
and set clear stakeholder expectations about delivery guarantees.
methodologyKind
prioritization
origin
Dai Clegg
yearIntroduced
1994
Outgoing edges
applies_to2
- domain:project-management·DomainProject Management
- domain:software-engineering·DomainSoftware Engineering
Incoming edges
None.