MoSCoW, Timeboxing & Practices
33 practice questions with explanations — 15 free to try
3 of these 33 questions are in the free 15-question taster · the full topic is part of Premium
PassNova has 33 AgilePM Foundation practice questions on MoSCoW, Timeboxing & Practices, each with a clear explanation. A 15-question taster is free with no sign-up; the full bank is part of PassNova Premium. Updated for 2026.
MoSCoW, Timeboxing & Practices: example questions & answers
3 worked examples with answers and explanations below. Try 15 AgilePM Foundation questions free in the browser; the full 33-question MoSCoW, Timeboxing & Practices bank is part of PassNova Premium.
What does AgilePM recommend about the proportion of effort allocated to Must Have requirements within a Sprint, so that contingency is provided?
- AMust Haves should be exactly 25% of the effort
- BThe balance of Must Haves is left entirely to the team
- CMust Haves should be no more than 60% of the effort✓
- DMust Haves should always be 100% of the effort
Answer: AgilePM guidance recommends Must Haves at no more than about 60% of effort, with around 20% Should Have and 20% Could Have, so the Could Haves provide a contingency that protects on-time delivery.
Which MoSCoW category is most likely to be sacrificed first if a Sprint comes under time pressure?
- AWon't Have this time
- BMust Have
- CShould Have
- DCould Have✓
Answer: Could Have requirements are desirable but not vital, so they act as the built-in contingency and are the first to be dropped to protect on-time delivery of the Must Haves.
In AgilePM timeboxing, what is meant by the deadline of a Sprint being fixed?
- AThe end date can be extended by the Project Manager if the highest-priority requirements are late
- BThe end date is immovable, so scope is flexed via MoSCoW rather than moving the deadline✓
- CThe Sprint has no defined end date and simply runs on until the planned work has been completed
- DThe Could Have requirements have a fixed deadline within the Sprint, while the rest may slip
Answer: A core idea of timeboxing is that the deadline is fixed and protected; if work is at risk, lower-priority requirements are dropped rather than extending the Sprint.