Case studies: Kanban at personal, software, non software and portfolio level - Jan De Baere As project management office in a large and traditional Belgium company we promote - unofficaly - agility in the company. One of the things is that we started to use kanban/visual management. It starts with a quick overview of kanban so everybody should be able to follow. Main thing is to show real live examples: - Three maintenance teams - Two non software teams - Personal - Portfolio level (200+ projects) As well in the maintenance teams as in the non software teams we have distributed team. As side information on the portfolio level topic you'll also receive an idea on how we included agile in our project management method.

1. Kanban @ different levels
Jan De Baere
Baere@aalst.com
2012 Octobre

2. ?
2

3. Kanban
3

4. Feedback after 3 weeks
SDM:
“Now I have better insight: e.g. “work done” and “work to be done”,
number of high priority issues, number of issues we wait for input…”
“team has better time management and works in a more structured
way without I have to do something more”
“after having tried several systems with several service teams in
different environments it strikes me that the whole team just used
Kanban without me having to do something”
“If have something to say…”

5. Kanban: applied lean principles
Kanban
•Visualize workflow
•Limit work in progress
•Measure and Manage flow
•Make process Policies Explicit
5 •Use Models to 07 2008
00 improve

7. Changes

8. Process

9. Backlog: ToDo

10. One task
Color indicates who

11. High priority issues

12. Waiting for: business, other teams…

13. KIR

14. limited set
of
clear rules

15. November 2011

16. March 2012

17. April 2012

18. Analyse

19. Analyse

20. March 2012

21. March 2012

22. Cumulative Flow diagram
50
45
40
35
30
25
Backlog
20
15
10
5
0
23/05/2011 23/06/2011 23/07/2011 23/08/2011 23/09/2011 23/10/2011 23/11/2011 23/12/2011
22 00 07 2008

23. Cumulative Flow diagram
50
45
40
35
30
25 Backlog
RTS
20
15
10
5
0
23/05/2011 23/06/2011 23/07/2011 23/08/2011 23/09/2011 23/10/2011 23/11/2011 23/12/2011
23 00 07 2008

24. 50
Cumulative Flow diagram
45
40
35
30
Backlog
25
RTS
20 Done
15
10
5
0
23/05/2011 23/06/2011 23/07/2011 23/08/2011 23/09/2011 23/10/2011 23/11/2011 23/12/2011
24 00 07 2008

25. 50
Cumulative Flow diagram
45
40
35
30
creation date
25
actual start date
20 actual end date
15
10
WIP
5
0
23/05/2011 23/06/2011 23/07/2011 23/08/2011 23/09/2011 23/10/2011 23/11/2011 23/12/2011
25 00 07 2008

26. 50
Cumulative Flow diagram
45
40
35
30
creation date
25
actual start date
20 actual end date
15
10
Average lead time
5
0
23/05/2011 23/06/2011 23/07/2011 23/08/2011 23/09/2011 23/10/2011 23/11/2011 23/12/2011
26 00 07 2008

27. Cumulative Flow diagram
27 00 07 2008

28. Cumulative Flow diagram
28 00 07 2008

29. Daily stand up
Introduction of Kanban teams
29

30. MAINTENANCE TEAMS
Frequency: Daily
05/05/09 www.agiletour.com

31. Different well organized channels with tools
support…
31

32. Small team
32

33. Distributed teams
Introduction of Kanban teams
33

34. NON SOFTWARE TEAMS
Frequency: Weekly
05/05/09 www.agiletour.com

35. Our team objectives: non development
Team: co-located
Frequency: Weekly meeting
Size: 4 people

36. Non development: Our team tasks
Focus on non recurring tasks

37. Team: Distributed
Frequency: Weekly meeting
Size: 7 people
37

38. INDIVIDUAL LEVEL
Personal kanban
05/05/09 www.agiletour.com

39. Example Personal Kanban
Frequency: per task
Size: 1 39

40. PORTFOLIO LEVEL
05/05/09 www.agiletour.com

41. Two layers: the framework
4
1

42. Two layers: implementation
4
2

43. Single track projects
PMG Classic => 1 classic track
Define Design Build implement Close
PMG Agile => 1 Agile track
Define Close
PMG Light=> 1 Light track
Define Light/No development Close
43

44. Multitrack: Possibility to combine types of tracks
Define Close
Design Build implement
Light development
Light development
Example
44

45. Overview of projects.
Team: Distributed
Frequency: Monthly
Size: company wide
45

46. PROGRAM LEVEL
Visual management
05/05/09 www.agiletour.com

47. Team: Distributed
Frequency: Weekly
Size: 7 PM

48. Positieve vs Negative feedback Remarkable
28%
Positive points
Negative points
72%

49. ?
4
9

50. Cumulative Flow diagram
Spectrum analysis of lead time (working days)
60
50
40
30
20
10
0
1 4 7 10 13 16 19 22 25 28 31 34 37 40 43 46 49 52 55 58 61 64 67 70 73 76 79 82 85 88 91 94 97 100
50 00 07 2008