This document discusses minimum viable products (MVPs). An MVP is not a prototype but rather aims to test fundamental business hypotheses with the minimum necessary features, including whether customers have a problem an offered solution could address, whether they would buy that solution, and whether that solution can be built. An example of an early MVP is given for Drupal Gardens. The document emphasizes that MVPs should undergo continuous validation loops with customers to test these hypotheses rather than being limited to code.

1. Software Architecture
Prof.Dr.ir. F. Gielen
Minimum Viable Products
Vakgroep Informatietechnologie – IBCN

2. Minimum Viable Product
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 2

3. MVP : Minimum Viable Product
 Minimal Viable Product
 Is not a prototype
 This is for the evaluation technical risks and design
decisions
 MVP’s Goal:
 Test the fundamental business hypothesis
 Do customers recognize that they are having a
problem that you try to solve ?
 If there were a solution, would they buy it ?
 Would they buy it from you ?
 Can we build the solution for that problem ?
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 3

4. MVP example : Drupal Gardens
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 4

5. The Value validating loop
Not just limited to code
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 5