Downloaded 13 times
Uploaded byÒscar Vilaplana
Lean Software Development: Validated Learning
This document discusses the importance of validated learning and experimentation when developing products. It advocates for a minimum viable product approach where the goal is to learn what customers want through quick, measurable experiments. Features should be prioritized based on learning what solves real problems for customers rather than vanity metrics. The process should involve establishing a baseline, tuning based on data from tests and customer feedback, and deciding whether to pivot or persevere.
More Related Content
![[Webinar] Innovate Faster by Adopting The Modern Growth Stack](https://cdn.slidesharecdn.com/ss_thumbnails/webinarinnovatefasterwiththemoderngrowthstack-180124222436-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Lean Software Development: Validated Learning
Lean Software Development: Validated Learning
- 1. VALIDATED LEARNING ÒscarVilaplana dev@oscarvilaplana.cat Paylogic August 2014
- 2. VALIDATED LEARNING ATale of Business, Vanity and Medieval Torture Òscar Vilaplana dev@oscarvilaplana.cat Paylogic August 2014
- 3.
- 4.
- 5.
- 6. we failed butat least we learned something
- 7.
- 8.
- 9.
- 10.
- 11. What works? Whatdo customers want?
- 12. What works? Whatdo customers want? Right path?
- 13.
- 14.
- 15.
- 16. Demonstrate progress Discovertruths Prevent failure
- 17.
- 18.
- 19.
- 20. Break down &Test
- 22. Did it makethe product better?
- 23. How do weknow?
- 26.
- 27.
- 29.
- 30.
- 31.
- 33. Teaching the garden to weed itself
- 34. Make truth revealitself
- 42.
- 44.
- 45.
- 46.
- 47.
- 48. According to plan High quality
- 49. According to plan High quality Expected costs
- 51.
- 52. If nobody wantsit, High quality, done in budget
- 54.
- 55. If nobody wantsit, High quality, done in budget
- 57.
- 58. tchair → 36.8°C $ → 0
- 59.
- 60.
- 61. Experiment: product Solvereal problems
- 62. Experiment: product Solvereal problems When ready, it has already customers
- 63.
- 64. Do customers havethis problem?
- 65. Do customers havethis problem? Would they buy a solution?
- 66. Do customers havethis problem? Would they buy a solution? From us?
- 67. Do customers havethis problem? Would they buy a solution? From us? Can we build it?
- 68.
- 71.
- 73. What should wetest?
- 74. What should wetest? What are the riskiest parts of the plan?
- 75. What should wetest? What are the leaps of faith?
- 76.
- 78.
- 80. Min product fora loop turn.
- 81. Min product fora loop turn. Min effort and dev time.
- 82. Min product fora loop turn. Min effort and dev time. Lacks essential features.
- 83. Min product fora loop turn. Min effort and dev time. Lacks essential features. Measurable impact.
- 84.
- 86. 3rd party Apps? Carrier choice? 3G? iChat? Calendar? WiFi sync? Word/Excel docs?
- 93. Any additional work beyond what was required to start learning is waste. No matter how important it might have seemed at the time.
- 95.
- 97.
- 98. Changes Increase ofsales
- 99. Changes Increase ofsales More Changes
- 100. Changes Increase ofsales More Changes More increase of sales
- 103.
- 105.
- 106.
- 107. Baseline Tune Pivotor Persevere
- 108.
- 113. Include validation: moreproductive
- 114. Include validation: moreproductive Why build feature not part of test?
- 115. Include validation: moreproductive Why build feature not part of test? Why build story unless well understood?
- 116.
- 117.
- 118.