Minimum viable product
In product development, the minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future development. Some experts suggest that in B2b an MVP also means saleable: "it’s not an MVP until you sell it. Viable means you can sell it".
Gathering insights from an MVP is often less expensive than developing a product with more features, which increase costs and risk if the product fails, for example, due to incorrect assumptions. The term was coined and defined by Frank Robinson about 2001, and popularized by Steve Blank, and Eric Ries. It may also involve carrying out market analysis beforehand.
A minimum viable product has just those core features sufficient to deploy the product, and no more. Developers typically deploy the product to a subset of possible customers—such as early adopters thought to be more forgiving, more likely to give feedback, and able to grasp a product vision from an early prototype or marketing information. This strategy targets avoiding building products that customers do not want and seeks to maximize information about the customer per dollar spent. "The minimum viable product is that version of a new product a team uses to collect the maximum amount of validated learning about customers with the least effort." The definition's use of the words maximum and minimum means it is decidedly not formulaic. It requires judgement to figure out, for any given context, what MVP makes sense.
An MVP can be part of a strategy and process directed toward making and selling a product to customers. It is a core artifact in an iterative process of idea generation, prototyping, presentation, data collection, analysis and learning. One seeks to minimize the total time spent on an iteration. The process is iterated until a desirable product/market fit is obtained, or until the product is deemed non-viable.
- Be able to test a product hypothesis with minimal resources
- Accelerate learning
- Reduce wasted engineering hours
- Get the product to early customers as soon as possible
- Base for other products
- To establish a builder's abilities in crafting the product required
- Results from a minimum viable product test aim to indicate if the product should be built to begin with. Testing evaluates if the initial problem or goal is solved in a manner that makes it reasonable to move forward.
- Steve Blank: "You’re selling the vision and delivering the minimum feature set to visionaries, not everyone."
|This section needs additional citations for verification. (February 2017) (Learn how and when to remove this template message)|
Releasing and assessing the impact of a minimum viable product is a market testing strategy that is used to screen product ideas soon after their generation. It is facilitated by rapid application development tools and languages common to web application development.
The MVP differs from the conventional market testing strategy of investing time and money early to implement a product before testing it in the market. The MVP is intended to ensure that the market wants the product before a large time and monetary investment is made. The MVP differs from the open source methodology of release early, release often that listens to users, letting them define the features and future of the product. The MVP starts with a product vision, which is maintained throughout the product life cycle, although it is adapted based on the explicit and implicit (indirect measures) feedback from potential future customers of the product.
The MVP is a strategy that may be used as a part of Blank's customer development methodology that focuses on continual product iteration and refinement based on customer feedback. Additionally, the presentation of non-existing products and features may be refined using web-based statistical hypothesis testing, such as A/B testing.
The general method of deploy first, code later is akin to the agile program code testing methodology called test-driven development where unit tests are written before and fail until the code is written.
Business Model CanvasEdit
The Business Model Canvas is used to map in the major components and activities for a company starting out. The minimum viable product can be designed by using selected components of the Business Model Canvas:
- Value Proposition
Concepts from minimum viable product are applied in other aspects of startups and organizations.
Minimum viable technology (MVT)Edit
|This section does not cite any sources. (March 2017) (Learn how and when to remove this template message)|
Minimum viable co-founderEdit
Finding other people to create a minimum viable product is a common challenge for new companies and startups. The concept of minimum viable co-founder is based on looking for a co-founder with the following attributes:
- Exceptional at building or selling
- Company commitment
- Personally likeable
Minimum viable teamEdit
Founders with an early-stage company are faced with the challenge of building a team with minimal people and cost. The process starts by listing out basic functions of a particular company (e.g., engineer, operations, finance) and then stripping down to the abstract job activities and skills that the company must have to operate.
- Ries, Eric (August 3, 2009). "Minimum Viable Product: a guide".
- "Top Software Developers Who Became Rich Thanks to MVP (PHOTO)". April 17, 2017.
- "SyncDev methodology". SyncDev. Retrieved May 16, 2016.
- W. S. Junk, "The Dynamic Balance Between Cost, Schedule, Features, and Quality in Software Development Projects", Computer Science Dept., University of Idaho, SEPM-001, April 2000.
- Eric Ries, March 23, 2009, Venture Hacks interview: "What is the minimum viable product?", Lessons Learned
- Perfection By Subtraction – The Minimum Feature Set
- Holiday, Ryan The single worst marketing decision you can make The Next Web. 1 April 2015
- Radoff, Jon (May 4, 2010). "Minimum Viable Product rant". http://web.archive.org/web/20140323181121/http://radoff.com/blog/2010/05/04/minimum-viable-product-rant/. Jon Radoff's Internet Wonderland. Archived from the original on March 23, 2014. Retrieved 19 August 2014. External link in
- Blank, Steve (March 4, 2010). "Perfection By Subtraction – The Minimum Feature Set".
- Lenarduzzi, Valentina; Taibi, Davide (August 2016). MVP Explained: A Systematic Mapping Study on the Definitions of Minimal Viable Product. 2016 42th Euromicro Conference on Software Engineering and Advanced Applications (SEAA). Cyprus. pp. 112–119. doi:10.1109/SEAA.2016.56. dsd-seaa2016.cs.ucy.ac.cy
- Kromer, Tristan (April 15, 2014). "The Four Parts of a Minimal Viable Product".
- Shah, Darmesh (October 5, 2011). "Choosing A Minimally Viable Co-Founder".
- Kromer, Tristan (October 11, 2011). "A Minimum Viable Team is More Important than a Minimum Viable Product".
- O'Donnell, Charlie (August 22, 2012). "Minimum Viable Team".