1. Kanban Basics of Beginners
kaizen WIP kaikaku flow value
stream mapping visualize
work flow cycle
time lead time throughput
TPS build failed CFD
created by
Zsolt Fabók
me@zsoltfabok.com October 25, 2011 @
twitter: @ZsoltFabok evoline, Cluj Napoca, RO

2. reference: http://alistair.cockburn.us/Oath+of+Non-Allegiance

3. The Origin
photo: http://softwarecreation.org/2009/reliable-software-development-process-the-toyota-way/

4. The Traditional Way
photo: http://blog.jonasbandi.net/2009/09/passionate-developer-i-do-like-my.html
http://thepaisano.wordpress.com/2008/03/03/free-microsoft-project-clone/

5. Our Company Board
photo: Digital Natives (http://digitalnatives.hu), Company wide Kanban Board

6. Visualize the Workflow

7. Limit the Work in Progress

8. Measure and Manage Flow
working time
cycle time queued time
lead time

9. Now we know where we are now: visualized and measured
Lean principles:
● Respect for People, Continuous Improvement
(kaizen)
Last two Kanban principles:
● make process policies explicit,
improve collaboratively
We want to be better (quality) and faster

10. Kanban is a method for development with a
set of principles! Kanban
○ doesn't exist alone
○ requires an existing process
or
or
+ or

11. Case Study I: Inefficiency and Quality Issues
... period n-1 period n Flow
avg lead time 5 19 10
avg waiting time 78% 92% 95%
estimation precision 51% 78% 65%
throughput 3/12 0/10 42/60
moving items back 3 13 26

12. Case Study II: SLA for Planning
photo: Digital Natives (http://digitalnatives.hu), SLA board

13. Finally, Our Current Board
photo: Digital Natives (http://digitalnatives.hu), playertise team Kanban board

14. Thank you very much for your attention!
For more check out my
website:
http://zsoltfabok.com/
or follow me on RSS:
http://www.zsoltfabok.com/
blog/?feed=rss2
and Twitter:
@ZsoltFabok