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
Related methods and what they add
Nothing here is exotic, and you can use the vocabulary with any team.
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.
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
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.
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
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- 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