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#leanstartupEric Ries (@ericries)http://StartupLessonsLearned.blogspot.com

2. Traditional Product DevelopmentUnit of Progress: Advance to Next StageWaterfallRequirementsSpecificationDesignProblem: knownSolution: knownImplementationVerificationMaintenance

3. Agile Product DevelopmentUnit of Progress: A line of Working Code“Product Owner” or in-house customerProblem: knownSolution: unknown

4. Product Development at Lean StartupUnit of Progress: Validated Learning About Customers ($$$)Customer DevelopmentHypotheses,Experiments,InsightsProblem: unknownData,Feedback,InsightsSolution: unknown

5. Minimize TOTAL time through the loopIDEASLEARNBUILDDATACODEMEASURE

6. There’s much more…IDEASCode FasterLearn FasterBUILDLEARNUnit TestsUsability TestsContinuous IntegrationIncremental DeploymentFree & Open-Source ComponentsCloud ComputingCluster Immune SystemJust-in-time ScalabilityRefactoringDeveloper SandboxMinimum Viable ProductSplit TestsCustomer InterviewsCustomer DevelopmentFive Whys Root Cause AnalysisCustomer Advisory BoardFalsifiable HypothesesProduct Owner AccountabilityCustomer ArchetypesCross-functional TeamsSemi-autonomous TeamsSmoke TestsCODEDATAMeasure FasterMEASURESplit TestsClear Product OwnerContinuous DeploymentUsability TestsReal-time MonitoringCustomer LiaisonFunnel AnalysisCohort AnalysisNet Promoter ScoreSearch Engine MarketingReal-Time AlertingPredictive Monitoring