Difference between revisions of "Minimum viable product"
| (2 intermediate revisions by the same user not shown) | |||
| 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 | + | A [[minimum viable product]] (sometimes, [[minimal 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]] | ||
Latest revision as of 03:50, 16 November 2022
A minimum viable product (sometimes, minimal 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.
