AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI. This time the event was based on four major themes : 'Agile for newbies', ' Agile Adoption Challenges', 'Workshops and Software Craftsmanship', and ' Post Agile'.

1. Kanban
Mayur Gupta
Principal Consultant

2. Agenda
 Introduction
 Origin
 Definition
 Setting Up Kanban
 Kanban in action
 Metrics
 Case Study

3. Supermarkets

4. What is Kanban?
Kan is Visual
Ban is Card
Kanban is “Visual Card”

5. Origin
Kanban
Taiichi Ohno —
Father of the Toyota
Production System
Lean JIT

6. Kanban in Software Development
Kanban System
is about letting value
flow through the system
by pulling work when there is capacity
available
as indicated by WIP limits
and adjusting these WIP limits to derive
continuous improvement

7. Lean Principles
Kanban
Customer Value Continuous Waste Continuous
Pull
Flow Elimination Improvement

8. Setting Up Kanban
STEP 1: Create a Value Stream Map
Feature waiting waiting waiting waiting
Analysis Dev Test UAT In Prod
.5 day 1 day 3 days 5 days
1 day 4 days 2 days 3 days
Ready Analysis Dev Dev Test Test UAT UAT Release In Prod
Ready Ready Ready Ready
Flow

9. Setting Up Kanban
STEP 2: Define WIP limits
Ready Analysis Dev Dev Test Test UAT UAT Release In Prod
3 2 Ready 3 2 Ready 1 Ready 8 Ready
2 5 10

10. Kanban in Action
Ready Analysis Dev Dev Test Test UAT UAT Release In Prod
3 2 Ready 2 2 Ready 1 Ready 8 Ready
2 5 10
A
B
C

11. Kanban in Action
Ready Analysis Dev Dev Test Test UAT UAT Release In Prod
3 2 Ready 2 2 Ready 1 Ready 8 Ready
2 5 10
D A
E B
C

12. Kanban in Action
Ready Analysis Dev Dev Test Test UAT UAT Release In Prod
3 2 Ready 2 2 Ready 1 Ready 8 Ready
2 5 10
D A
E B
C

13. Kanban in Action
Ready Analysis Dev Dev Test Test UAT UAT Release In Prod
3 2 Ready 2 2 Ready 1 Ready 8 Ready
2 5 10
D A
E B
C

14. Kanban in Action
Ready Analysis Dev Dev Test Test UAT UAT Release In Prod
3 2 Ready 2 2 Ready 1 Ready 8 Ready
2 5 10
D
E A
I G C
J F B
H

15. Kanban in Action
Ready Analysis Dev Dev Test Test UAT UAT Release In Prod
3 2 Ready 2 2 Ready 1 Ready 8 Ready
2 5 10
D
C E A
I G
J F B
H

16. Kanban in Action
Ready Analysis Dev Dev Test Test UAT UAT Release In Prod
3 2 Ready 2 2 Ready 1 Ready 8 Ready
2 5 10
D
C E A
I G
J F B
H
Flow

17. Pull System with WIP Limits
• Reduces multi tasking
• Makes bottlenecks & gaps visible
• Maximize throughput
• Little’s Law for Queuing Theory
Cycle Time = No of things in progress
Average Completion Rate
• Better Teamwork

18. Metrics & Reporting
• Cumulative Flow Diagram (CFD)
Feature Flow
C u m u la tiv e F lo w D ig ra m
600
140
500
120
100 To D o
400
Total Features
Total Features
80 A na lys is
To Do
C ode
300 In Progress 60
Te s t
Completed 40 D o ne
200 20
0
100
20-02-2004
27-02-2004
05-03-2004
12-03-2004
19-03-2004
26-03-2004
02-04-2004
09-04-2004
16-04-2004
23-04-2004
30-04-2004
07-05-2004
14-05-2004
21-05-2004
28-05-2004
0
Apr May Jun Jul Aug Sep
D ate
Date

19. Metrics & Reporting
Cycle Time: Duration of time to complete a item when it is
ready.
Cycle Time
Cc T e
y le im
25
20
1
5
Cc T e
y le im
1
0
5
0

20. Metrics & Reporting
• Quality
• Throughput
• Timely performance

21. Case Study
Team Configuration
• 6 members cross functional team
• Defect Fixing
Sprint
(2weeks)
Sprint Backlog

22. Challenges
• Failed Sprints most of the time
• Priorities changing frequently
• Bug estimation difficult
• Hard release date

23. Options
Option 1: Sprints with buffer for high priority work
Option 2: Shorter sprints
But still defect estimation is …
• Difficult
• Time Consuming
• Inaccurate

24. Another solution
Test Doc SAT Ready
Ready (5) Dev (3) Test (2) Doc (1)
Ready (3) Ready (2) (10)
Defect Pool
Defect Silver Bullet Blocked Bug

25. References
• http://www.limitedwipsociety.org/
• http://availagility.co.uk (Karl Scotland)
• http://www.agilemanagement.net/ (David J Anderson)

26. “Rather than focusing on being Agile which may (and should)
lead to being successful, Kanban focuses on becoming
successful, which may lead to being Agile.”
Thank You