
nuAgility Glossary
What is a Minimum Viable Product (MVP)?
A Minimum Viable Product (MVP) is a version of an offering designed to test important assumptions and support validated learning with limited effort. Its purpose is to help a team decide what to do next based on evidence from customers and users.
Why it matters
It helps teams learn whether an idea deserves further investment before building a larger solution.
How it works
Begin with an important assumption: who has the problem, whether the proposed solution helps, or whether the offering can support a viable business. Decide what evidence would support changing or continuing the idea.
Choose the smallest responsible way to test that assumption. Depending on the question, this might involve a limited service, a manually delivered experience, or a small working product. Define measures that reflect customer behavior and useful learning.
Use the results to revise the idea, run another experiment, or invest further. Keep essential quality, privacy, and other obligations appropriate to the situation.
Example
Consider a team exploring whether small businesses would pay for a weekly report that helps them make staffing decisions. Before building an automated platform, it manually prepares reports for a few willing customers using approved data. The team asks customers to use the reports in real decisions and tests willingness to pay for continued service. It learns that customers value timely exception alerts more than lengthy summaries, so it changes the offering. The MVP limits effort while testing an important business assumption. Its success depends on useful evidence, not simply on launching an unfinished version of the eventual product.
Common misunderstanding
An MVP is often treated as a small, unfinished version of the intended product. Teams remove features, release it, and collect opinions without deciding what assumption they are testing. They may learn little while exposing users to avoidable problems or investing in an idea that remains unproven.
Start with the uncertainty and the next decision. What behavior or other evidence would justify continuing, changing, or stopping? Build only what is needed to obtain credible learning, while meeting the responsibilities appropriate to the people and situation involved.
Further reading
Related terms
Minimum Marketable Feature (MMF) · Mock Prototype · Outcome-Based Planning
Explore questions like this with other practitioners through the Agile Community Network, nuAgility's free live community event and podcast.
