Transcript AAP204 [email protected] US Team India Contract • 10 developers • 23 projects • 6-8 projects per person • But one dev working 16 projects, all with weekly status meetings •

AAP204
[email protected]
US Team
India Contract
• 10 developers
• 23 projects
• 6-8 projects per person
• But one dev working
16 projects, all with
weekly status
meetings
• 2 developers
• 1 project per person
• One daily status
meeting
Impact of High Work in Process (WIP)
Introduction to Kanban
kan
看
カン
visual
ban
板
バン
card
Respect for
People
Continuous
Improvement
Visualize
Work
Focus
on Flow
Make
Policies
Explicit
Limit
WIP
Commit to
Continuous
Improvement
accept a WIP limit
pull work
An Example
Håkan Forss
Håkan Forss
Håkan Forss
Hours of Throughput
Hours of Effort
60
50
51.6
40
28.96
30
27.04
26.8
18.64
20
10
4.372
3.435
3.038
2.781
2.756
0
January
February
March
April
May
1/6/2011
1/8/2011
1/10/2011
1/12/2011
1/14/2011
1/16/2011
1/18/2011
1/20/2011
1/22/2011
1/24/2011
1/26/2011
1/28/2011
1/30/2011
2/1/2011
2/3/2011
2/5/2011
2/7/2011
2/9/2011
2/11/2011
2/13/2011
2/15/2011
2/17/2011
2/19/2011
2/21/2011
2/23/2011
2/25/2011
2/27/2011
3/1/2011
3/3/2011
3/5/2011
3/7/2011
3/9/2011
3/11/2011
3/13/2011
3/15/2011
3/17/2011
3/19/2011
3/21/2011
3/23/2011
3/25/2011
3/27/2011
3/29/2011
3/31/2011
4/2/2011
4/4/2011
4/6/2011
4/8/2011
4/10/2011
4/12/2011
4/14/2011
4/16/2011
4/18/2011
4/20/2011
4/22/2011
4/24/2011
4/26/2011
4/28/2011
4/30/2011
5/2/2011
5/4/2011
5/6/2011
5/8/2011
5/10/2011
5/12/2011
200
180
160
140
120
100
80
60
40
20
0
Some Math
Executive
Decision to Limit
WIP
WIP is a LEADING metric
for Lead Time
Flow
Getting Started
Determine
Your WIP &
Halve It
Then Halve
It Again
Baseline
Lead/Touch
Times
Map Your
Value
Stream
Expedite &
Measure
One Item
Expose &
Embrace
Pain
http://northamerica.msteched.com
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn