Uploaded byEric Ries
The Lean Startup at Code for America fellows
The document discusses the Lean Startup methodology for developing products under conditions of extreme uncertainty. It advocates for minimizing the time between product iterations or "pivots" through rapid experimentation and validated learning about customers. This is achieved by adopting practices like continuous integration, deployment and testing to get fast feedback; measuring key metrics through techniques like A/B testing and cohort analysis; and employing customer development processes to gain insights. The document debunks some myths about Lean Startups and provides examples of how companies have implemented continuous deployment and a "cluster immune system" to learn quickly from customers.
More Related Content
Similar to The Lean Startup at Code for America fellows
The Lean Startup at Code for America fellows
- 1. The Lean Startup#leanstartup“Innovationthrough experimentation”Eric Ries (@ericries)http://StartupLessonsLearned.com
- 2.
- 3.
- 4.
- 5. What is astartup?A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty.
- 6. Nothing to dowith size of company, sector of the economy, or industryThe Pivot
- 7.
- 8. The PivotWhat dosuccessful startups have in common?
- 9. They started outas digital cash for PDAs, but evolved into online payments for eBay.
- 10. They started buildingBASIC interpreters, but evolved into the world's largest operating systems monopoly.
- 11. They were shockedto discover their online games company was actually a photo-sharing site.
- 12. Pivot: change directionsbut stay grounded in what we’ve learned. Speed WinsIf we can reduce the time between pivotsWe can increase our odds of successBefore we run out of money
- 13. Making ProgressIn alean transformation, question #1 is – which activities are value-creating and which are waste?
- 14. In traditional business,value is created by delivering products or services to customers
- 15. In a startup,the product and customer are unknowns. We need a new definition of value for startups: validated learning about customersTraditional Product DevelopmentUnit of Progress: Advance to Next StageWaterfallRequirementsSpecificationsDesignProblem: knownSolution:knownImplementationVerificationMaintenance
- 16. Agile Product DevelopmentUnitof Progress: A line of Working Code“Product Owner” or in-house customerProblem: knownSolution:unknown
- 17. Lean StartupUnit ofProgress: Validated Learning About Customers ($$$)Customer DevelopmentHypotheses, Experiments,InsightsProblem:unknownData, Feedback,InsightsSolution:unknownAgile Development
- 18. Minimize TOTAL timethrough the loop
- 19. There’s much more…BuildFasterUnit TestsUsability TestsContinuous IntegrationIncremental DeploymentFree & Open-SourceCloud ComputingCluster Immune SystemJust-in-time ScalabilityRefactoringDeveloper SandboxMinimum Viable ProductLearn FasterSplit TestsCustomer DevelopmentFive WhysCustomer Advisory BoardFalsifiable HypothesesProduct OwnerAccountabilityCustomer ArchetypesCross-functional TeamsSemi-autonomous TeamsSmoke TestsMeasure FasterFunnel AnalysisCohort AnalysisNet Promoter ScoreSearch Engine MarketingPredictive MonitoringMeasure FasterSplit TestsContinuous DeploymentUsability TestsReal-time Monitoring & AlertingCustomer Liaison
- 21. Myth #1MythLean meanscheap. Lean startups try to spend as little money as possible.Truth The Lean Startup method is not about cost, it is about speed.
- 22. Myth #2MythThe LeanStartup is only for Web 2.0/internet/consumer software companies.Truth The Lean Startup applies to all companies that face uncertainty about what customers will want.
- 23. Myth #3MythLean Startupsare small bootstrapped startups.Truth Lean Startups are ambitious and are able to deploy large amounts of capital.
- 24. Myth #4MythLean Startupsreplace vision with dataor customer feedback.Truth Lean Startups are driven by a compelling vision, and are rigorous about testing each element of this vision
- 25.
- 26. The Lean Startupto be published by Crown in Fall, 2011
- 27.
- 28.
- 29.
- 30. Getting in touch(#leanstartup)
- 31.
- 32.
- 33.
- 34. Lean Startup Wiki http://leanstartup.pbworks.com
- 35. Lean Startup Circle http://leanstartupcircle.comContinuous DeploymentLearn FasterCustomer DevelopmentFive WhysBuild FasterContinuous DeploymentSmall BatchesMinimum Viable ProductRefactoringMeasure FasterSplit TestingActionable MetricsNet Promoter ScoreSEM
- 36. Continuous DeploymentDeploy newsoftware quickly
- 37. At IMVU timefrom check-in to production = 20 minutes
- 38. Tell a goodchange from a bad change (quickly)
- 39. Revert a badchange quickly
- 40. And “shut downthe line”
- 41. Work in smallbatches
- 42. At IMVU, alarge batch = 3 days worth of work
- 43. Break large projectsdown into small batchesCluster Immune SystemWhat it looks like to ship one piece of code to production:Run tests locally (SimpleTest, Selenium)
- 44. Everyone has acomplete sandbox
- 45. Continuous Integration Server(BuildBot)
- 46. All tests mustpass or “shut down the line”
- 47. Automatic feedback ifthe team is going too fast
- 48.
- 49. Monitor cluster andbusiness metrics in real-time
- 50. Reject changes thatmove metrics out-of-bounds
- 51. Alerting & Predictivemonitoring (Nagios)
- 52. Monitor all metricsthat stakeholders care about
- 53. If any metricgoes out-of-bounds, wake somebody up
- 54. Use historical trendsto predict acceptable bounds
- 55. When customers seea failure
- 56. Fix the problemfor customers
- 57. Improve your defensesat each level