Kanban for sustainment lssc10

Kanban for Sustainment projects
April 23rd, 2010-- Atlanta, GA (LSSC10)
Sameh Zeid-- sameh@koo-doy.com
1

Sample software sustainment system
Customer request
Customer acceptance
Review & High-Level Design
Test & Development
QA, Build & Release
1 Day.-Team
2Day.-Team
1 Day.-Team
2
Duration
$ 1/Day-Team
$ 2/Day-Team
$ 2/Day-Team
Cost
1 Request/Team
1 Request/Team
1 Request/Team
WIP limit/team

Situation 1
Arrival rate is constant = 1 Request/day
All Requests are of Standard size
No defect produced by any team
Items are processed in FIFO basis
Every team always take same duration per CR
3

4
Lead-Time
Date Request Submitted

2 Days
Cycle Time
$10
Cost per request
50%
Throughput

Situation 2
Exactly same rules as situation 1, we just added one more team for Test & Development stage
6

4 Days
Lead Time
1 day
Cycle Time
$7
Cost per request
100%
Throughput

Situation 3
Same rules. Size is uniformly distributed.
Large
Standard
Tiny
2 Day
4 Day
8 Day
8

Lead Time
Date submitted

Size indifference
Increasing trend in Lead-Time
Conclusions

Stochastic system
Sustainment center
Item size
Throughput
Arrival rate
CR priority
Lead Time
Stage defect injection rate
Cost/ CR
Time deviation per stage
11
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

Thank you!
21

Kanban for sustainment lssc10

by samehsz on Apr 29, 2010

Accessibility

Tags

Upload Details

Usage Rights

1 Embed 5

Statistics

Kanban for sustainment lssc10 — Presentation Transcript