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.

1. What can traffic inteach you aboutqueuingtheory Håkan Forss - hakan.forss@avegagroup.se - @hakanforss

2. Håkan Forss Lean/Agile Coach Håkan Forss - hakan.forss@avegagroup.se - @hakanforss

7. Little’s Law Work-in-Process Throughput Cycle Time =

8. Little’s Law 12 12 / min 1 min =

9. Little’s Law 6 12 / min 0,5 min=

10. Little’s Law 24 12 / min 2 min =

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

12. TheoryofConstraints

15. 5

16. Don’t allow inertia to cause a system constraint.

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

22. Don’t allow inertia to cause a system constraint.

26. Bottleneck at the end of the process Work is backing up Slowing down the process Cycle times goes up

28. Bottleneck at the beginning/middle of the process Work is drying up at the end of the processmaking workers idle

31. ?

33. Non-instant availability resource Looks like a bottleneck

34. Non-instant availability resource A resource that is not available all the time Has required capacity but is not instantly available

37. Don’t allow inertia to cause a system constraint.

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

39. Don’t allow inertia to cause a system constraint.

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

43. Don’t allow inertia to cause a system constraint.

45. Elevate your bottleneck Expand the capacity at the bottleneck Expensive as it usually will use bottleneck resources

46. Don’t allow inertia to cause a system constraint.

48. Don’t allow inertia to cause a system constraint.

49. Balance demand to flow

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

51. Onlyonevehicleevery green period

52. Balance demand to flow An even flow can stabilize the process Low work-in-progress Keeps cycle time down Makes bottlenecks visible faster

54. Slow down to go faster Slowing down can stabilize the process flow A stable process can go faster

57. Håkan Forss Mail: hakan.forss@avegagroup.se Twitter: @hakanforss Blog: http://hakanforss.wordpress.com/

58. Recommended reading Håkan Forss - hakan.forss@avegagroup.se - @hakanforss