Kanban and visual management at different levels
50
-
Upload
jan-de-baere -
Category
Business
-
view
575 -
download
1
description
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.
Transcript of Kanban and visual management at different levels
2
?
3
Kanban
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…”
500 07 2008
Kanban
• Visualize workflow• Limit work in progress• Measure and Manage flow• Make process Policies Explicit• Use Models to improve
Kanban: applied lean principles
Changes
Process
Backlog: ToDo
One taskColor indicates who
High priority issues
Waiting for: business, other teams…
KIR
limited set of
clear rules
November 2011
March 2012
April 2012
Analyse
Analyse
March 2012
March 2012
2200 07 2008
Cumulative Flow diagram
0
5
10
15
20
25
30
35
40
45
50
Backlog
2300 07 2008
Cumulative Flow diagram
0
5
10
15
20
25
30
35
40
45
50
BacklogRTS
2400 07 2008
Cumulative Flow diagram
0
5
10
15
20
25
30
35
40
45
50
BacklogRTSDone
2500 07 2008
Cumulative Flow diagram
0
5
10
15
20
25
30
35
40
45
50
creation dateactual start dateactual end date
WIP
2600 07 2008
Cumulative Flow diagram
0
5
10
15
20
25
30
35
40
45
50
creation dateactual start dateactual end date
Average lead time
2700 07 2008
Cumulative Flow diagram
2800 07 2008
Cumulative Flow diagram
29
Introduction of Kanban teams
Daily stand up
MAINTENANCE TEAMS
Frequency: Daily
www.agiletour.com05/05/09
31
Different well organized channels with tools support…
32
Small team
33
Introduction of Kanban teams
Distributed teams
NON SOFTWARE TEAMS
Frequency: Weekly
www.agiletour.com05/05/09
Our team objectives: non development
Team: co-locatedFrequency: Weekly meetingSize: 4 people
Non development: Our team tasks
Focus on non recurring tasks
37
Team: DistributedFrequency: Weekly meetingSize: 7 people
INDIVIDUAL LEVEL
Personal kanban
www.agiletour.com05/05/09
39
Example Personal Kanban
Frequency: per taskSize: 1
PORTFOLIO LEVEL
www.agiletour.com05/05/09
Two layers: the framework
41
Two layers: implementation
42
43
Single track projects
Define
Close
PMG Classic => 1 classic track
Define
PMG Agile => 1 Agile track
Close
Define
PMG Light=> 1 Light track
Light/No developmentClos
e
Design Build implement
44
Multitrack: Possibility to combine types of tracks
Design Build implement
Define
Close
Light development
Light development
Example
45
Overview of projects.
Team: DistributedFrequency: MonthlySize: company wide
PROGRAM LEVEL
Visual management
www.agiletour.com05/05/09
Team: DistributedFrequency: Weekly
Size: 7 PM
Remarkable
72%
28%
Positieve vs Negative feedback
Positive pointsNegative points
49
?
5000 07 2008
Cumulative Flow diagram
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
0
10
20
30
40
50
60
Spectrum analysis of lead time (working days)
