In this session you will learn about queuing theory and Theory of Constrains. By using real world examples of different traffic situations in Stockholm, illustrations and examples from Kanban boards you will see the similarities between them. You will lean how you can apply Theory of Constrains to find the bottleneck in your development process and how you can use this to continuously improve your development process.
This session is adding more details about Theory of Constrains than previous talks on this subject.
11. 20 sec 40 sec With less Work-In-Process Shorter cycle time Better time to market Faster feedback Makes problems visible faster Are we working on the right things
19. Capacity = 4 Capacity = 6 Capacity = 6 Throughput = 4 You can never go faster than your bottleneck The capacity at the bottleneck will dictate the capacity of the complete process
20. Capacity = 4 Capacity >= 4 Capacity = 6 Throughput = 4 You can never go faster than your bottleneck As long as capacity in front of the bottleneck is equal to or grater than the bottleneck you will go as fast as your bottleneck Full use of a higher capacity in front of the bottleneck will make cycle time go up
21. Capacity = 4 Capacity = 6 Capacity >= 4 Throughput = 4 You can never go faster than your bottleneck As long as capacity is equal to or greater after the bottleneck you will go as fast as your bottleneck Higher capacity after the bottleneck than at the bottleneck will not improve throughput over time
38. Exploit your bottleneck Bottlenecks should only work on bottleneck activities Do whatever you can to make your bottleneck 100% utilized Try your hardest to avoid problems at you bottleneck Time lost at the bottleneck is time forever lost for the process
41. Subordinate to your bottleneck Do what you can to always have work for the bottleneck Do what you can to avoid passing defects on to the bottleneck Sub optimal performance for non bottlenecks can be accepted
42. Subordinate to your bottleneck Try to use you over capacity to alleviate the bottleneck of non bottleneck work Sub optimal performance for non bottlenecks can be accepted
50. Wishful thinking Capacity = 4 Demand = 6 Balance demand to flow Capacity at the bottleneck will dictate the capacity of the process Balance your demand to a continuous flow through the bottleneck Higher demand than capacity will increase cycle time
Every process has at least oneOne is always a number oneWhen you break it number two will take it’s place
Identify the constraint
Very busy, all the timeWork piles up in front of themPeople downstream idle
There are two different types of bottlenecks: - Capacity contraint resource - a resource limited by capacity, like a bottle - non instantly available resource - a resource that is not available all the time
There are two different types of bottlenecks: - Capacity contraint resource - a resource limited by capacity, like a bottle - non instantly available resource - a resource that is not available all the time
Exploit the constraint
No task switchingNo idle timeOnly work on highest priority itemsOnly value-adding workNo wasted effortBest working conditions.
Subordinate to the constraint
Only high quality inputDon’twastevaluecreated by bottleneckDrum-buffer-ropeSubordinates need slackShare work.
Training and toolsCoaching and mentoringTeam retrospectivesIndividual improvementWorkspaceimprovementProcess improvementPairingMore resources