Kanban for Sustainment projects<br />April 23rd, 2010-- Atlanta, GA (LSSC10)<br />Sameh Zeid-- sameh@koo-doy.com<br />1<br />
Sample software sustainment system<br />Customer request<br />Customer acceptance<br />Review & High-Level Design<br />Tes...
Situation 1<br />Arrival rate is constant = 1 Request/day<br />All Requests are of Standard size<br />No defect produced b...
4<br />Lead-Time<br />Date Request Submitted<br />
2 Days<br />Cycle Time<br />$10<br />Cost per request<br />50%<br />Throughput<br />
Situation 2<br />Exactly same rules as situation 1, we just added one more team for Test & Development stage<br />6<br />
4 Days<br />Lead Time<br />1 day<br />Cycle Time<br />$7<br />Cost per request<br />100%<br />Throughput<br />
Situation 3<br />Same rules. Size is uniformly distributed. <br />Large<br />Standard<br />Tiny<br />2 Day<br />4 Day<br /...
Lead Time<br />Date submitted<br />
Size indifference<br />Increasing trend in Lead-Time <br />Conclusions<br />
Stochastic system<br />Sustainment center<br />Item size<br />Throughput<br />Arrival rate<br />CR priority<br />Lead Time...
Controlling input factors<br />Effect of Factors change/ interact<br />
Simulation should be done beforehand!<br />
Continue with normal working practice<br />
At interval-end, collect data<br />Feedback for process changes<br />
Refine the system<br />And possibly the agreement<br />
Use Lean Measures for agreement setting<br />Not person-hours<br />
Simulate to know from up-front how system would behave<br />
This will reduce daily tracking overheads<br />
Kanban is like a doctor, extensively wanted till you cure<br />Afterwards, Follow-ups<br />
Thank you!<br />21<br />
Upcoming SlideShare
Loading in...5
×

Kanban for sustainment lssc10

515

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
515
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Kanban for sustainment lssc10

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

    Clipping is a handy way to collect important slides you want to go back to later.

×