Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Slow Down To Speed Up


Published on

These slides are part of a presentation given at Silicon Valley code Camp 2009.

Published in: Education
  • Be the first to comment

  • Be the first to like this

Slow Down To Speed Up

  1. 1. Slow Down to Speed Up Workshop & Discovery Session Silicon Valley Code Camp October, 2009
  2. 2. Welcome to Agile AeroSpace (first shift) <ul><ul><li>Build some airplanes
  3. 3. Do a little cost accounting </li></ul></ul>
  4. 4. Some Questions <ul><ul><li>Was anyone idle during the first shift?
  5. 5. What were the results?
  6. 6. How much money did you make (or lose)? </li></ul></ul>
  7. 7. Let's Slow it Down a Little (second shift) <ul><ul><li>Go no faster than the slowest operation
  8. 8. Do a little more cost accounting </li></ul></ul>
  9. 9. Same Questions <ul><ul><li>Was anyone idle during the second shift?
  10. 10. What were the results?
  11. 11. How much money did you make (or lose)? </li></ul></ul>
  12. 12. Some Basic Definitions Throughput The rate at which a system generates money through sales . Inventory All the money that a system has invested in purchasing things it intends to sell . Operating Expense All the money a system spends in order to turn inventory into throughput .
  13. 13. How to Stay in Business Throughput Inventory Operating Expense
  14. 14. So What Does All This Have To Do With Developing Software? Software development is not the same as manufacturing
  15. 15. Software Development is About Creating and Sharing Knowledge <ul><ul><li>Knowledge is the Inventory of software development
  16. 16. People consume knowledge at their own rate
  17. 17. Creating knowledge faster than it can be consumed does not increase throughput </li></ul></ul>
  18. 18. Questions ?
  19. 19. 5 Steps <ul><ul><li>Identify the system's bottlenecks.
  20. 20. Decide how to exploit the bottlenecks.
  21. 21. Subordinate everything else to the above decision.
  22. 22. Elevate the system's bottlenecks.
  23. 23. If, in a previous step, a bottleneck has been broken, go back to step 1. </li></ul></ul>(From The Goal, page 301)