This document discusses the importance of data driven development. It emphasizes using metrics and hypothesis testing to iteratively build and validate minimum viable products (MVPs). Key aspects covered include defining metrics, developing hypothesis statements, building MVPs, monitoring metrics, learning from data, and continuous improvement through addressing technical debt. The overall message is that data should guide decision making throughout the development process.
21. [An MVP] is a concise summary of the smallest
possible group of features that will work as a
stand-alone product while still solving at least the “core”
problem and demonstrating the product’s value.
“
- Steve Blank
51. Types of Technical Debt
Reckless Prudent
Deliberate
Inadvertent
“We don’t have time
for design”
“We must ship now
and deal with
consequences”
“We now know how we
should have done it”
“What is Layering?”