Kanban is a lean methodology for managing workflow and limiting work-in-progress. The document discusses how Kanban was implemented at a company to visualize their workflow, limit work-in-progress, and measure cycle times. This resulted in decreased cycle times by 80%, increased throughput by over 5 times, and a predictability rate of 80%. Kanban also led to a more committed and satisfied self-organizing team as well as satisfied clients.

1. KANBAN AN EFFECTIVE
IT CHANGE MANAGEMENT APPROACH
p e n t a l o g . c om

2. AGENDA
What is Kanban?
Why to Kanban?
How to deploy it?
What were the results?
10 different kanbans
Q&A
SEPTEMBER 2012 pentalog.com 2

3. WHY THIS TOPIC? KANBAN
Small changes=>Huge business value
SEPTEMBER 2012 pentalog.com 3

4. KANBAN IN A NUTSHELL
Less prescriptible Agile framework
Visualize the workflow
Limit Work In Progress
Manage Flow
Make process policies more explicit
Improve collaboratively
SEPTEMBER 2012 pentalog.com 4

5. VISUALIZE THE FLOW
SEPTEMBER 2012 pentalog.com 5

6. LIMIT WIP
SEPTEMBER 2012 pentalog.com 6

7. MEASURE CYCLE TIME
SEPTEMBER 2012 pentalog.com 7

8. CUMULATIVE FLOW
SEPTEMBER 2012 pentalog.com 8

9. CUMULATIVE FLOW
SEPTEMBER 2012 pentalog.com 9

10. WHY TO KANBAN?
Remove Muri (work overflow)
Decrease Mura (work debit & variations)
SEPTEMBER 2012 pentalog.com 10

11. WHY PROJECT FAILS?
KPMG
SEPTEMBER 2012 pentalog.com 11

12. WHY PROJECT FAILS?
KPMG
SEPTEMBER 2012 pentalog.com 12

13. NEGATIVE RESPONSE TO CHANGE
SEPTEMBER 2012 pentalog.com 13

14. WHY TO KANBAN?
Less resistance to change
People appreciate it as a tool for supporting them
SEPTEMBER 2012 pentalog.com 14

15. HOW TO DEPLOY IT?
In an existing organization
Step 1 : visualize/analyze the flow, build a
Value Stream Map, build kanban board
Step 2 : create a pull system
Step 3 : regulate the volume of cards, based on team’s capacity and
multi-tasking limits
In a new organization
Step 1 : just start with a new kanban board and 3 stages (To do, WIP,
Done)=>adjust afterwards
SEPTEMBER 2012 pentalog.com 15

16. VALUE STREAM MAP
SEPTEMBER 2012 pentalog.com 16

17. HOW TO DEPLOY IT?
Focus on facts
Rely your changes on reality, start with an audit, a data collection
phase...=>analyzes
Focus on the work people perform and how the perform
Don't focus on people, culture, environment... (avoid mixing causes
with results)
SEPTEMBER 2012 pentalog.com 17

18. HOW TO DEPLOY IT?
Agile is more about values than rules
Commitment
Openness
Focus
Respect
Courage
sounds familiar (Agile Scrum)?
SEPTEMBER 2012 pentalog.com 18

19. HOW TO DEPLOY IT?
Kanban requires an agile mindset!
Kanban rules are not sufficient, you should add your own rules
- Daily kanban Stand-up
- Retrospectives
- Build an event driven environment
SEPTEMBER 2012 pentalog.com 19

20. LEAN THINKING
SEPTEMBER 2012 pentalog.com 20

21. GALBRAITH'S START MODEL
SEPTEMBER 2012 pentalog.com 21

22. THEORY X
SEPTEMBER 2012 pentalog.com 22

23. THEORY Y
SEPTEMBER 2012 pentalog.com 23

24. SMALLER WORK ITEMS
SEPTEMBER 2012 pentalog.com 24

25. YERKES-DODSON HUMAN
PERFORMANCE CURVE
SEPTEMBER 2012 pentalog.com 25

26. KANBAN KICK-START EXAMPLE
SEPTEMBER 2012 pentalog.com 26

27. WHAT WERE THE RESULTS?
In the books
decreases the cycle time by 92%
increases the throughput by more than 3 times
approaches a very acceptable predictability rate of 98%
SEPTEMBER 2012 pentalog.com 27

28. IN REALITY – CLIENT FEEDBACK
SEPTEMBER 2012 pentalog.com 28

29. IN REALITY – SUSTAINABLE PACE
SEPTEMBER 2012 pentalog.com 29

30. WHAT WERE THE RESULTS?
In reality in my team
decreases the cycle time by 80%
increases the throughput by more than 5 times
approaches a very acceptable predictability rate of 80%
SEPTEMBER 2012 pentalog.com 30

31. WHAT WERE THE RESULTS?
In reality in my team (other kind of benefits)
committed and satisfied self-organizing team
very satisfied clients (80% of their feedback is “Good” or “Perfect”,
while 15% is “Ok, but we can improve)”!
secondary products emerged from the organization
SEPTEMBER 2012 pentalog.com 31

32. 10 DIFFERENT KANBANS
Document from infoQ
SEPTEMBER 2012 pentalog.com 32

33. Q&A
SEPTEMBER 2012 pentalog.com 33

34. THANK YOU!
p e n t a l o g . c om

35. SEPTEMBER 2012 pentalog.com 35