Kanban Basics of Beginners                           kaizen WIP kaikaku flow value                           stream mappin...
reference: http://alistair.cockburn.us/Oath+of+Non-Allegiance
The Originphoto: http://softwarecreation.org/2009/reliable-software-development-process-the-toyota-way/
The Traditional Wayphoto: http://blog.jonasbandi.net/2009/09/passionate-developer-i-do-like-my.html       http://thepaisan...
Our Company Boardphoto: Digital Natives (http://digitalnatives.hu), Company wide Kanban Board
Visualize the Workflow
Limit the Work in Progress
Measure and Manage Flow        working timecycle time     queued timelead time
Now we know where we are now: visualized and measuredLean principles: ● Respect for People, Continuous Improvement   (kaiz...
Kanban is a method for development with a        set of principles! Kanban   ○ doesnt exist alone   ○ requires an existing...
Case Study I: Inefficiency and Quality Issues                       ...   period n-1   period n    Flowavg lead time      ...
Case Study II: SLA for Planningphoto: Digital Natives (http://digitalnatives.hu), SLA board
Finally, Our Current Boardphoto: Digital Natives (http://digitalnatives.hu), playertise team Kanban board
Thank you very much for your attention!                  For more check out my                  website:                  ...
Upcoming SlideShare
Loading in …5
×

Kanban Basics for Beginners Revised

1,989 views

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,989
On SlideShare
0
From Embeds
0
Number of Embeds
446
Actions
Shares
0
Downloads
35
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Kanban Basics for Beginners Revised

  1. 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. 2. reference: http://alistair.cockburn.us/Oath+of+Non-Allegiance
  3. 3. The Originphoto: http://softwarecreation.org/2009/reliable-software-development-process-the-toyota-way/
  4. 4. The Traditional Wayphoto: 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. 5. Our Company Boardphoto: Digital Natives (http://digitalnatives.hu), Company wide Kanban Board
  6. 6. Visualize the Workflow
  7. 7. Limit the Work in Progress
  8. 8. Measure and Manage Flow working timecycle time queued timelead time
  9. 9. Now we know where we are now: visualized and measuredLean 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. 10. Kanban is a method for development with a set of principles! Kanban ○ doesnt exist alone ○ requires an existing process or or + or
  11. 11. 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/60moving items back 3 13 26
  12. 12. Case Study II: SLA for Planningphoto: Digital Natives (http://digitalnatives.hu), SLA board
  13. 13. Finally, Our Current Boardphoto: Digital Natives (http://digitalnatives.hu), playertise team Kanban board
  14. 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

×