Introduction to Kanban Steven Borg, Northwest Cadence Co-founder and Strategist AAP204
US Team 10 developers 23 projects 6-8 projects per person But one dev working 16 projects, all with weekly status meetings India Contract 2 developers 1 project per person One daily status meeting
kan 看カン visual ban 板バン card
Respect for People Continuous Improvement
Visualize Work Make Policies Explicit Limit WIP Focus on Flow Commit to Continuous Improvement
Make Work Visible Limit WIP Help Work Flow
Impact of Reducing WIP on Throughput & Cycle Time
Executive Decision to Limit WIP
Determine Your WIP & Halve It Then Halve It Again Baseline Lead/Touch Times Map Your Value Stream Expedite & Measure One Item Expose & Embrace Pain
Connect. Share. Discuss. Learning Microsoft Certification & Training Resources TechNet Resources for IT Professionals Resources for Developers
Required Slide Complete an evaluation on CommNet and enter to win!
Scan the Tag to evaluate this session now on myTechEd Mobile