Difference between revisions of "Minimum viable product"
| Line 1: | Line 1: | ||
A [[minimum viable product]] (alternatively known as an [[introductory product]] or, often, by its acronym, [[MVP]]) is a version of a [[work product]] that includes sufficient features to satisfy early adopters and allows a team to collect the maximum amount of [[validated learning]] about customers with the least effort. | A [[minimum viable product]] (alternatively known as an [[introductory product]] or, often, by its acronym, [[MVP]]) is a version of a [[work product]] that includes sufficient features to satisfy early adopters and allows a team to collect the maximum amount of [[validated learning]] about customers with the least effort. | ||
| + | |||
| + | |||
| + | ==Definitions== | ||
| + | According to the [[ITIL Foundation 4e by Axelos]], | ||
| + | :[[Minimum viable product]] ([[MVP]]). A product with just enough features to satisfy early customers, and to provide feedback for future product development. | ||
| + | |||
| + | [[Category: Information Technology]] | ||
Revision as of 16:41, 11 December 2020
A minimum viable product (alternatively known as an introductory product or, often, by its acronym, MVP) is a version of a work product that includes sufficient features to satisfy early adopters and allows a team to collect the maximum amount of validated learning about customers with the least effort.
Definitions
According to the ITIL Foundation 4e by Axelos,
- Minimum viable product (MVP). A product with just enough features to satisfy early customers, and to provide feedback for future product development.
