This document discusses Kanban, a lean methodology for managing workflow. It begins by explaining that the goal is to solve problems, not to focus on specific practices like Scrum or Agile. Kanban uses visual cues and limits on work-in-progress to manage flow and improve processes over time using feedback. The origins of Kanban in Toyota's manufacturing "pull system" are described. Key Kanban principles are outlined as starting with the current process and pursuing incremental change. An example of applying Kanban to a pizza restaurant workflow is provided to illustrate concepts like lead time, cycle time, and cumulative flow diagrams.

1. Kanban
by Klaas Ardinois
Ardonio Ltd.

2. @DonArdonio
klaas@ardonio.com
www.ardonio.com

3. Me = You + 10 years

5. Why are we here?

6. Usual answers
•
To apply a trade and
take pride in the result
•
To deliver with the team
•
To earn a living

7. NOT to “do agile/scrum/
kanban/prince2/…”

8. So why bother?
Isn’t it waste?

9. We’re solving problems
•
IT = usually complex
•
Complex!
Complicated!
Need for emergent
practices
•
a tool, not a goal!
Probe - Sense - Sense - Analyze
Respond
- Respond
Chaos!
act - sense respond
Simple!
Sense Categorize Respond

10. “kanban is something you strive to get rid of,
not to be proud of”
The Toyota way

11. The origin of Kanban
•
Toyota & W.E. Deming (manufacturing)
•
•
Theory of constraints
•
•
Pull System / JIT
Drum-Buffer-Rope
David Anderson (software)

12. 4 Principles
1. Start with what you know
2. Agree to pursue incremental change
3. Respect the current process, roles, titles
4. Leadership at all levels

13. Implementing KanBan
1. Visualize flow
2. Limit work in progress (WIP)
3. Manage flow
4. Make policies explicit
5. Feedback loops
6. Improve

14. Your turn!
“Pizza makes everything better” - Katy Perry

15. Donio’s Pizza
Order In
Roll Dough
Add
Toppings
∞
2
2
Bake
Serve
4
6
optimal throughput for
oven
Apply quality measures and change based on
feedback

16. Donio’s Pizza
Order In
Roll Dough
Add
Toppings
Bake
LEAD TIME
CYCLE TIME
Control charts —> SLA
Serve

17. Cumulative flow Diagram

18. Think about…
•
Cumulative flow diagrams, lead & cycle time
•
•
•
In scrum
In waterfall projects
Flow in
•
Starbucks (+ what happens if a queu forms)
•
McDonalds

19. One does not simply
say thank you without meme

20. Pro Tips!
(free stuff! not part of the lecture)

21. When I hire…
•
Theoretical background
•
How you think
•
Curiosity
•
Skill

22. Being a developer…
•
write code!
•
Don’t be a one trick pony
•
Know what you don’t know
•
Study theory and practice

23. Quality?
•
jquery.js or jquery.min.js
•
switching values of 2 int vars with or without
temp var
•
html source of google.com

24. Quality!
•
A measure of “good”
•
•
Subjective & Relative
Different perspectives
•
coder, compiler, user, …