Agile Evolution with Kanban
•
1 recomendación•707 vistas
Given at the BCS in Edinburgh on the 1/8/2012. Talk about change and failed attempt to introduce XP into an organisation. Suggests potential reasons for the failure, introduces Kanban and then speculates as to how change might have been more successful in an evolutionary manner with Kanban.
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (18)
Similar a Agile Evolution with Kanban
Similar a Agile Evolution with Kanban (20)
Más de Chris McDermott
Más de Chris McDermott (10)
Último
Último (20)
Agile Evolution with Kanban
- 1. Agile revolution or an agile evolution? Chris McDermott @chrisvmcd chris.v.mcdermott@gmail.com
- 4. Planning game Release planning Iterations Small releases
- 5. Planning game Release planning Iterations Small releases Common code ownership Test driven development Refactoring Emergent design Pair programming Continuous integration
- 6. Planning game Release planning Iterations Small releases Common code ownership Test driven development Refactoring Emergent design Pair programming Continuous integration Code as documentation Generalists On site customer Sustainable pace
- 7. Planning game Stand up meetings Release planning Retrospectives Iterations Small releases Common code ownership Test driven development Refactoring Emergent design Pair programming Continuous integration Code as documentation Generalists On site customer Sustainable pace
- 9. why?!
- 13. Iterations Release planning Stand up meetings Project Managers Sustainable pace Pair programming
- 14. Generalists On site customer Business Analysts Documentation light
- 15. Test driven development Sustainable pace Continuous Common code integration ownership Emergent design Developers Refactoring Pair programming On site customer Generalists
- 16. Automated testing Sustainable pace QA Generalists Documentation light
- 17. it is risky!
- 18. desired 1 2 3 4 5 Capability current Time
- 19. desired 1 2 3 4 5 Capability current organisational threshold Time
- 20. why not forget about adopting an “Agile” method?
- 21. feedback quality through craftsmanship improved lead times strive for increased culture of trust predictability agility patience
- 22. what is Kanban and how can it help? stop starting, start finishing
- 24. kanban system • WIP (Work In Progress) limited pull system.
- 25. Kanban Method • A change management system that uses kanban systems to provoke change • Catalyst for evolutionary change • Can help to create an culture of continuous improvement
- 27. Microsoft XIT Worst to Best in 9 months http://www.agilemanagement.net/AMPDFArchive/From_Worst_to_Best_in_9_Months_Final_1_3.pdf
- 28. Corbis
- 30. Principles • Start with what you do now • Agree to pursue incremental, evolutionary change • Initially, respect the current process, roles, responsibilities & job titles • Encourage leadership at all levels
- 32. Demand Analysis Development Test Released
- 33. Demand Analysis Development Test Released In
- 34. Progress Done In
- 35. Progress Done In
- 36. Progress Done
- 37. Demand Analysis Development Test Released 214*** In
- 38. Progress Done In
- 39. Progress Done In
- 40. Progress Done Task 214*** Task description description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task 214*** Task Task Task description description Task description description description **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task 214*** Task Task Task description description Task description description description **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task 214*** Task Task Task description description Task description description description **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task 214*** Task Task Task description description Task description description description **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** Task 214*** Task description Task description **/**/2011 description **/**/2011 **/**/2011 Reason
- 41. Type: Feature 2146767 Work item type Digital tracking - Bug number - Feature Ability to search by product - Non Functional - etc Cust: Chris BA: Mike Due: 09/06 Dev: Liz Start: 07/06 QA: Brian End: 08/06 Tracking dates Contacts
- 44. Limit WIP
- 45. Demand
- 46. (4) Analysis
- 47. (5) Development
- 48. (6) Test Released In
- 49. Progress Done In
- 50. Progress In
- 51. Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** Task Task Task description description description **/**/2011 **/**/2011 **/**/2011 214*** 214*** Task Task description description **/**/2011 **/**/2011
- 52. Demand
- 53. (4) Analysis
- 54. (5) Development
- 55. (6) Test Released In
- 56. Progress Done In
- 57. Progress In
- 58. Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** Task Task description description **/**/2011 **/**/2011
- 59. Demand
- 60. (4) Analysis
- 61. (5) Development
- 62. (6) Test Released In
- 63. Progress Done In
- 64. Progress In
- 65. Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** Task description **/**/2011
- 66. Demand
- 67. (4) Analysis
- 68. (5) Development
- 69. (6) Test Released In
- 70. Progress Done In
- 71. Progress In
- 72. Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** 214*** Task 214*** Task Task Task description Task description description description **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011
- 73. Demand
- 74. (4) Analysis
- 75. (5) Development
- 76. (6) Test Released In
- 77. Progress Done In
- 78. Progress In
- 79. Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** Task 214*** Task Task description Task description description **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011
- 80. Manage Flow
- 81. Demand
- 82. (4) Analysis
- 83. (5) Development
- 84. (6) Test Released In
- 85. Progress Done In
- 86. Progress In
- 87. Progress Done Done 214*** 214*** Task Task description (2) description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task Task description description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task Task description description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Lead Time
- 91. Make process policies explicit
- 92. Demand
- 93. (4) Analysis
- 94. (5) Development
- 95. (6) Test Released In
- 96. Progress Done In
- 97. Progress In
- 98. Progress Done Done 214*** 214*** Task Task description (2) description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task Task description description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task Task description description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Definition of Done: Definition of Done: Definition of Done: • Goal is clear • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
- 99. Implement feedback loops
- 101. Improve collaboratively (using models the scientific method)
- 102. Demand
- 103. (4) Analysis
- 104. (5) Development
- 105. (6) Test Released In
- 106. Progress Done In
- 107. Progress In
- 108. Progress Done Done 214*** Task description (2) **/**/2011 214*** 214*** 214*** Task Task Task description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** Task Task Task description description description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** Task Task Task description description description **/**/2011 **/**/2011 **/**/2011 214*** 214*** Task Task description description **/**/2011 **/**/2011 214*** 214*** Task Task description description **/**/2011 **/**/2011 **/**/2011 Definition of Done: Definition of Done: Definition of Done: • Goal is clear • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
- 109. Demand
- 110. (4) Analysis
- 111. (5) Development
- 112. (6) Test Released In
- 113. Progress Done In
- 114. Progress In
- 115. Progress Done Done 214*** Task description (2) **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** Task description **/**/2011 214*** Task description **/**/2011 Definition of Done: Definition of Done: Definition of Done: • Goal is clear • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
- 116. Demand
- 117. (4) Analysis
- 118. (5) Development
- 119. (6) Test Released In
- 120. Progress Done In
- 121. Progress In
- 122. Progress Done Done 214*** Task description (2) **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** Task description **/**/2011 214*** Task Failure Demand description **/**/2011 Definition of Done: Definition of Done: Definition of Done: • Goal is clear • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
- 123. Demand
- 124. (4) Analysis
- 125. (5) Development
- 126. (6) Test Released In
- 127. Progress Done In
- 128. Progress In
- 129. Progress Done Done 214*** Task description (2) **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** Task description **/**/2011 214*** Task Failure Demand description **/**/2011 Definition of Done: • Goal is clear Transaction Cost Definition of Done: Definition of Done: • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
- 130. Improvements Visualise Feedback Limit Loops WIP Explicit Policies Manage Flow
- 131. Improvements Visualise Feedback Limit Loops WIP Explicit Policies Manage Flow
- 132. what if?
- 134. LT C U GO Y A R O R C C IS ECIFI V SP A D XT NTE C O
- 136. Input Analysis Dev Build Test UAT Signed
- 137. Off Doing Done Doing Done Doing Done
- 138. Input Analysis Dev Build Test UAT Signed
- 139. Off Doing Done Doing Done Doing Done 214*** Task description **/**/ 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** Task Task Task description description description **/**/ **/**/ **/**/ 214*** 214*** Task description Task **/**/ description **/**/ 214*** Task 214*** description Task **/**/ description **/**/ 214*** Task description **/**/ 214*** Task description **/**/
- 140. Input Analysis Dev Build Test UAT Signed
Notas del editor
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- We don’t have this landscape on most software development projects/teams etc\n
- We don’t have this landscape on most software development projects/teams etc\n
- \n
- \n
- \n
- \n
- \n
- \n
- 1. current\n2. abyss\n3. valley\n4. ascent\n5. mountaintop\n
- \n
- \n
- \n
- Karl Scotland\n
- - Invented by Ohno in the early 50’s after studying supermarkets\n - uses the rate of demand to control the rate of production\n
- set of techniques and practices used to provoke and help manage change\nno such thing as: \n - the Kanban Software Development Process \n - or the Kanban Project Management Method. \n
- Background\nReason for Kanban\n
- Changed the way the work works\n
- \n
- \n
- does not prescribe a specific set of roles or process. \n\n\n\n
- \n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- Card content\nStand Ups\n\n
- \n
- \n
- \n
- \n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
- \n
- flow should be monitored, measured and reported\nchange can be evaluated\n
- SPC - Variation in lead time\nCFD - Check that the Kanban System is working correctly\n
- SPC - Variation in lead time\nCFD - Check that the Kanban System is working correctly\n
- \n
- - hard to discuss improvement if the system is not understood\n - with explicit policies discussions are emotional and anecdotal \n - facilitate consensus around improvement suggestions\n - Leads to a self organising team\n
- \n
- \n
- \n
- \n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
- \n\n\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n\n\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n\n\n
- \n
- \n
- \n
- \n
- \n\n\n
- \n
- \n
- \n
- \n
- 1. current\n2. abyss\n3. valley\n4. ascent\n5. mountaintop\n
- \n