Skip to main content
GullySystem

MVP Feature Development

MVP feature development builds one journey completely and records every other idea on a parked list. A user signs in, completes the task and receives the outcome.

Drawing the scope line

The scope is written in four groups and agreed in writing before work starts. Nothing is deleted, only parked.

In the first release

The single journey that tests the assumption you are least sure about, built properly from start to finish.

Parked for later

Every other idea, recorded with who asked for it and a date to revisit, so the same argument does not restart at every review meeting.

Done by hand

Matching, verification or approval that a person handles for early users while the rules are still being learned and before any of it is coded.

Explicitly out

Features that will not be built at all, stated in writing. Silence would otherwise be read as agreement.

What still has to be built properly

Minimum applies to the number of features and not to the quality of the ones included.

  • Login and permissions, since a leaked record in a pilot is still a leaked record
  • Payment collection, wherever willingness to pay is the question being tested
  • An operator console, so your own team can fix a stuck record without a developer
  • Event tracking at each step, so drop-off is measured and not guessed

What the first release may lack

Settings screens, bulk import, a second language and a report for every question can wait, and they are built once real usage shows which of them are needed. Some first versions also rely on one person doing a task manually each morning. That is a valid way to learn a rule before it is written into code.

How a build cycle runs

Work moves in short cycles so you see progress on a real phone, not in a status report.

Slice by outcome

Each slice delivers something a user can do end to end, such as register and see a confirmation. A slice that only builds the database table gives you nothing to try.

Show a working build early

A deployed version you can open lands within the first cycles. Early sight of a thin but working path catches misreadings of the brief while they are small.

Test each story against its note

Every story has a plain acceptance note written during scoping. The story is finished when that note is satisfied, and not when the code merely exists.

Keep a short list of known gaps

Rough edges that were accepted on purpose are written down with the reason. That list becomes the starting point for later hardening.

Choices that save rework later

A small product still needs sensible foundations. The data model should reflect how your business really names things, because renaming a core table after launch is slow and risky. Configuration lives outside the code. Third-party services such as payments or messaging sit behind one thin layer, so swapping a provider touches one place. None of this adds screens, and all of it lowers the cost of the next release.

How one feature gets built across a week

A single MVP feature moves from agreement to a working screen in a short cycle of build, check and show. The people involved are the founder, the developer and the first test user. This page follows that cycle. Nobody works alone.

Founder at the start

The founder confirms what the feature must do and what it will not do this time. The parked list gets the extra ideas. Both lists are saved, so later arguments have a reference. Scope stays visible to everyone.

Developer building midweek

The developer builds the feature’s main path and shows a working screen to the founder. Rough edges are fine. The founder replies with one change request, not five, and the developer records it. Feedback stays focused.

Test user on Thursday

A friendly user tries the feature on a phone and completes the task. Where they stall, the developer notes the exact step. Those notes decide what is fixed before the next demo. The test is short.

End of cycle review

Together, they look at what shipped and what slipped. A slipped item returns to the list with a reason. Nothing disappears, and the next cycle starts from facts. Every slip gets a clear written reason today.

Questions the founder answers before building starts

Before a feature is built, a few questions need a clear answer from the owner of the idea. They are about people and rules, not code. Writing them down saves arguments in the middle of a build. Answer them early.

Who may use it first

Decide who gets the first release, such as ten invited customers. Opening it to everyone means every rough edge becomes a public problem. A small group forgives more and talks more. Invite people who will reply.

What data it stores

List what the feature records about each user and why. Anything not needed should be left out. Less stored data means less to protect and less to explain to the first customers. Collect nothing without a use.

How early users join

If a spreadsheet or a messaging group already holds the first users, decide how they enter the product. Typing in twenty names by hand is acceptable at this size. Small numbers allow hand work. Keep a list of who joined.

What counts as done

Agree one test the feature must pass, such as a stranger completing the task unaided. That test ends the feature. Without it, the build stretches while ideas keep arriving. Write the test on the board for everyone.

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.

Drawing the scope line

Which observation would change the proposed scope?

For “Drawing the scope line”, 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

What still has to be built properly

Can an ordinary account reach a record outside its allowed scope?

For “What still has to be built properly”, agree two accounts with different permissions and test direct requests. Record the expected refusal and include exported or downloaded data in the assessment.

Background reading: OWASP: authorisation checks

FAQ

Frequently asked questions

How do we decide which features make the first release?

Start from the assumption that would do the most damage if it were wrong. Whatever tests that assumption goes in, and the rest waits. The scope is agreed with you during the first review.

Does MVP feature development produce throwaway code?

No. The database, code and hosting carry into the full product, and the source code, hosting and data stay in your name throughout. What is cut is scope, not quality.

What if the pilot shows the idea does not work?

Then the first version has done its job. Stopping before the full budget is committed is a valid outcome, and it is the reason for building small before building everything.

Can we add a feature in the middle of the build?

Yes, if something comes off the list to make room. Adding without removing stretches the date and blurs the test. The trade is written down so everyone sees what moved.

Do we need a mobile app or is a web app enough?

A mobile-friendly web app can serve a first release, because it needs no store approval and updates instantly. A native app makes sense when the core journey depends on the camera, offline use or push alerts.

Who owns the code once it is built?

You do. The repository, the hosting account and the data are set up in your name from the start, so you can hand the product to another team at any point.

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