Kanban

Mayur GuptaPrincipal Consultant

Agenda

Introduction Origin Definition

Setting Up Kanban Kanban in actionMetrics Case Study

Supermarkets

What is Kanban?Kan is VisualBan is Card

Kanban is “Visual Card”

Origin

Taiichi Ohno — Father of the Toyota Production System

Lean JIT

Kanban

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

Lean Principles

Kanban

Customer Value Continuous Flow Pull Waste

EliminationContinuous Improvement

Setting Up KanbanSTEP 1: Create a Value Stream Map

Ready Analysis Dev Ready

Dev Test Ready

Test UAT Ready

UAT Release Ready

In Prod

AnalysisFeature

Dev Test UAT In Prodwaiting waiting waiting waiting

1 day.5 day

4 days

1 day

2 days 3 days

3 days 5 days

Flow

Setting Up Kanban

STEP 2: Define WIP limits

Ready3

Analysis2

Dev Ready 3

Dev2

Test Ready2

Test1

UAT Ready5

UAT8

Release Ready10

In Prod

Kanban in ActionReady3

Analysis2

Dev Ready 2

Dev2

Test Ready2

Test1

UAT Ready5

UAT8

Release Ready10

In Prod

A

B

C

Kanban in ActionReady3

Analysis2

Dev Ready 2

Dev2

Test Ready2

Test1

UAT Ready5

UAT8

Release Ready10

In Prod

A

B

C

D

E

Kanban in ActionReady3

Analysis2

Dev Ready 2

Dev2

Test Ready2

Test1

UAT Ready5

UAT8

Release Ready10

In Prod

A

B

C

D

E

Kanban in ActionReady3

Analysis2

Dev Ready 2

Dev2

Test Ready2

Test1

UAT Ready5

UAT8

Release Ready10

In Prod

A

BC

D

E

Kanban in ActionReady3

Analysis2

Dev Ready 2

Dev2

Test Ready2

Test1

UAT Ready5

UAT8

Release Ready10

In Prod

A

B

GD

EC

FH

I

J

Kanban in ActionReady3

Analysis2

Dev Ready 2

Dev2

Test Ready2

Test1

UAT Ready5

UAT8

Release Ready10

In Prod

A

B

GD

EC

FH

I

J

Kanban in ActionReady3

Analysis2

Dev Ready 2

Dev2

Test Ready2

Test1

UAT Ready5

UAT8

Release Ready10

In Prod

A

B

GD

EC

F

I

J H

Flow

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

Metrics & Reporting

• Cumulative Flow Diagram (CFD)

Feature Flow

0

100

200

300

400

500

600

Apr May Jun Jul Aug Sep

Date

Tota

l Fea

ture

s

To DoIn ProgressCompleted

C u m u la tiv e F lo w D ig ra m

0

2 0

4 0

6 0

8 0

1 0 0

1 2 0

1 4 0

20-0

2-20

0427

-02-

2004

05-0

3-20

0412

-03-

2004

19-0

3-20

0426

-03-

2004

02-0

4-20

0409

-04-

2004

16-0

4-20

0423

-04-

2004

30-0

4-20

0407

-05-

2004

14-0

5-20

0421

-05-

2004

28-0

5-20

04

Date

Tota

l Fea

ture

s

To D oA na lys isC o d eTe s tD o ne

Metrics & Reporting

Cycle Time: Duration of time to complete a item when it is ready.

Cycle Time

Cycle Time

0

5

10

15

20

25

Cycle Time

Metrics & Reporting

• Quality• Throughput• Timely performance

Case StudyTeam Configuration

• 6 members cross functional team

• Defect Fixing

Sprint

Sprint Backlog

(2weeks)

Challenges

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

Options

Option 1: Sprints with buffer for high priority work

Option 2: Shorter sprints

But still defect estimation is …• Difficult• Time Consuming• Inaccurate

Another solutionReady (5) Dev (3)

Test Ready (3)

Test (2)Doc Ready (2)

Doc (1) SAT Ready (10)

Defect Pool

Defect Silver Bullet Blocked Bug

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

“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