Build-Measure-Learn - What software enterprises can learn from startups - XP Days 2013
•
3 j'aime•2,006 vues
This document discusses lean startup practices and agile development. It promotes building minimum viable products and measuring results through quick iterations to gain validated learning. Diagrams show the lean startup cycle of making business hypotheses, defining experiments, building measurement into MVPs, measuring results, and deciding to persevere or pivot. The document advocates applying lean startup practices beyond just young tech ventures and emphasizes customer development through build-measure-learn cycles.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Build-Measure-Learn - What software enterprises can learn from startups - XP Days 2013
Similaire à Build-Measure-Learn - What software enterprises can learn from startups - XP Days 2013 (20)
Plus de Tobias Schimmer
Plus de Tobias Schimmer (20)
Dernier
Dernier (20)
Build-Measure-Learn - What software enterprises can learn from startups - XP Days 2013
- 1. Bauen, Messen und Lernen im großen Stil – vom Software-Konzern zurück zum Startup Christian Binder, Microsoft Dr. Tobias Hildenbrand, SAP AG
- 8. Flow of Value Reduction of Waste Transparency, with practices including Scrum Unit Testing Test-Driven Development Continuous Integration Small Batches Definition of Done Exploratory Testing…
- 10. Lean Startups “Lean-startup practices aren’t just for young tech ventures” Steve Blank Customer Development requires Build-Measure-Learn cycles http://theleanstartup.com/principles
- 11. Build, Measure and Learn in Quick Iterations
- 13. 1. MAKE BUSINESS HYPOTHESIS A TESTABLE EXPERIMENT 2. DEFINE EXPERIMENT AS MINIMUM VIABLE PRODUCT (MVP) 3. BUILD MEASUREMENT INTO MVP 6. PERSEVERE OR PIVOT 5. GAIN VALIDATED LEARNING 4. MEASURE THE RESULTS
- 14. … " In Zuckerberg's S-1 letter from earlier in 2012, he wrote, "The idea is that if you never break anything, you’re probably not moving fast enough.“…. Source: http://investing.covestor.com/2013/01/the-most-important-difference-between-facebook-andgoogle?aff=TAB&utm_source=TAB&utm_medium=taboola&utm_campaign=content
- 16. VS 2010 TF Service VS2012 and beyond n/a ~3 Weekly updates Feature Packs & Servicing Quarterly updates Bi-annual Annual (rapid cadence, cloud deployed) Core product updates (periodic, highly compatible) Core product release (new baseline, product upgrade)
- 17. Kanban support Enhanced agile planning Web testing code coverage Enhanced Test Manager Kanban customization Work Item enhancements TCM Web management System Center integration Windows Store development enhancements C++ targeting XP Win Store Apps instrumentation Win Phone unit tests Testing scenarios for SharePoint SharePoint IntelliTrace LightSwitch HTML & SharePoint apps Blend for WPF, SL, SketchFlow Extended support for VS Updates Code visualization: CodeMap Blue theme CodeMap debugger integration
- 19. Done!
- 20. 10 – 12 weeks 6 weeks 3 weeks
- 21. Pre-Lean Lean Dev “Quarterly Shipments” up to 18 months 6 months 3 months
- 24. Keep Iterating Sprint Results Validate your Assumption Build Early Prototypes
- 26. A Diverse Team… An Iterative Approach… A Creative Space…
- 27. WORKING Software
- 30. Rank TFS ID Resolution PU Hits CABs Details #1 358582 Fixed VS: Pro 1010 6.0% 45 xxxxxx.DLL!== [Crash32_Normal: 0xC0000005] #2 276670 (Active) VS: Ultimate 454 2.7% 9 xxxxxxx.DLL!xxxxxxxxxx [Crash32_Normal: 0xC0000005] #3 378926 (Active) NDP: WPF 326 1.9% 42 xxxxxxxx.DLL!unknown [Crash32_Normal: 0xC0000005] #4 372955 (Active) VS: Pro 313 1.9% 21 xxxxxxxx.DLL!Microsoft.VisualStudio.xxxxx #5 374532 Fixed VS: Ultimate 226 1.3% 8 xxxxxx.DLL!ScriptDM::xxxxxxxxxx::
- 40. Customer Development - Build - Measure - Learn Agile Engineering Teams and Product Units Business Thinking