The document outlines three approaches to product development: traditional waterfall, agile development, and lean startup. Traditional waterfall involves known problems and solutions and advancing in stages. Agile development has a known problem but unknown solution and focuses on working code. Lean startup has unknown problems and solutions and emphasizes validated learning about customers through experiments, insights, and minimizing time to learn through building, measuring, and iterating on ideas.

1. Schematic View of Product Development#leanstartup Eric Ries (@ericries) http://StartupLessonsLearned.blogspot.com

2. Traditional Product Development Unit of Progress: Advance to Next Stage Waterfall Requirements Specification Design Problem: known Solution: known Implementation Verification Maintenance

3. Agile Product Development Unit of Progress: A line of Working Code “Product Owner” or in-house customer Problem: known Solution: unknown

4. Product Development at Lean Startup Unit of Progress: Validated Learning About Customers ($$$) Customer Development Hypotheses, Experiments, Insights Problem: unknown Data, Feedback, Insights Solution: unknown

5. Minimize TOTAL time through the loop IDEAS LEARN BUILD DATA CODE MEASURE

6. There’s much more… IDEAS Code Faster Learn Faster BUILD LEARN Unit Tests Usability Tests Continuous Integration Incremental Deployment Free & Open-Source Components Cloud Computing Cluster Immune System Just-in-time Scalability Refactoring Developer Sandbox Minimum Viable Product Split Tests Customer Interviews Customer Development Five Whys Root Cause Analysis Customer Advisory Board Falsifiable Hypotheses Product Owner Accountability Customer Archetypes Cross-functional Teams Semi-autonomous Teams Smoke Tests CODE DATA Measure Faster MEASURE Split Tests Clear Product Owner Continuous Deployment Usability Tests Real-time Monitoring Customer Liaison Funnel Analysis Cohort Analysis Net Promoter Score Search Engine Marketing Real-Time Alerting Predictive Monitoring