Skip to main content
GullySystem

MVP Scoping and the First Release Backlog

MVP scoping turns an idea into a short list of what the first release must do, what waits and what is never built. The backlog holds the rest.

Three piles for every idea

Sort every idea into three piles. Must have means the customer cannot finish the core journey without it, and later means wanted but not missed by the first users. Never means it belongs elsewhere. That third pile is the hardest for founders to fill, yet it removes the most effort, because every item in it is a screen nobody has to build.

What the backlog holds

User stories

Each story is small. It names one person, one action and one outcome, such as a receptionist booking a slot for a patient who phoned at lunch. Two actions mean two stories.

Acceptance notes

Every story carries a check. It is a plain note saying how you will know the thing works, written so you can try it yourself on a phone without a developer beside you.

Effort as a range

Small, medium and large beat one number. A wide band marks a story nobody understands yet, so it gets a conversation first, and only then a place in the release plan.

Release order

Order follows the buyer’s path. Stories are sequenced along the first user journey, with dependencies marked, so payment is never planned ahead of the sign-up it relies on.

Related methods and what they add

Nothing here is exotic, and you can use the vocabulary with any team.

Must, should, could, won’t

This four-way sort is known as MoSCoW. The won’t group holds requests that are acknowledged but not built in this round. Naming that group stops those requests from drifting back in.

A cap on the must pile

If almost everything is a must, nothing has been decided. Some buffer is kept so one surprise does not break the date.

Stories that pass a quick test

Good stories are independent enough to build alone, small enough to finish in a few days and testable with a clear pass or fail. Stories failing that test are split or rewritten.

Given, when, then notes

Acceptance notes can follow a given, when, then pattern: given a registered customer, when they pay, then they see a receipt. The shape keeps notes short and checkable.

What founders over-build

Admin dashboards come first. Then roles and permissions, a second language and a referral scheme arrive, and none of it helps you learn whether anyone wants the product. A spreadsheet stands in for the back office. Scoping has limits too. It cuts guesswork but cannot prove demand, and a careful tidy backlog for a product nobody wants is still a wasted build.

What to bring to an MVP scoping session

  • A one-line statement of who the product is for and what pain it removes
  • Any competitor or workaround your customers use today
  • Screenshots, forms or spreadsheets from the current manual process
  • A rough budget and the date you would like real users to start
  • The single assumption that worries you most

A scoping session and the weeks after it

Scoping happens in a room and then lives on as a list. A founder, a developer and sometimes an early customer decide what goes first. This page shows how that session sets up the weeks that follow. Scope is settled here.

Founder opens with the idea

The founder explains the problem in one paragraph and names the person who suffers from it. That person’s task sets the first journey. Everything else is held on a separate list for later. One paragraph is enough.

Developer asks what is missing

The developer asks what happens when a step fails or a user forgets a password. Those answers add unglamorous items to the list. Without them, the first release looks complete and breaks on day one.

Customer reads the short list

An early customer is asked to read the first-release list. They cross out what they would not miss and circle what they would. The final list is shorter than the founder expected. Their view corrects the founder.

Weekly backlog check

Each week the founder moves one item up or down and records why. Honesty keeps this list useful for everyone. The developer picks the top item, and the founder resists adding new ones without removing one.

Make an informed decision

Agree the evidence before signing off this part.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

Three piles for every idea

Which observation would change the proposed scope?

For “Three piles for every idea”, observe someone completing the task with a representative example. Record where they stop, ask another person or re-enter information, then choose the smallest change whose result the team can verify.

Background reading: GOV.UK: researching user needs

FAQ

Frequently asked questions

How many features should a first release have?

Only as many as let one customer finish one journey and pay or commit, which is fewer than the founder first writes down on paper. Cut again before building starts.

Why are estimates shown as ranges?

Early estimates are guesses about unknowns, and a single figure hides that fact from the person approving the budget and planning the launch date. A range shows where the doubt sits. Ranges narrow by building, not by negotiating.

Can the scope change after building starts?

Yes, and it should change whenever real users teach you something the plan could not have known at the start of the project. Each addition replaces something. The trade stays visible.

Who decides what is in the first release?

You decide, as the owner of the idea, with advice from the team on cost and risk, because developers rarely know your customer as well as you do. Owners rarely know what is costly.

What is the difference between a backlog and a roadmap?

A backlog is the detailed list of stories waiting to be built. A roadmap is the broader picture of what comes in which release. The backlog changes weekly, while the roadmap changes when your plan does.

How long does scoping take?

A few working sessions, depending on how clear the idea is and how many people must agree. A founder with one clear journey finishes sooner than a group with five competing priorities.

Do we need user stories if the team is small?

A short written story still helps, because it forces one person, one action and one outcome. It also gives you something to test against, which a verbal request does not.

Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements