MoSCoW Prioritization is a key technique in PRINCE2 Agile used to prioritize requirements, particularly when time and resources are fixed. The acronym stands for four categories: Must have, Should have, Could have, and Won't have (this time). 'Must have' requirements are non-negotiable and critical…MoSCoW Prioritization is a key technique in PRINCE2 Agile used to prioritize requirements, particularly when time and resources are fixed. The acronym stands for four categories: Must have, Should have, Could have, and Won't have (this time). 'Must have' requirements are non-negotiable and critical for delivery; without them, the solution is unviable, has no legal compliance, or cannot function. In PRINCE2 Agile, the guideline suggests that Must haves should account for no more than around 60% of the effort to maintain flexibility. 'Should have' requirements are important but not vital; their absence causes inconvenience but the solution still works, often via a workaround. These typically make up around 20% of effort. 'Could have' requirements are desirable but less important, providing 'nice-to-have' features that enhance value if time permits; these form the contingency (around 20%) that can be flexed when under pressure. 'Won't have this time' requirements are agreed to be excluded from the current delivery, though they may be revisited in future timeboxes or releases, helping manage stakeholder expectations. MoSCoW enables 'protecting the level of quality' and 'fixing time and cost' by flexing what is delivered, supporting the PRINCE2 Agile focus on delivering on time. Ordering, by contrast, is about the sequence in which items are delivered, not their importance. It arranges work based on factors such as dependencies, risk reduction, value delivery, or logical build order. A backlog can be ordered to deliver the highest value or riskiest items first. Together, MoSCoW and Ordering complement each other: prioritization determines what is essential versus optional, while ordering determines the delivery sequence. Both techniques support effective backlog management, collaboration with stakeholders, and the agile behaviours of transparency and flexibility, ensuring teams deliver the most valuable outcomes within fixed constraints of time, cost, and quality.
MoSCoW Prioritization and Ordering in PRINCE2 Agile
Introduction MoSCoW Prioritization is one of the most important prioritization techniques used within PRINCE2 Agile. It provides a structured, transparent way to decide what must be delivered and what can be dropped or deferred when time and resources are constrained. In an agile environment where time and cost are typically fixed, prioritization becomes the primary way to protect delivery while flexing scope.
Why MoSCoW Prioritization Is Important In PRINCE2 Agile, one of the key ideas is to fix time and cost, but flex what is being delivered (the scope and quality of features). To be able to flex scope effectively, you need to know which requirements are essential and which are optional. MoSCoW gives everyone (customers, users, delivery teams) a shared understanding of priority. This protects deadlines, supports the concept of delivering on time, and prevents low-value work from crowding out essential work.
Key benefits include: - Ensures the most valuable and essential features are delivered first. - Enables the flexing of scope without compromising deadlines or budget. - Creates a common language between business and technical stakeholders. - Supports timeboxing by making it clear what can be dropped if time runs short.
What MoSCoW Is MoSCoW is an acronym representing four priority categories. The 'o's are added simply to make the word pronounceable.
M – Must Have: Requirements that are fundamental and non-negotiable. Without these, the solution is unworkable, unsafe, or not legally compliant. If even one Must Have is not delivered, the delivery is considered a failure. (Sometimes described as the Minimum Usable SubseT.)
S – Should Have: Important requirements that are painful to leave out but for which a workaround may exist. The solution is still viable without them, but they add significant value.
C – Could Have: Desirable requirements that add value if included but have a smaller impact if left out. These are the first things dropped when time is short.
W – Won't Have (this time): Requirements that have been agreed as out of scope for the current timeframe. They may be revisited later. This category is valuable because it explicitly records what will NOT be done, avoiding scope creep.
How MoSCoW Works in Practice MoSCoW is applied to requirements, features, or user stories. A crucial guideline in PRINCE2 Agile (drawn from DSDM) concerns the balance of effort: no more than around 60% of effort should be Must Haves, with roughly 20% Should Haves and 20% Could Haves. This ensures there is enough contingency (the Should and Could Haves) to flex if delivery becomes difficult.
If Must Haves make up too high a proportion, there is little room to flex, and the risk of missing the deadline increases significantly.
Ordering Prioritization decides whether something is done and its relative importance. Ordering decides the sequence in which items are worked on. A high-priority item is not always done first – ordering may be influenced by technical dependencies, risk reduction, the desire to deliver value early, or the need to learn quickly. So MoSCoW tells you importance, while ordering tells you the delivery sequence, and the two are related but distinct.
Applying MoSCoW to Levels of Planning MoSCoW can be applied at different levels – across a whole project, within a release, or within a single timebox/sprint. Within a timebox, the Should and Could Haves act as the natural contingency that can be sacrificed to guarantee that the Must Haves are delivered on time.
How to Answer Exam Questions on MoSCoW Exam questions typically test your understanding of the definitions, the recommended balance of effort, and the difference between prioritization and ordering. Read the scenario carefully to identify which requirements are genuinely essential versus merely desirable.
Common question types include: - Matching a requirement to the correct MoSCoW category. - Identifying the recommended percentage split of effort. - Recognising the difference between prioritization (importance) and ordering (sequence). - Understanding why 'Won't Have this time' is a useful category.
Exam Tips: Answering Questions on MoSCoW Prioritization and Ordering
1. Remember what each letter stands for: Must Have, Should Have, Could Have, Won't Have (this time). Note the phrase 'this time' – it signals the item may be reconsidered later.
2. Learn the guideline effort split: aim for no more than 60% Must Haves, and around 20% Should and 20% Could Haves. Watch for questions where too many Must Haves reduce flexibility.
3. A Must Have is defined by the phrase: if it is not delivered, the solution is unworkable and the delivery has failed. Use this test to classify items in scenario questions.
4. Distinguish clearly between prioritization (relative importance) and ordering (delivery sequence). Do not assume the highest priority item is always built first – dependencies and risk can change the order.
5. Link MoSCoW to the core PRINCE2 Agile idea of fixing time/cost and flexing scope. Should and Could Haves provide the contingency to protect deadlines.
6. Beware of distractor answers that add fake categories or misremember the percentages.
7. In scenario questions, identify legal, safety, or minimum-viable requirements as Must Haves, and 'nice to have' extras as Could Haves.
Summary MoSCoW Prioritization gives PRINCE2 Agile teams a simple, shared way to agree what is essential and what can be flexed, while ordering determines the sequence of delivery. Mastering the definitions, the 60/20/20 effort guideline, and the distinction between priority and sequence will help you answer exam questions confidently and correctly.
