Your SlideShare is downloading. ×
Sufficient Design
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Sufficient Design

1,752
views

Published on

If your software product were a film, which of its features would be a movie star, a supporting actor or an extra? …

If your software product were a film, which of its features would be a movie star, a supporting actor or an extra?

Should you invest more in the software design of star features, especially if they generate the most revenue? And if so, what level of design quality is sufficient forfeatures that are supporting actors or extras? Doesn't Software Craftsmanship tell us that we need to write clean and simple code, regardless of its role? Or, if we are Lean and focus on increasing the speed of concept to cash, will quality suffer?

Sufficient Design answers these questions and points the way towards how to blend Lean processes with Software Craftsmanship.

Published in: Technology

1 Comment
9 Likes
Statistics
Notes
No Downloads
Views
Total Views
1,752
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
40
Comments
1
Likes
9
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. December 2010 Joshua Kerievsky Industrial Logic, Inc. Twitter: @JoshuaKerievsky #SufficientDesign Sufficient DesignThursday, December 16, 2010
  • 2. ThereIFixedIt.comThursday, December 16, 2010
  • 3. ThereIFixedIt.comThursday, December 16, 2010
  • 4. ThereIFixedIt.comThursday, December 16, 2010
  • 5. ThereIFixedIt.comThursday, December 16, 2010
  • 6. ThereIFixedIt.comThursday, December 16, 2010
  • 7. ThereIFixedIt.comThursday, December 16, 2010
  • 8. Thursday, December 16, 2010
  • 9. What Is Sufficient Design?Thursday, December 16, 2010
  • 10. Thursday, December 16, 2010
  • 11. Thursday, December 16, 2010
  • 12. Build It Right!Thursday, December 16, 2010
  • 13. Build It Ship It Right! Fast!Thursday, December 16, 2010
  • 14. Thursday, December 16, 2010
  • 15. What Is Best? Build It Ship It Right! Fast!Thursday, December 16, 2010
  • 16. Thursday, December 16, 2010
  • 17. Fast Dirty Clean SlowThursday, December 16, 2010
  • 18. Fast Dirty Clean SlowThursday, December 16, 2010
  • 19. Fast Dirty Clean SlowThursday, December 16, 2010
  • 20. Fast Dirty Clean SlowThursday, December 16, 2010
  • 21. Fast Dirty Clean SlowThursday, December 16, 2010
  • 22. Fast DEFECT Dirty Clean SlowThursday, December 16, 2010
  • 23. Value Low High Demand Low High Delivery Slow FastThursday, December 16, 2010
  • 24. Design Complex Simple Debt Low High Development Assembled CraftedThursday, December 16, 2010
  • 25. 5.X Development DeathcycleThursday, December 16, 2010
  • 26. 1.0 ReleaseThursday, December 16, 2010
  • 27. 2.0 ReleaseThursday, December 16, 2010
  • 28. 3.0 ReleaseThursday, December 16, 2010
  • 29. 4.0 ReleaseThursday, December 16, 2010
  • 30. 5.0 ReleaseThursday, December 16, 2010
  • 31. Cost Actual of CoCChange(CoC) Release Optimal CoC 1 2 3 4 5 Years Model courtesy of Jim HighsmithThursday, December 16, 2010
  • 32. Cost Actual of CoCChange(CoC) Release Technical Debt Optimal CoC 1 2 3 4 5 Years Model courtesy of Jim HighsmithThursday, December 16, 2010
  • 33. Customer Responsiveness Cost Actual of CoCChange(CoC) Release Technical Debt Optimal CoC 1 2 3 4 5 Years Model courtesy of Jim HighsmithThursday, December 16, 2010
  • 34. Thursday, December 16, 2010
  • 35. Thursday, December 16, 2010
  • 36. Thursday, December 16, 2010
  • 37. Thursday, December 16, 2010
  • 38. Thursday, December 16, 2010
  • 39. Thursday, December 16, 2010
  • 40. Thursday, December 16, 2010
  • 41. Thursday, December 16, 2010
  • 42. Thursday, December 16, 2010
  • 43. Thursday, December 16, 2010
  • 44. Thursday, December 16, 2010
  • 45. Thursday, December 16, 2010
  • 46. Sufficient Design Case StudiesThursday, December 16, 2010
  • 47. Thursday, December 16, 2010
  • 48. Thursday, December 16, 2010
  • 49. Manufacture In Bulk At Low CostThursday, December 16, 2010
  • 50. Deliver At No Cost To Least ServedThursday, December 16, 2010
  • 51. Goal: Quickly Deliver To 20 Million PeopleThursday, December 16, 2010
  • 52. $59.20 Competitor? $150 Cheap Tough, Tough Steel Frame Simple Patio Durable Cheap Cheaply Parts + Furniture Bike Tire Castors Produced AssemblyThursday, December 16, 2010
  • 53. $59.20 Competitor? $150 Cheap Tough, Tough Steel Frame Simple Patio Durable Cheap Cheaply Parts + Furniture Bike Tire Castors Produced AssemblyThursday, December 16, 2010
  • 54. Value Low High Demand Low High Delivery Slow FastThursday, December 16, 2010
  • 55. Design Complex Simple Debt Low High Development Assembled CraftedThursday, December 16, 2010
  • 56. Thursday, December 16, 2010
  • 57. Value Low High Demand Low High Delivery Slow FastThursday, December 16, 2010
  • 58. Design Complex Simple Debt Low High Development Assembled CraftedThursday, December 16, 2010
  • 59. Quick Collaboration on the WebThursday, December 16, 2010
  • 60. Value Low High Demand Low High Delivery Slow FastThursday, December 16, 2010
  • 61. Design Complex Simple Debt Low High Development Assembled CraftedThursday, December 16, 2010
  • 62. Thursday, December 16, 2010
  • 63. Value Low High Demand Low High Delivery Slow FastThursday, December 16, 2010
  • 64. Design Complex Simple Debt Low High Development Assembled CraftedThursday, December 16, 2010
  • 65. Thursday, December 16, 2010
  • 66. Thursday, December 16, 2010
  • 67. Value Low High Demand Low High Delivery Slow FastThursday, December 16, 2010
  • 68. Design Complex Simple Debt Low High Development Assembled CraftedThursday, December 16, 2010
  • 69. Thursday, December 16, 2010
  • 70. Thursday, December 16, 2010
  • 71. Thursday, December 16, 2010
  • 72. Thursday, December 16, 2010
  • 73. Value Low High Demand Low High Delivery Slow FastThursday, December 16, 2010
  • 74. Design Complex Simple Debt Low High Development Assembled CraftedThursday, December 16, 2010
  • 75. Thursday, December 16, 2010
  • 76. SketchThursday, December 16, 2010
  • 77. SketchThursday, December 16, 2010
  • 78. Sketch CraftThursday, December 16, 2010
  • 79. Sketch Craft RefineThursday, December 16, 2010
  • 80. Fowler’s Design Payoff LineThursday, December 16, 2010
  • 81. Thursday, December 16, 2010
  • 82. “Good Enough” involves rational choices, not compulsive behavior. -James Bach, Good Enough QualityThursday, December 16, 2010
  • 83. Thursday, December 16, 2010
  • 84. Thursday, December 16, 2010
  • 85. Thursday, December 16, 2010
  • 86. Thursday, December 16, 2010
  • 87. Sufficient Design may be Excellent to Poor design based on the CONTEXT at hand.Thursday, December 16, 2010
  • 88. Good Enough has nothing to do with mediocrity. -James Bach, Good Enough QualityThursday, December 16, 2010
  • 89. “Our goal is to achieve an acceptable level of risk.” -James Bach, The Challenge of “Good Enough” SoftwareThursday, December 16, 2010
  • 90. Thursday, December 16, 2010
  • 91. “Learn One New Programming Language Every Year.”Thursday, December 16, 2010
  • 92. “Learn One New Programming Language Every OTHER Year.”Thursday, December 16, 2010
  • 93. Thursday, December 16, 2010
  • 94. Thursday, December 16, 2010
  • 95. Thank You!Thursday, December 16, 2010
  • 96. Bibliography • The Challenge of Good Enough Software, James Bach (www.satisfice.com/articles/ gooden2.pdf) • Good Enough Quality, James Bach (www.satisfice.com/articles/ good_enough_quality.pdf) • Good Enough Never Is (Or Is It?), Eric Ries (http://www.startuplessonslearned.com/ 2010/09/good-enough-never-is-or-is-it.html)Thursday, December 16, 2010