Embed Size (px)
DESCRIPTION
Citation preview
1
Kanban for Sustainment projects
Sameh Zeid-- [email protected]
April 23rd, 2010-- Atlanta, GA (LSSC10)
2
Review & High-Level Design
Test & Development
QA, Build & Release
Customer request
Customer acceptance
1 Day.-Team 2 Day.-Team 1 Day.-Team
$ 1/Day-Team $ 2/Day-Team$ 2/Day-Team
1 Request/Team 1 Request/Team1 Request/Team
Cost
Duration
WIP limit/team
Sample software sustainment system
3
Situation 1
1. Arrival rate is constant = 1 Request/day2. All Requests are of Standard size3. No defect produced by any team4. Items are processed in FIFO basis5. Every team always take same duration per CR
4
Lead-Time
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 200
2
4
6
8
10
12
14
16
18
20
22
Date Request Submitted
Cycle Time
Cost per request
2 Days
$10
Throughput 50%
6
Situation 2
Exactly same rules as situation 1, we just added one more team for Test & Development stage
Cycle Time
Cost per request
1 day
$7
Throughput 100%
Lead Time 4 Days
8
Situation 3
Same rules. Size is uniformly distributed.
Tiny LargeStandard
2 Day 4 Day 8 Day
0 5 10 15 20 25 300
2
4
6
8
10
12
14
16
Tiny
0 5 10 15 20 25 300
2
4
6
8
10
12
14
16
Standard
0 5 10 15 20 25 300
2
4
6
8
10
12
14
16
Large
Date submitted
Lead
Tim
e
Size indifference
Increasing trend in Lead-Time
Conclusions
11
Sustainment center
Item size
Arrival rate
CR priority
Stage defect injection rate
Time deviation per stage
Throughput
Lead Time
Cost/ CR
Stochastic system
Cycle Time
Controlling input factors
Effect of Factors change/ interact
Simulation should be done beforehand!
Continue with normal working practice
At interval-end, collect data
Feedback for process changes
Refine the system
And possibly the agreement
Use Lean Measures for agreement setting
Not person-hours
Simulate to know from up-front how system would behave
This will reduce daily tracking overheads
Kanban is like a doctor, extensively wanted till you cure
Afterwards, Follow-ups
21
Thank you!
