Difference between revisions of "Minimal viable product"

From Pearl Language
Jump to navigation Jump to search
(+= The Lean Startup)
(Bockground++ += Forces)
Line 2: Line 2:
|goal=test strategic assumptions and hypotheses in a series of rapid feedback loops
|goal=test strategic assumptions and hypotheses in a series of rapid feedback loops
|theme=Agile, Maneuver, Lean
|theme=Agile, Maneuver, Lean
|background={{mvp}}s:
|background===Acceleration==
*generally accelerate: the first {{mvp}} takes three quarters, the second only two, the third just one and then they start to come in every other week or so.
{{mvp}}s generally accelerate: the first {{mvp}} takes three quarters, the second only two, the third just one and then they start to come in every other week or so. Each time you will be able to validate or refute your next hypotheses faster than before.
 
==Forces==
*every {{mvp}} that results from a {{p|pivot}} both destroys and creates product infrastructure, platform and features, so this accounts for just a part of the acceleration;
*as the product evolves, it turns into legacy, potentially slowing development down;
*learning critical things about needs, customers, markets, and strategy will accelerate development and {{p|pivots}}.
}}
}}
{{tag|experiment}}
{{tag|experiment}}
Line 21: Line 26:
{{Source
{{Source
|source=The Lean Startup
|source=The Lean Startup
|author=Eric Ries,  
|author=Eric Ries,
|coder=Martien van Steenbergen
|coder=Martien van Steenbergen
}}
}}

Revision as of 14:08, 24 August 2015

…{{{context}}}

✣  ✣  ✣

{{{wish full}}}

Acceleration

minimal viable products generally accelerate: the first minimal viable product takes three quarters, the second only two, the third just one and then they start to come in every other week or so. Each time you will be able to validate or refute your next hypotheses faster than before.

Forces

  • every minimal viable product that results from a pivot both destroys and creates product infrastructure, platform and features, so this accounts for just a part of the acceleration;
  • as the product evolves, it turns into legacy, potentially slowing development down;
  • learning critical things about needs, customers, markets, and strategy will accelerate development and pivots.

Therefore:

{{{therefore full}}}

✣  ✣  ✣



✣  ✣  ✣

Sources