Successfully reported this slideshow.

Lean Software Development: Validated Learning

1

Share

Loading in …3
×
1 of 118
1 of 118

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Lean Software Development: Validated Learning

  1. 1. VALIDATED LEARNING Òscar Vilaplana dev@oscarvilaplana.cat Paylogic August 2014
  2. 2. VALIDATED LEARNING A Tale of Business, Vanity and Medieval Torture Òscar Vilaplana dev@oscarvilaplana.cat Paylogic August 2014
  3. 3. Progress
  4. 4. Learn
  5. 5. we failed
  6. 6. we failed but at least we learned something
  7. 7. Failed
  8. 8. Learned
  9. 9. Learning is vital
  10. 10. What works?
  11. 11. What works? What do customers want?
  12. 12. What works? What do customers want? Right path?
  13. 13. Goals
  14. 14. Demonstrate progress
  15. 15. Demonstrate progress Discover truths
  16. 16. Demonstrate progress Discover truths Prevent failure
  17. 17. Can
  18. 18. Should
  19. 19. Sustainable
  20. 20. Break down & Test
  21. 21. Did it make the product better?
  22. 22. How do we know?
  23. 23. Plead guilty
  24. 24. Trial by ordeal
  25. 25. 208
  26. 26. ?
  27. 27. 2/3
  28. 28. Teaching the garden to weed itself
  29. 29. Make truth reveal itself
  30. 30. Is there interest?
  31. 31. Expertise
  32. 32. Knowledge
  33. 33. Progress
  34. 34. According to plan
  35. 35. According to plan High quality
  36. 36. According to plan High quality Expected costs
  37. 37. If nobody wants it,
  38. 38. If nobody wants it, High quality, done in budget
  39. 39. If nobody wants it,
  40. 40. If nobody wants it, High quality, done in budget
  41. 41. tchair → 36.8°C
  42. 42. tchair → 36.8°C $ → 0
  43. 43. Experiment
  44. 44. Experiment: product
  45. 45. Experiment: product Solve real problems
  46. 46. Experiment: product Solve real problems When ready, it has already customers
  47. 47. Questions
  48. 48. Do customers have this problem?
  49. 49. Do customers have this problem? Would they buy a solution?
  50. 50. Do customers have this problem? Would they buy a solution? From us?
  51. 51. Do customers have this problem? Would they buy a solution? From us? Can we build it?
  52. 52. Answers
  53. 53. Identify
  54. 54. What should we test?
  55. 55. What should we test? What are the riskiest parts of the plan?
  56. 56. What should we test? What are the leaps of faith?
  57. 57. Build-Measure-Learn
  58. 58. MVP
  59. 59. Min product for a loop turn.
  60. 60. Min product for a loop turn. Min effort and dev time.
  61. 61. Min product for a loop turn. Min effort and dev time. Lacks essential features.
  62. 62. Min product for a loop turn. Min effort and dev time. Lacks essential features. Measurable impact.
  63. 63. Minimum
  64. 64. 3rd party Apps? Carrier choice? 3G? iChat? Calendar? WiFi sync? Word/Excel docs?
  65. 65. Any additional work beyond what was required to start learning is waste. No matter how important it might have seemed at the time.
  66. 66. Vanity Metrics
  67. 67. Changes
  68. 68. Changes Increase of sales
  69. 69. Changes Increase of sales More Changes
  70. 70. Changes Increase of sales More Changes More increase of sales
  71. 71. Learn
  72. 72. Baseline
  73. 73. Baseline Tune
  74. 74. Baseline Tune Pivot or Persevere
  75. 75. Kanban
  76. 76. Include validation: more productive
  77. 77. Include validation: more productive Why build feature not part of test?
  78. 78. Include validation: more productive Why build feature not part of test? Why build story unless well understood?
  79. 79. Learn more
  80. 80. Learn more
  81. 81. Thanks

×