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.

Rolling Rocks Downhill @ Agile cymru by Clarke Ching

1,991 views

Published on

Clarke Ching's Agile Cymru presentation on using Goldratt's TOC to accelerate Agile projects.

Published in: Business
  • Be the first to comment

Rolling Rocks Downhill @ Agile cymru by Clarke Ching

  1. 1. How to: Roll Rocks Downhill www.Rolls.Rocks @clarkeching
  2. 2. How to: Roll Rocks Downhill Accelerate  Agile  with  Goldratt’s  TOC. www.Rolls.Rocks @clarkeching
  3. 3. How to: Roll Rocks Downhill Accelerate  Agile  with  Goldratt’s  TOC. www.Rolls.Rocks @clarkeching By  Clarke  Ching
  4. 4. Before After Rolling Rocks Downhill
  5. 5. Before After Rolling Rocks Downhill Big Batch Small Batch
  6. 6. Before After Rolling Rocks Downhill Big Batch Small Batch Limited WIP Iterative Incremental
  7. 7. Before After Rolling Rocks Downhill Big Batch Small Batch Limited WIP Accelerate by improving the Bottleneck Iterative Incremental
  8. 8. TOC = Theory of Constraints
  9. 9. TOC = Theory of Constraints
  10. 10. TOC = Theory of Constraints
  11. 11. TOC = Theory of Constraints
  12. 12. TOC = Theory of Constraints
  13. 13. TOC = Theory of Constraints
  14. 14. TOC = Theory of Constraints
  15. 15. TOC = Theory of Constraints
  16. 16. How do you make a CHAIN stronger?
  17. 17. How do you make a CHAIN stronger? Q: What is your GOAL?
  18. 18. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight)
  19. 19. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain?
  20. 20. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link
  21. 21. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link Q: What happens if you strengthen the weakest link?
  22. 22. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link Q: What happens if you strengthen the weakest link? A: The chain gets stronger
  23. 23. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link Q: What happens if you strengthen the weakest link? A: The chain gets stronger Q: Or, what else might happen?
  24. 24. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link Q: What happens if you strengthen the weakest link? A: The chain gets stronger Q: Or, what else might happen? A: If that link is no longer the weakest, the chain just gets heavier
  25. 25. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link Q: What happens if you strengthen the weakest link? A: The chain gets stronger Q: Or, what else might happen? A: If that link is no longer the weakest, the chain just gets heavier Q: Generally, what happens if you strengthen any link other than the weakest?
  26. 26. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link Q: What happens if you strengthen the weakest link? A: The chain gets stronger Q: Or, what else might happen? A: If that link is no longer the weakest, the chain just gets heavier Q: Generally, what happens if you strengthen any link other than the weakest? A: The chain gets heavier, not stronger.
  27. 27. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link Q: What happens if you strengthen the weakest link? A: The chain gets stronger Q: Or, what else might happen? A: If that link is no longer the weakest, the chain just gets heavier Q: Generally, what happens if you strengthen any link other than the weakest? A: The chain gets heavier, not stronger. The “weakest link” is our “Constraint”.
  28. 28. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link Q: What happens if you strengthen the weakest link? A: The chain gets stronger Q: Or, what else might happen? A: If that link is no longer the weakest, the chain just gets heavier Q: Generally, what happens if you strengthen any link other than the weakest? A: The chain gets heavier, not stronger. The “weakest link” is our “Constraint”. That’s where we should focus our THINKING.
  29. 29. How do you make a CHAIN stronger? Q: What is your GOAL? A: STRENGTH (not weight) Q: What determines the STRENGTH of the chain? A: The Weakest Link Q: What happens if you strengthen the weakest link? A: The chain gets stronger Q: Or, what else might happen? A: If that link is no longer the weakest, the chain just gets heavier Q: Generally, what happens if you strengthen any link other than the weakest? A: The chain gets heavier, not stronger. The “weakest link” is our “Constraint”. That’s where we should focus our THINKING. Improving anywhere else is either pointless or BAD
 UNLESS
 it improves the performance of the constraint.
  30. 30. Accelerate? What is your Goal?
  31. 31. 1. Deliver more value Accelerate? What is your Goal?
  32. 32. 1. Deliver more value — profitability Accelerate? What is your Goal?
  33. 33. 1. Deliver more value — profitability — accelerate the flow of £££££ Accelerate? What is your Goal?
  34. 34. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time Accelerate? What is your Goal?
  35. 35. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? What is your Goal?
  36. 36. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. What is your Goal?
  37. 37. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. What is your Goal?
  38. 38. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Fixed Date What is your Goal?
  39. 39. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Fixed Date What is your Goal?
  40. 40. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Fixed Date What is your Goal?
  41. 41. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Guaranteed min scope - variable duration Fixed Date What is your Goal?
  42. 42. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Guaranteed min scope - variable duration Fixed Date What is your Goal?
  43. 43. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Guaranteed min scope - variable duration Fixed Date What is your Goal?
  44. 44. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Guaranteed min scope - variable duration Variable scope Fixed Date What is your Goal?
  45. 45. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Guaranteed min scope - variable duration Variable scope Fixed Date What is your Goal?
  46. 46. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Guaranteed min scope - variable duration Variable scope Fixed Date What is your Goal? Better odds of on-time
  47. 47. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Guaranteed min scope - variable duration Variable scope Fixed Date What is your Goal? Better odds of on-time Maybe more variable scope
  48. 48. 1. Deliver more value — profitability — accelerate the flow of £££££ 2. Deliver on time — predictability -> … reputation … credibility Accelerate? Dec 1st “Running 10% faster, gifts you 1 months extra “runway” on a 10 month project. Guaranteed min scope - variable duration Variable scope Fixed Date What is your Goal? Better odds of on-time Maybe more variable scope Perhaps deliver early
  49. 49. Example 1. Request: Eliminate the 120 top-priority defects, ASAP. Team of 16 - mixed roles & skill-sets COBOL, ASP, Oracle
  50. 50. Example 1. Request: Eliminate the 120 top-priority defects, ASAP. Team of 16 - mixed roles & skill-sets time # 120 COBOL, ASP, Oracle
  51. 51. Example 1. Request: Eliminate the 120 top-priority defects, ASAP. Team of 16 - mixed roles & skill-sets Q: Do you have estimates for each defect? A: No, we’ve given up estimating. Q: Why? A: Cos easy looking stuff usually turns out tricky, and so does the hard looking stuff. Q: Is it really that unpredictable? A1: It takes 2-60 days, typically. A2: “We do 10 a month, average” time # 120 COBOL, ASP, Oracle
  52. 52. Example 1. Request: Eliminate the 120 top-priority defects, ASAP. Team of 16 - mixed roles & skill-sets Q: Do you have estimates for each defect? A: No, we’ve given up estimating. Q: Why? A: Cos easy looking stuff usually turns out tricky, and so does the hard looking stuff. Q: Is it really that unpredictable? A1: It takes 2-60 days, typically. A2: “We do 10 a month, average” time # BEFORE - 10 / M 120 COBOL, ASP, Oracle
  53. 53. Example 1. Request: Eliminate the 120 top-priority defects, ASAP. Team of 16 - mixed roles & skill-sets Q: Do you have estimates for each defect? A: No, we’ve given up estimating. Q: Why? A: Cos easy looking stuff usually turns out tricky, and so does the hard looking stuff. Q: Is it really that unpredictable? A1: It takes 2-60 days, typically. A2: “We do 10 a month, average” time # BEFORE - 10 / M 120 COBOL, ASP, Oracle
  54. 54. Example 1. Request: Eliminate the 120 top-priority defects, ASAP. Team of 16 - mixed roles & skill-sets Q: Do you have estimates for each defect? A: No, we’ve given up estimating. Q: Why? A: Cos easy looking stuff usually turns out tricky, and so does the hard looking stuff. Q: Is it really that unpredictable? A1: It takes 2-60 days, typically. A2: “We do 10 a month, average” time # BEFORE - 10 / M AFTER ??? 120 COBOL, ASP, Oracle
  55. 55. Not Started Analysis Design Program
  56. 56. Not Started Analysis Design Program
  57. 57. Not Started Analysis Design Program Test
  58. 58. Not Started Analysis Design Program Test
  59. 59. Not Started Analysis Design Program Test 10/m
  60. 60. Not Started Analysis Design Program Test 20/m 10/m
  61. 61. Not Started Analysis Design Program Test 20/m 25/m 10/m
  62. 62. Not Started Analysis Design Program Test 20/m 15/m25/m 10/m
  63. 63. Not Started Analysis Design Program Test 20/m 10/m15/m25/m 10/m
  64. 64. Not Started Analysis Design Program Test 20/m 10/m15/m25/m 10/m
  65. 65. Not Started Analysis Design Program Test 20/m 10/m15/m25/m Have a told you about the buffalo? 10/m
  66. 66. The Buffalo Story started out as an email joke. Music: http://www.bensound.com
  67. 67. The Buffalo Story started out as an email joke. An imagined conversation between Norm and Cliff, from “Cheers”, the TV Show. Music: http://www.bensound.com image: wikipedia
  68. 68. slowest fastest
  69. 69. Well, you see, Norm, it’s like this. slowest fastest
  70. 70. Well, you see, Norm, it’s like this. A herd of buffalo can only move as fast as the slowest buffalo. slowest fastest
  71. 71. Well, you see, Norm, it’s like this. A herd of buffalo can only move as fast as the slowest buffalo. The slowest buffalo stays at the back and the faster buffalo run in front, but at the slower speed. Otherwise, the herd would split apart. slowest fastest
  72. 72. Like this. slowest fastest
  73. 73. Like this. And when they were split apart they were prone to attack by wolves. slowest fastest
  74. 74. Like this. And when they were split apart they were prone to attack by wolves. slowest fastest
  75. 75. Like this. And when they were split apart they were prone to attack by wolves. Evolution favoured the herds that didn’t spread apart. slowest fastest
  76. 76. slowest fastest
  77. 77. When these tightly packed herds were hunted, the wolves killed the slowest and weakest buffalo. slowest fastest
  78. 78. When these tightly packed herds were hunted, the wolves killed the slowest and weakest buffalo. The guys at the back. slowest fastest
  79. 79. When these tightly packed herds were hunted, the wolves killed the slowest and weakest buffalo. The guys at the back. That made the remaining herd stronger and faster. slowest fastest
  80. 80. When these tightly packed herds were hunted, the wolves killed the slowest and weakest buffalo. The guys at the back. That made the remaining herd stronger and faster. slowest fastest
  81. 81. slowest fastest Here’s the JOKE Bit.
  82. 82. slowest fastest
  83. 83. In much the same way, the human brain can only operate as fast as the slowest brain cells. slowest fastest
  84. 84. In much the same way, the human brain can only operate as fast as the slowest brain cells. [Hmmm … ] slowest fastest
  85. 85. In much the same way, the human brain can only operate as fast as the slowest brain cells. [Hmmm … ] Now, as we know, excessive intake of alcohol kills brain cells. slowest fastest
  86. 86. In much the same way, the human brain can only operate as fast as the slowest brain cells. [Hmmm … ] Now, as we know, excessive intake of alcohol kills brain cells. But naturally, it attacks the slowest and weakest brain cells first. slowest fastest
  87. 87. slowest fastest
  88. 88. In this way, regular consumption of beer eliminates the weaker brain cells, making the brain a faster and more efficient machine. slowest fastest
  89. 89. In this way, regular consumption of beer eliminates the weaker brain cells, making the brain a faster and more efficient machine. And that, Norm, is why you always feel smarter after a few beers. slowest fastest
  90. 90. Not Started Analysis Design Program Test 20/m 10/m15/m25/m Step 1: Identify your bottleneck TOC’s 5 step recipe
  91. 91. Not Started Analysis Design Program Test 20/m 10/m15/m25/m Q: Where’s your “slowest buffalo?” Step 1: Identify your bottleneck TOC’s 5 step recipe
  92. 92. Not Started Analysis Design Program Test 20/m 10/m15/m25/m Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit
  93. 93. Not Started Analysis Design Program Test 20/m 10/m15/m25/m How can we speed up the slowest buffalo? Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit
  94. 94. Not Started Analysis Design Program Test 20/m 10/m15/m25/m How can we speed up the slowest buffalo? Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit test cleverer & faster simple “time management” stuff
  95. 95. Not Started Analysis Design Program Test 20/m 10/m15/m25/m Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit Step 3: Subordinate
  96. 96. Not Started Analysis Design Program Test 20/m 10/m15/m25/m How can the “faster buffalo” help? Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit Step 3: Subordinate
  97. 97. Not Started Analysis Design Program Test 20/m 10/m15/m25/m How can the “faster buffalo” help? Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit Step 3: Subordinate SLOW DOWN! Don’t distract the testers Help them.
  98. 98. Not Started Analysis Design Program Test 20/m 10/m15/m25/m Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit Step 3: Subordinate Step 4: Elevate
  99. 99. Not Started Analysis Design Program Test 20/m 10/m15/m25/m Do we need to get/pay for more “slower buffalo”? Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit Step 3: Subordinate Step 4: Elevate
  100. 100. Not Started Analysis Design Program Test 20/m 10/m15/m25/m Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit Step 3: Subordinate Step 4: Elevate bottleneck moved?
  101. 101. Not Started Analysis Design Program Test 20/m 10/m15/m25/m Be careful though: your bottleneck may move and you might miss it! You’ll need to change your exploit & subordinate rules. Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit Step 3: Subordinate Step 4: Elevate bottleneck moved?
  102. 102. Not Started Analysis Design Program Test 20/m 10/m15/m25/m 25-35% improvement in throughput. = 13/m
  103. 103. Not Started Analysis Design Program Test 20/m 10/m15/m25/m That’s like getting 4+ extra staff for free. Without working any harder. It was less stressful than normal.
  104. 104. Not Started Analysis Design Program Test 20/m 10/m15/m25/m It took: 20 minutes to figure out what to do. 1 week to “sell it” 8 months to do it.
  105. 105. Not Started Analysis Design Program Test 20/m 10/m15/m25/m
  106. 106. Not Started Analysis Design Program Test 20/m 10/m15/m25/m 8 months! Not 12.
  107. 107. - Clarke Ching “The covert enemy of productivity is trying to keep everyone busy. And yet … that is so counter-intuitive and counter-cultural it scares people.”
  108. 108. - Clarke Ching “Testing is usually the bottleneck in teams new to Agile. Usually, we want it to be development”
  109. 109. Example 2. Request: Resuscitate a project which “looks” “Agile” but isn’t producing potentially shippable code. Team of 80-100
 - mixed roles & skill- sets old ASP, old Oracle, new .net
  110. 110. slowest herd - testers fastest herd - developers
  111. 111. Same situation:Testing was the bottleneck, but developers were - obliviously - racing ahead writing “code” which wasn’t tested. slowest herd - testers fastest herd - developers
  112. 112. Same situation:Testing was the bottleneck, but developers were - obliviously - racing ahead writing “code” which wasn’t tested. slowest herd - testers fastest herd - developers
  113. 113. Same situation:Testing was the bottleneck, but developers were - obliviously - racing ahead writing “code” which wasn’t tested. We needed to get them running as 1 herd again. slowest herd - testers fastest herd - developers
  114. 114. slowest herd fastest herd
  115. 115. slowest herd fastest herd STOP
  116. 116. slowest herd fastest herd STOP SPEED-UP
  117. 117. slowest herd fastest herd STOP SPEED-UP HELP
  118. 118. slowest herd fastest herd STOP SPEED-UP HELP We’d built up too much untested code so we started a test phase.
  119. 119. slowest herd fastest herd STOP SPEED-UP HELP We’d built up too much untested code so we started a test phase.
  120. 120. slowest herd fastest herd STOP SPEED-UP HELP We’d built up too much untested code so we started a test phase. After that, we restarted development, working in small batches, learning how to deliver potentially shippable working software, with testing as our bottleneck.
  121. 121. Testing Developers
  122. 122. Testing Developers With (1) our bottleneck id’d, we kept (2) exploiting & (3) subordinating & (4) elevating.
  123. 123. Testing Developers With (1) our bottleneck id’d, we kept (2) exploiting & (3) subordinating & (4) elevating. • Recruited more/better testers • Stopping devs coding stuff that can't be tested; • More emphasis on dev testing / quality • Devs helped with some of the testing (automating stuff); • Testers prevented defects (3 amigos, etc); • Testers moved from shotgun to sniper mode; • Protecting dev & test from starvation.
  124. 124. Testing Developers With (1) our bottleneck id’d, we kept (2) exploiting & (3) subordinating & (4) elevating. Then, 18 months later - (5) our bottleneck moved into dev. • Recruited more/better testers • Stopping devs coding stuff that can't be tested; • More emphasis on dev testing / quality • Devs helped with some of the testing (automating stuff); • Testers prevented defects (3 amigos, etc); • Testers moved from shotgun to sniper mode; • Protecting dev & test from starvation.
  125. 125. Testing Developers With (1) our bottleneck id’d, we kept (2) exploiting & (3) subordinating & (4) elevating. Then, 18 months later - (5) our bottleneck moved into dev. • Recruited more/better testers • Stopping devs coding stuff that can't be tested; • More emphasis on dev testing / quality • Devs helped with some of the testing (automating stuff); • Testers prevented defects (3 amigos, etc); • Testers moved from shotgun to sniper mode; • Protecting dev & test from starvation.
  126. 126. Testing Developers With (1) our bottleneck id’d, we kept (2) exploiting & (3) subordinating & (4) elevating. Then, 18 months later - (5) our bottleneck moved into dev. • Recruited more/better testers • Stopping devs coding stuff that can't be tested; • More emphasis on dev testing / quality • Devs helped with some of the testing (automating stuff); • Testers prevented defects (3 amigos, etc); • Testers moved from shotgun to sniper mode; • Protecting dev & test from starvation.
  127. 127. Protecting the bottleneck - not just test & dev!
  128. 128. Protecting the bottleneck - not just test & dev! Buffer
  129. 129. Buffer Big project 8-10 Business Analysts Slicing & Dicing preparing a “buffer” of fuel. Protecting the bottleneck
  130. 130. Don’t let the engine run out of fuel Don’t put too much fuel in the tank Don’t put sugar in the tank Buffer Protecting the bottleneck
  131. 131. Don’t let the engine run out of fuel 1. Run at the speed of your bottleneck. 2. Plan according to your bottleneck. Don’t let the engine run out of fuel Don’t put too much fuel in the tank Don’t put sugar in the tank 3. Chose work to get the biggest “bang from your bottleneck’s buck” Protecting the bottleneck
  132. 132. Example 3. Problem: What features should we build next? Same project as before Business / Operational Bottleneck.
  133. 133. Example 3. Problem: What features should we build next? Same project as before Business / Operational Bottleneck.
  134. 134. Market demand: (from sales figures or customer’s comments) “OMG the customers won’t buy this product because the competitor has this, but we don’t” “The customers HATE This. It’s hard to use / hard to sell.”
  135. 135. Market demand: (from sales figures or customer’s comments) “OMG the customers won’t buy this product because the competitor has this, but we don’t” “The customers HATE This. It’s hard to use / hard to sell.” Capacity demand: (from analysis or looking around) “We’re selling so well but we need to Automate processes A, B and C”. “The cancellation process needs to be self- serve.” “We are selling so we need more disk space.”
  136. 136. Failure demand: - “We’re getting loads of problems with BLA … we need to fix BLA.” Market demand: (from sales figures or customer’s comments) “OMG the customers won’t buy this product because the competitor has this, but we don’t” “The customers HATE This. It’s hard to use / hard to sell.” Capacity demand: (from analysis or looking around) “We’re selling so well but we need to Automate processes A, B and C”. “The cancellation process needs to be self- serve.” “We are selling so we need more disk space.”
  137. 137. Marketing - bottleneck is lack of sales Servicing - bottleneck internal Them? - or- Them? Business - not IT
  138. 138. Marketing work to sell more? OR Servicing work to process more? Marketing - bottleneck is lack of sales Servicing - bottleneck internal Them? - or- Them? Business - not IT
  139. 139. We had an internal bottleneck. We couldn’t process everything we could sell. A wonderful problem to have! We ignored ALL marketing features (for many, many months) We 80/20’d all of the capacity related features Then worked on them according to “bang for buck”. business processes
  140. 140. Cash-Cow Buffalo
  141. 141. Example 4. Request: Build a new business from scratch. ASAP, of course. Team of 60 mixed roles & skill- sets Big clunky Vendor of a big clunky package!
  142. 142. Internal herd
  143. 143. We ensured Testing was NOT the bottleneck. Internal herd
  144. 144. We ensured Testing was NOT the bottleneck. Developers - the “strategic” bottleneck Internal herd
  145. 145. We ensured Testing was NOT the bottleneck. Developers - the “strategic” bottleneck Internal herd Testers - spare capacity, rapid response
  146. 146. We ensured Testing was NOT the bottleneck. Developers - the “strategic” bottleneck Internal herd Testers - spare capacity, rapid response Vendor - “waterfall” elephant in the room
  147. 147. We ensured Testing was NOT the bottleneck. Q: How do you eat an elephant? Developers - the “strategic” bottleneck Internal herd Testers - spare capacity, rapid response Vendor - “waterfall” elephant in the room
  148. 148. We ensured Testing was NOT the bottleneck. Q: How do you eat an elephant? A: One bite at a time. Developers - the “strategic” bottleneck Internal herd Testers - spare capacity, rapid response Vendor - “waterfall” elephant in the room
  149. 149. We ensured Testing was NOT the bottleneck. Q: How do you eat an elephant? A: One bite at a time. Q: So, how should we eat this elephant - without “going all agile on them (which they won’t do)? Developers - the “strategic” bottleneck Internal herd Testers - spare capacity, rapid response Vendor - “waterfall” elephant in the room
  150. 150. We ensured Testing was NOT the bottleneck. Q: How do you eat an elephant? A: One bite at a time. Q: So, how should we eat this elephant - without “going all agile on them (which they won’t do)? Q: One small-ish batch at a time - i.e. 4 “drops” rather than 1 Developers - the “strategic” bottleneck Internal herd Testers - spare capacity, rapid response Vendor - “waterfall” elephant in the room
  151. 151. Developers - the “strategic” bottleneck Internal herd Testers - spare capacity, rapid response Vendor - “waterfall” elephant in the room
  152. 152. Summary TOC is about focusing - finding the thing which limits - or “constrains” your system (relative to its goal). Step 1: Identify your bottleneck TOC’s 5 step recipe Step 2: Exploit Step 3: Subordinate Step 4: Elevate bottleneck moved? Agile is about delivering business improvements frequently. Keep the “herd together” by limiting WIP & building potential shippable software. Go faster by following the 5-step recipe.
  153. 153. Acknowledge scarcity. Make a “Slam dunk” START 2 3 FINISH Deliver. Benefits. Incrementally. Deliver on-time. Or early. Slice, Dice and Prioritise. Limit WIP Leverage your bottleneck. Recalibrate, Reprioritise, Repeat

×