Minimum viable product (MVP): definition, examples and Agile method

Reworking software means taking over existing code to correct it and make it evolve.
We start by accessing the code, then carry out a free maintainability analysis.
Depending on the quality of the code, improvements are made using the same technology or part of the code (often the back-end) is overhauled.
Changing service providers allows you to unlock fixes when the current team is no longer available.
Updating a language or migrating a technology improves performance and security.

A minimum viable product (MVP) is an approach that involves launching a basic version a product for validate use and demand, with as few functions as possible.

On this page, you'll find out what an MVP is, see some concrete examples (Zappos, Airbnb, Uber, Instagram), then discover how to develop an MVP using Agile methodology, In short cycles, iterating on user feedback.

What is an MVP (Minimum Viable Product)?

MVP means “Minimum Viable Product”, or minimum viable product.
This term is widely used in product development (including software).

The idea is simple: an MVP is the simplest version of a new product, placed on the market for :

test demand
validate actual use
solve the main problem targeted
while keeping a minimum functional scope

“Minimal” does not mean “slapdash”. Even with few functionalities, the product must remain usable and add value.

Why the MVP is at the heart of Lean Startup

The MVP concept is presented as an essential aspect of the Lean Startup methodology, developed by Eric Ries.
This approach focuses on’experiment testing business assumptions rather than investing for a long time in a complete product with no proof of demand.

In practical terms, the MVP serves as “field proof”: you put a first version in the hands of users, then observe, measure and improve.

4 examples of MVPs (Zappos, Airbnb, Uber, Instagram)

Zappos

The Zappos MVP was a simple website listing shoes... from a local shop near the founder.
With each order, he would buy the pair to the shop, then delivered it. Objective: test demand before building a complete e-commerce platform.

Airbnb

Airbnb's MVP was a website with photos and information on housing.
The founders did the research and took the photos themselves. Here again : test demand before a complete platform.

Uber

Uber's MVP started out as a website to request a journey from a nearby driver.
Before full application, the idea was to validate the concept and gather user feedback.
The initial functions mentioned are: registration/log-in, journey request, driver connection, real-time tracking, payment, user feedback.

Instagram

Instagram's MVP was a simple application photo sharing with some basic filters.
Aim: test interest, get feedback, then add features.

Develop an MVP using Agile methodology (2 to 3 week sprints)

Developing an MVP using Agile is presented as one of the most popular methods, because it allows you to’iterate according to :

the user feedback
the latest market information

The principle: divide development into small cycles (of sprints of 2 to 3 weeks).

1) Define the product's vision and objectives

Step one: Clarify :

the problem that the product must solve
the target audience
the desired results

Without this basis, it becomes difficult to choose “the minimum” to build.

2) Define user stories

The user stories help the team to understand users' needs and how the product responds to their problem.

Clarification (general): a user story often formalises a user need in a short, actionable way.

3) Prioritising functionalities

The product team must prioritise functionalities:

according to their importance for the user
according to value provided

The aim is to separate :

functionalities essential to MVP
those that can be added later

The transcript also stresses a practical idea: select only a few user stories for development to start.

4) Planning the sprint

During the planning phase, the :

chooses the user stories it will work on
estimates the effort required

Objective: that’a sprint (or two) provides new functions that can be used by users.

5) Developing the MVP

The development team implements the selected user stories and builds the minimum viable product.

If you're in the MVP/POC business, here are two useful pages to help you get started:

6) Review and iteration (each sprint)

After each sprint, the :

revise the MVP
collects user feedback
uses this feedback to improve the product in the following sprints

7) Repeat the process

The cycle continues: sprints → prioritisation → improvement... until the product meets the needs of the target audience.

Advantages of an MVP

Here are the benefits cited:

Reducing risks and costs You test the idea with a minimum investment of time and resources, concentrating on the essentials.
Faster time to market This is a useful tool in a competitive environment, enabling you to gain a foothold earlier and start generating revenue.
Validation of hypotheses MVP: the MVP enables you to check your hypotheses about the product idea and confirm a real demand.

Faster iteration and improvement Feedback is used to improve the product and add features based on observed needs.

Disadvantages of an MVP and points to watch out for

The transcript lists several limitations:

Limited functionality At the outset, the product does not have everything that some users would like, which may limit its appeal.
Risk of negative user experience If the MVP is poorly designed (unintuitive UI, unstable product), users may give up.
- Important point: negative feedback can also be useful to improve.
Limited market appeal An MVP can target a very specific audience, which can make growth more difficult until the product evolves.
Difficulty attracting investors In the early stages, some investors are reluctant to invest if the concept has not yet been proven.
- But once you've got an audience via the MVP, you may be in a more favourable position (proof of concept, first paying users, market data, growth prospects).

Lighting (general): if you are hesitating between MVP and POC depending on your technical or market uncertainty, you may want to clarify your choice before investing: Proof of concept for a mvp

To remember

A MVP is a minimum version of a product, designed to validate demand and usage.
It focuses on main problem with limited functionality.
Well-known examples: Zappos, Airbnb, Uber, Instagram.
Visit Agile, we advance by sprints of 2 to 3 weeks, with prioritisation and iteration based on feedback.
Advantages: fewer risks/costs, speed to market, validation, rapid iteration.
Disadvantages: limitations, UX risk if poorly executed, limited initial market, more difficult for investors at the outset.

Next stage: from idea to MVP

If your objective is to create an MVP (or clarify what really needs to be built first), you can :

explore the MVP or POC
or see how to choose the the right partner to build an MVP

To find out more, click here:

Take a Meeting with an MVP or POC expert
Contact us via the contact form for MVP or POC projects

Tell us about your project

One exchange, a thousand possibilities.

Describe your vision to us using this form: we'll analyse your request and get back to you within 24 hours with personalised advice and a concrete action plan.

We have the team and the resources to help you with your projects. Give us the details in this form and we'll get back to you as soon as possible to discuss them together.

Name

Company

Telephone

Subject

Message

Attachment