Scoping the MVP · 5 minute read

How to scope an MVP with MoSCoW

Scope is the list of what your MVP will do. It is where most budgets are won or lost. Every extra feature adds design, building, testing and support, and many of them do nothing to show whether the core idea works.

MoSCoW is a simple way to decide. It is part of DSDM, an agile framework set out by the Agile Business Consortium, and it sorts every feature into one of four groups: Must have, Should have, Could have, or Won’t have this time.

Start with a long list

Write down every feature you have thought of, including the ones you are sure about. Write each one as a short user story, so you know who it is for and why: as a… I want to… so that…

Large stories are a problem for prioritising. The GOV.UK Service Manual calls stories that would take more than a few weeks to build and test “epics”, and suggests splitting them into smaller stories. Splitting “manage bookings” into booking, cancelling and rescheduling lets you decide on each part separately.

Sort features with MoSCoW

The Agile Business Consortium defines the four groups like this:

  • Must have: the minimum usable subset. Without it there is no point launching, the product would not be legal or safe, or it would not work. A useful test: if this were missing, would you cancel the launch?
  • Should have: important but not vital. Painful to leave out, but the product still works, perhaps with a workaround.
  • Could have: wanted, but with less impact if left out. These are the first things to drop when time or money runs short.
  • Won’t have this time: agreed as out of scope for this version. Writing them down stops them creeping back in later.

Be strict about Must haves

The usual trap is marking everything as a Must have. The Consortium’s test helps: if there is any way round a missing feature, even a manual and painful one, it is not a Must have. For an MVP, the founder doing something by hand for the first 50 users is often a perfectly good workaround.

DSDM recommends that Must haves take no more than about 60% of the total effort, with around 20% of the effort in Could haves as contingency. The point is to keep part of the plan flexible, so the important features still arrive on time if estimates turn out to be wrong.

For an MVP, add one more question for every Must have: does this help test our riskiest assumption? If not, it is probably a Should have or something for later. The exception is anything needed to make the product legal or safe, including protecting personal data. Those stay as Must haves.

Features that can usually wait

These often appear on first lists but can usually be done by hand, with an off-the-shelf tool or not at all until the core idea is proven:

  • A custom admin dashboard: a spreadsheet or the database tool’s own screens often do at first.
  • Native iPhone and Android apps: a web app that works well on phones is one build, with no app store review.
  • Social login, detailed profiles, avatars and notification settings.
  • In-app chat: email or an existing messaging app works for early users.
  • Detailed reports and analytics: start with the few numbers that show whether the MVP is working.
  • Automated billing for every case: invoice the first customers by hand or use a payment provider’s hosted checkout.

Turn the scope into a budget

Once the features are sorted, ask developers to estimate the Must haves and Should haves separately. If the Must haves alone are over budget, the answer is fewer or simpler Must haves, not a cheaper developer.

Keep the Won’t have list in your brief. It tells suppliers exactly what they are not pricing, which makes quotes easier to compare.

The free feature prioritiser on this site helps you sort a long list, and the scope step of the MVP builder records each feature with its priority and user story.

Before you finish

  • Every feature is on the list, written as a user story.
  • Large stories are split into smaller ones.
  • Each feature has one priority: Must, Should, Could or Won’t.
  • Every Must have passes the “would we cancel the launch without it?” test.
  • Must haves are no more than about 60% of the estimated effort.
  • Legal, safety and data protection needs are treated as Must haves.
  • The Won’t have list is written down and shared with suppliers.

Common questions

How many Must haves should an MVP have?

There is no fixed number. Judge by effort rather than count: DSDM suggests Must haves should be no more than about 60% of the total effort. For many MVPs that means a handful of core features.

What is the difference between a Should have and a Could have?

Neither is guaranteed. A Should have is painful to leave out; a Could have has less impact. The Agile Business Consortium suggests agreeing at the start how you will tell them apart, for example by how many users are affected.

Can priorities change during the build?

Yes. Review them at the end of each stage of work. If a new feature comes in as a Must have, something else should move down, so the budget and the date still hold.

Is MoSCoW the only way to prioritise?

No. Other methods score each feature for value and effort. MoSCoW suits an MVP because it is simple and makes you name what you are leaving out.

Scope your MVP with the builder

Guided sections, features ranked, your budget and runway worked out, and a brief a developer can price. Free, no sign-up.

Start your brief

Sources

Checked on 15 November 2026. Prices, rates and rules change: follow the links for the latest figures. This page is general information, not professional, financial, legal or tax advice.