This document provides a high-level overview of Kanban in 3 sentences or less: Kanban is a method for managing and improving workflows through visualizing and measuring flow, limiting work-in-progress, and making process policies explicit. The core principles of Kanban involve visualizing the workflow, measuring and managing flow, and continuously improving the process collaboratively using models and the scientific method. The goal of Kanban is to find and reduce waiting time and repetition in order to improve productivity and throughput.

1. Kanban in 5 minutes
measure and manage flow
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)
August 3, 2011 @
Bp New Tech Meetup

2. Before saying anything:
"I promise not to exclude from consideration any idea based on its source,
but to consider ideas across schools and heritages in order to find the
ones that best suit the current situation." [1]
This means the end of statements like “That’s no good – it’s not
agile / object-oriented / pure / etc…”, but rather a discussion
about whether an idea (agile or plan-driven or impure or
whatever) works well in the conditions of the moment.

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

4. The core principles of Kanban
visualize the
workflow measure
and manage flow improve
collaboratively (using models & the
limit the
scientific method)
work in progress (WIP)
make process policies explicit

5. The feedback is the key for better
products, not the method...
...more precisely: faster feedback

6. Measure and manage flow
Spent time
+ or
Age
waiting
effective work
cycle time (repetition!)
lead time

7. The goal is...
...to find the reason behind ...and to reduce and/or
waiting and repetition... manage it
hamster effect wrong * delivery cadence Little's law
prioritisation weekend rush batching cost of delay
defects slow builds manual prioritisation MMF task oriented
builds dependencies late
dynamic
daily stand up
integration no
prioritisation mark
cadence context
ageing service level agreement
switching changing
avatars explicit definition of
missing
requirements
done criteria
delivery strategy
* smaller fonts indicate common or
already discussed issues

8. Thank you very much for your attention!
For more Kanban-related topics, check out my website:
http://zsoltfabok.com/
or follow me on twitter:
@ZsoltFabok

9. Related articles:
● http://www.zsoltfabok.com/blog/2011/06/kanban-basics/
● http://www.zsoltfabok.com/blog/2011/07/physical-and-electronic-boards/
● http://www.zsoltfabok.com/blog/2010/06/more-kanban-numbers/
● http://www.zsoltfabok.com/blog/2010/09/never-move-items-back/
● http://www.zsoltfabok.com/blog/2010/09/ageing-items-on-the-board/
● http://www.zsoltfabok.com/blog/2010/12/daily-stand-up-variations/
● http://www.zsoltfabok.com/blog/2011/01/visualize-wf-dod/