A survey of Kanban, a software development practice, its history, why people are using it, how to start using it, why it works, criticisms of it, advanced techniques, some general advice and a selected set of references,
14. How to do it the first time Copyright (c) Norbert Winklareth Flow: from Engineering Release to Production Model & Visual Control WIP Limits Pull
15.
16.
17.
18.
19. Why it works Copyright (c) Norbert Winklareth Tasks to be done. Active Tasks (WIP) Completed Tasks, (the purpose of the system is to complete as many of these as possible per unit of time) Lead Time Cycle Time (CT) Product Development is Queuing System and it works independent of iterations Little’s Law applies and it says LT = WIP / CT Easiest way to reduce LT is to reduce number of Active Tasks, which improves Total Lead Time
This is meant to be a overview of what Kanban software development practice is, where it came from, why people are using it, some of the more advanced practices and where to get more information on it. Will not compare it to others, this is meant to give you enough material to know if you want to add it to bag of tools. Discussions about it versus others are for the pub afterwards. I am known for having wordy and dense presentations and I do this so that you can follow it later. I will be making the presentation available.