The Lean Startup at Code for America fellows
4 likes708 views
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.
The Lean Startup at Code for America fellows
- 1. The Lean Startup#leanstartup“Innovation through experimentation”Eric Ries (@ericries)http://StartupLessonsLearned.com
- 5. What is a startup?A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty.
- 6. Nothing to do with size of company, sector of the economy, or industryThe Pivot
- 7. I’
- 8. The PivotWhat do successful startups have in common?
- 9. They started out as digital cash for PDAs, but evolved into online payments for eBay.
- 10. They started building BASIC interpreters, but evolved into the world's largest operating systems monopoly.
- 11. They were shocked to discover their online games company was actually a photo-sharing site.
- 12. Pivot: change directions but 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 a lean 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 DevelopmentUnit of Progress: A line of Working Code“Product Owner” or in-house customerProblem: knownSolution:unknown
- 17. Lean StartupUnit of Progress: Validated Learning About Customers ($$$)Customer DevelopmentHypotheses, Experiments,InsightsProblem:unknownData, Feedback,InsightsSolution:unknownAgile Development
- 18. Minimize TOTAL time through the loop
- 19. There’s much more…Build FasterUnit 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 means cheap. 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 Lean Startup 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 Startups are small bootstrapped startups.Truth Lean Startups are ambitious and are able to deploy large amounts of capital.
- 24. Myth #4MythLean Startups replace vision with dataor customer feedback.Truth Lean Startups are driven by a compelling vision, and are rigorous about testing each element of this vision
- 26. The Lean Startup to be published by Crown in Fall, 2011
- 28. Startup Lessons Learned Blog
- 30. Getting in touch (#leanstartup)
- 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 new software quickly
- 37. At IMVU time from check-in to production = 20 minutes
- 38. Tell a good change from a bad change (quickly)
- 39. Revert a bad change quickly
- 40. And “shut down the line”
- 41. Work in small batches
- 42. At IMVU, a large batch = 3 days worth of work
- 43. Break large projects down into small batchesCluster Immune SystemWhat it looks like to ship one piece of code to production:Run tests locally (SimpleTest, Selenium)
- 44. Everyone has a complete sandbox
- 45. Continuous Integration Server (BuildBot)
- 46. All tests must pass or “shut down the line”
- 47. Automatic feedback if the team is going too fast
- 49. Monitor cluster and business metrics in real-time
- 50. Reject changes that move metrics out-of-bounds
- 51. Alerting & Predictive monitoring (Nagios)
- 52. Monitor all metrics that stakeholders care about
- 53. If any metric goes out-of-bounds, wake somebody up
- 54. Use historical trends to predict acceptable bounds
- 55. When customers see a failure
- 56. Fix the problem for customers
- 57. Improve your defenses at each level