Kanban Basics of Beginners

created byZsolt Fabókme@zsoltfabok.comtwitter: @ZsoltFabok

October 25, 2011 @evoline, Cluj Napoca, RO

kaizen WIP kaikaku flow value

stream mapping visualize work flow cycle time lead time throughput TPS build failed CFD

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

The Origin

photo: http://softwarecreation.org/2009/reliable-software-development-process-the-toyota-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/

The Traditional Way

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

Our Company Board

Visualize the Workflow

Limit the Work in Progress

Measure and Manage Flow

lead time

cycle time

working time

queued time

Now we know where we are now: visualized and measured

We want to be better (quality) and faster

Lean principles:● Respect for People, Continuous Improvement

(kaizen)

Last two Kanban principles:● make process policies explicit,

improve collaboratively

Kanban is a method for development with a set of principles! Kanban

○ doesn't exist alone○ requires an existing process

+or

or

or

Case Study I: Inefficiency and Quality Issues

... period n-1 period n Flowavg lead time 5 19 10avg waiting time 78% 92% 95%estimation precision 51% 78% 65%throughput 3/12 0/10 42/60

moving items back 3 13 26

Case Study II: SLA for Planning

photo: Digital Natives (http://digitalnatives.hu), SLA board

Finally, Our Current Board

photo: Digital Natives (http://digitalnatives.hu), playertise team Kanban board

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