The MoSCoW Method: Prioritizing for Fixed Deadlines
The MoSCoW method protects deadlines by sorting work into four buckets: Must Have, Should Have, Could Have, and Won't Have this time. It's used in agile projects with fixed timelines to ensure critical features ship.
The mental model
MoSCoW is a prioritization framework that treats time as fixed and scope as flexible. Instead of asking 'What is the highest priority?', it asks 'What is essential for this release to be a success?'. It forces teams and stakeholders to make hard choices, ensuring that a viable product is delivered on time by defining what can be deferred.
How it works
The acronym categorizes requirements into four distinct buckets. First, MUST HAVE requirements are non-negotiable; the system is not viable without them. Second, SHOULD HAVE requirements are important but not vital for the current delivery. The solution is still viable without them, but they may be painful to leave out. Third, COULD HAVE requirements are desirable but less important. These are 'nice-to-haves' that will be included only if time and resources permit. Finally, WON'T HAVE THIS TIME requirements are explicitly acknowledged as being out of scope for the current timebox, managing expectations and preventing scope creep for a future release.
When to use it
Use MoSCoW in any time-boxed project, like a sprint or a fixed-deadline release, where you need to guarantee delivery of a core set of features. It's more effective than simple 'high/medium/low' labels, which are often subjective, or a numbered list (1, 2, 3...), which can lead to arguments over minor rank changes. It provides a clear promise to the business about what to expect.
When not to use it
The framework is less effective when time is not the primary constraint. If a project has a completely fixed scope where every feature is genuinely a 'must have', or if deadlines are entirely flexible, MoSCoW loses its power to force the necessary trade-offs that protect a delivery date.
One canonical example
For a new user login feature in a two-week sprint: a MUST HAVE is login with email and password. A SHOULD HAVE is a 'Forgot Password' flow. A COULD HAVE is login via a social media provider. A WON'T HAVE THIS TIME is two-factor authentication.
Interview question
Which principle best describes the MoSCoW method's approach to project delivery?
- a.Adapting the project timeline to accommodate all identified requirements.
- b.Prioritizing all features equally to maintain stakeholder satisfaction.
- c.Focusing on delivering only the 'nice-to-have' features first to build momentum.
- d.Adjusting the scope of work to meet a predefined delivery schedule.Correct
Why? this is the answer
The MoSCoW method treats time as fixed and scope as flexible, meaning the scope is adjusted to ensure a viable product is delivered by a specific deadline. Option A is incorrect because MoSCoW is used when the timeline is fixed, not flexible.
Just read this? Test yourself on what you have been reading.
Read the original → agilebusiness.org
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles