Kanban for generic use: a visual guide

95
Kanban for generic use July 2015 Álvaro Ruiz de Mendarozqueta

Transcript of Kanban for generic use: a visual guide

Kanban for generic use

July 2015

Álvaro Ruiz de Mendarozqueta

看板

Kanban A visual guide

Versión 1.1 Alvaro Ruiz de Mendarozqueta; review Diego Rubio

看板

Visual card

Kanban

Kanban

Basics

看板

Basic board

TO DO DOING DONE

Basic board

TO DO DOING DONE

To do list List of just doing tasks Finished tasks

Whiteboard

Lines that separate columns

To do tasks

TO DO DOING DONE

T1 T2

T3

T4

To do tasks

TO DO DOING DONE

T1 T2

T3

T4

Adhesive card

Tasks

Doing

TO DO DOING DONE

T1

T2

T3

T4

T1

T2

Doing

TO DO DOING DONE

T1

T2

T3

T4

T1

T2

When you start working on a task, you move the card

Doing

TO DO DOING DONE

T1

T2

T3

T4

T1

T2

T3

T4

Doing and Done

TO DO DOING DONE

T1

T2

T3

T4

T1

T2

T3

T4 When the task is finished you move it to “done”

Done

TO DO DOING DONE

T1

T2

T3

T4

T3

T4

Task basic information

TO DO DOING DONE

Name: To do date: Finished date:

Task basic information

TO DO DOING DONE

Name: To do date: Finished date:

Usual but you can add more info if needed

We can measure throughput

TO DO DOING DONE

T1

T2

T3

T4

Number of finished taks: 4

T1

T2

T3

T4

Throughput

We can measure throughput

TO DO DOING DONE

We can measure lead time

T1 T1 T1

Time “t” in order to finish T1

TO DO DOING DONE

We can measure lead time

T1 T1 T1

Lead Time

TO DO DOING DONE

We can measure net work

T1 T1 T1

Time “t” for T1 net work

TO DO DOING DONE

We can measure net work

TO DO DOING DONE

T1 T1 T1

Cycle time

TO DO DOING DONE

T1

T2

T3

T4

T1

T2

T3

T4

We can measure the work-in-progress

Work in progress: 2

T1

T2

T3

T4

T1

T2

T3

T4

We can measure the work-in-progress

W.I.P

TO DO DOING DONE

Kanban Some problems and

their solutions

看板

Do you have too many tasks?

TO DO DOING DONE

T1 T2

T3

T4

Problem #1

Do you have too many tasks?

TO DO DOING DONE

T1 T2

T3

T4

Kanban helps but can’t do miracles You have to sort, delete and prioritize!

Pending column

TO DO DOING DONE PENDING

Pending column

New column for pending tasks

Place here all new tasks

TO DO DOING DONE PENDING

Pending column

TO DO DOING DONE PENDING

T1

T2

T3

T4

Task ready to start working on it

Pending task

Pending column

TO DO DOING DONE PENDING

T1

T2

T3

T4

What we choose?

Pending column

TO DO DOING DONE PENDING

ERASED

Board with erased tasks

T4

The task is not ready to get started and is not important

Task is ready to start and it’s important

We can keep them visible or delete

TO DO DOING DONE PENDING

ERASED

Board with erased tasks

T4

TO DO DOING DONE PENDING

More information about the task

TO DO DOING DONE

Task name: Responsible: Importance: “To do” date: Finished date:

More information about the task

TO DO DOING DONE

Task name: Responsible: Importance: “To do” date: Finished date:

Assign the importance of the task, for example from 1 to 5

More information about the task

TO DO DOING DONE

Task name: Responsible: Importance: Complexity: “To do” date: Finished date:

More information about the task

TO DO DOING DONE

Task name: Responsible: Importance: Complexity: “To do” date: Finished date:

If you also assign complexity we can select combining complexity and importance

Choosing with importance

Importance High to Low +

-

Ordered tasks using importance

TO DO DOING DONE PENDING

T1

T2

T3

T4

Importance = 5

Importance = 4

Importance = 3

Importance = 2

Choosing with importance

TO DO DOING DONE PENDING

Complexity Low to High

+

-

-

+

Ordered tasks using importance and complexity

Choosing with importance

TO DO DOING DONE PENDING

Importance High to Low

+

-

-

+

Lower importance and high complexity tasks, are candidates for deletion

Choosing with importance

TO DO DOING DONE PENDING

T1

T2

T3

T4

Importance = 5

Importance = 4

Importance = 3 Complexity= 1

Importance = 3 Complexity= 2

Choosing with importance and complexity

TO DO DOING DONE PENDING

Not finished

T1

T2

T3

T4

Problem #2

Not ready

TO DO DOING DONE

T1

T2

T3

T4

T1

Task goes back to DOING

Not finished

TO DO DOING DONE

T1 T1

T1

T1

Still not ready, pending things to do

1

2

3

Not finished

TO DO DOING DONE

Adding done criteria

Name: Responsible: Done criteria: Importance: Complexity: “To do” date: Finished date:

Adding done criteria in order to know that the task is done.

TO DO DOING DONE

Done criteria

T1

T2

T3

T4

Done criteria is fulfilled

T1

TO DO DOING DONE

T1

T2

T3

T4

Done criteria

If all tasks have the same done criteria, it could be placed in the section

T1

Done criteria

TO DO DOING DONE

Blocked tasks

T1

T2

T3

T4

The task can not be completed (usually depends on third party activities)

Problem #3

TO DO DOING DONE

T1

T2

T3

T4

Mark the blocked task

Colored sticker or any other sign

Blocked tasks

TO DO DOING DONE

A section for blocked tasks can be added

T1

T2

T4

T3

Task is moved to the blocked section

T1

TO DO DOING DONE BLOCKED

T1

T2

T4

T1 Goes back to DOING when block is released

T3

A section for blocked tasks can be added

TO DO DOING DONE BLOCKED

Blocked or waiting a response

TERMINADO

T1

T2

T4

T3

Waiting a response

Problem #3, with waiting

Blocked by a problem

TO DO DOING BLOCKED

T1

T2

T4

T3

Waiting time is recorded

Elapsed time until the problem is resolved is recorded

Blocked or waiting a response

TO DO DOING BLOCKED DONE

Working in too many tasks

T1

T2

T3

T4

Problem #4

Working on all of them and no finished tasks

Blocking Multitasks Procrastinate

TO DO DOING

Work in progress

T1

T2

T4

T3

Work in Progress (WIP) = 2

Limiting work in progress in DOING

TO DO DOING DONE BLOCKED

T1

T2

T4

T3

WIP = 2

Work in progress limit (WIP) = 2 Showed in the board

Work in progress

TO DO DOING DONE BLOCKED

T1

T2

T4

T3

WIP = 2

Work in progress

TO DO DOING DONE BLOCKED

The goal is to keep a sustainable pace

WIP = 2

Work in progress

TO DO DOING DONE BLOCKED

T1

T2

T4

T3 T2 T3

New task enter in column only if WIP is below limit

Kanban

All together

看板

TO DO DOING DONE PENDING BLOCKED

WIP= 2

T1

T2

T3

T4

T6

T5

T7

T8

DONE CRITERIA

Kanban

Different tasks

看板

WIP = 2

T1 T2

T3

T4

T6

T5

T7

T8

DONE CRITERIA

Some tasks are different

Different tasks TO DO DOING DONE PENDING BLOCKED

WIP = 2

T1 T2

T3

T4

T6

T5

T7

T8

DONE CRITERIA

Done criteria will vary for each task type

Different tasks

we can identify task type with different colors

TO DO DOING DONE PENDING BLOCKED

WIP= 2

T1

T3

T4

T6

T5

T7

T8

Different tasks can be separated with swim lines

T2

T4

T5

T8

Different tasks TO DO DOING DONE PENDING BLOCKED

Kanban When DOING is

complex

看板

Several steps in DOING

TO DO DOING DONE

T1

T2

T4

BLOCKED

T3

WIP = 2

T2 T3

Steps are needed in order to finish the task

Analyzing the process

Value added chain

P1 P2 P3 Input Output O1 = I2 O2 = I3

The output of a process must add value to the input

TO DO DOING DONE PENDING BLOCKED

T1 T2

T3

T4

T6

T5

T7

T8

Split DOING

Split DOING based on the value chain

P1 P2 P3

P1 P2 P3

C1 C2 C3

Done criteria will be different for each step

Kanban

Who is working

看板

T1 T2

T3

T4

T6

T5

T7

T8

Who is working

Responsible for each task is identified

P1 P2 P3

C1 C2 C3

T6

TO DO DOING DONE PENDING BLOCKED

Kanban

Fundamentals

看板

T1 T2

T3

T4

T6

T5

T7

T8

Visibility

P1 P2 P3

C1 C2 C3

White board shows what is happening

1

TO DO DOING DONE PENDING BLOCKED

Visibility

TO DO DOING DONE

Task name: Responsible: Done criteria: TO DO date: DONE date: Priority: Complexity:

Management key information

1

T1 T2

T3

T4

T6

T5

T7

T8

Focus on the flow

Focus on the added value flow

P1 P2 P3

P1 P2 P3

C1 C2 C3

2

TO DO DOING DONE PENDING BLOCKED

T1 T2

T3

T4

T6

T5

T7

T8

Explicit quality policy as done criteria

Each process has its done criteria

P1 P2 P3

P1 P2 P3

C1 C2 C3

3

TO DO DOING DONE PENDING BLOCKED

T1 T2

T3

T4

T6

T5

T8

Explicit quality policy as done criteria

P1 P2 P3

P1 P2 P3

C1 C2 C3

3

TO DO DOING DONE PENDING BLOCKED

T1 T1

T7 If done criteria is fulfilled, task is considered done

Measurement 4

Date TODO DOING BLOCKED DONE

01/03/2015 10 0 0 0

02/03/2015 8 1 1 0

03/03/2015 5 2 1 2

04/03/2015 7 3 2 2

05/03/2015 7 3 0 4

06/03/2015 6 3 1 4

07/03/2015 8 3 0 5

08/03/2015 9 4 0 5

09/03/2015 10 2 2 7

10/03/2015 9 1 3 8

11/03/2015 10 2 2 9

For each day

We recorded how many tasks are in each stage of the process

Measurement 4

Process steps

0 0 2 2

4 4 5 5 7 8 9 10

12 14

16 18 19

21 22 23 25

27 29 30

0 1

2 3 3

3 3 4

2 1 2 2

2

2

2 1

2 1 1

2 2

2 3

2

0

5

10

15

20

25

30

35

400

1/0

3/2

01

5

02

/03

/20

15

03

/03

/20

15

04

/03

/20

15

05

/03

/20

15

06

/03

/20

15

07

/03

/20

15

08

/03

/20

15

09

/03

/20

15

10

/03

/20

15

11

/03

/20

15

12

/03

/20

15

13

/03

/20

15

14

/03

/20

15

15

/03

/20

15

16

/03

/20

15

17

/03

/20

15

18

/03

/20

15

19

/03

/20

15

20

/03

/20

15

21

/03

/20

15

22

/03

/20

15

23

/03

/20

15

24

/03

/20

15

TO DO

DOING

BLOCKED

DONE

Work in progress

Measurement 4

0 0 2 2

4 4 5 5 7 8 9 10

12 14

16 18 19

21 22 23 25

27 29 30

0 1

2 3 3

3 3 4

2 1 2 2

2

2

2 1

2 1 1

2 2

2 3

2

0

5

10

15

20

25

30

35

400

1/0

3/2

01

5

02

/03

/20

15

03

/03

/20

15

04

/03

/20

15

05

/03

/20

15

06

/03

/20

15

07

/03

/20

15

08

/03

/20

15

09

/03

/20

15

10

/03

/20

15

11

/03

/20

15

12

/03

/20

15

13

/03

/20

15

14

/03

/20

15

15

/03

/20

15

16

/03

/20

15

17

/03

/20

15

18

/03

/20

15

19

/03

/20

15

20

/03

/20

15

21

/03

/20

15

22

/03

/20

15

23

/03

/20

15

24

/03

/20

15

TO DO

DOING

BLOCKED

DONE

Effective work average

Measurement 4

0 0 2 2

4 4 5 5 7 8 9 10

12 14

16 18 19

21 22 23 25

27 29 30

0 1

2 3 3

3 3 4

2 1 2 2

2

2

2 1

2 1 1

2 2

2 3

2

0

5

10

15

20

25

30

35

400

1/0

3/2

01

5

02

/03

/20

15

03

/03

/20

15

04

/03

/20

15

05

/03

/20

15

06

/03

/20

15

07

/03

/20

15

08

/03

/20

15

09

/03

/20

15

10

/03

/20

15

11

/03

/20

15

12

/03

/20

15

13

/03

/20

15

14

/03

/20

15

15

/03

/20

15

16

/03

/20

15

17

/03

/20

15

18

/03

/20

15

19

/03

/20

15

20

/03

/20

15

21

/03

/20

15

22

/03

/20

15

23

/03

/20

15

24

/03

/20

15

TO DO

DOING

BLOCKED

DONE

Possible bottle neck due to too much blocks

Possible impediment

Limit work in progress

T1

T2

T4

T3

WIP = 2

Looking for a sustainable pace

5

TO DO DOING DONE BLOCKED

T1

T2

T4

T3

WIP = 3

Try and measure reulus

5

Change WIP

Limit work in progress

TO DO DOING DONE BLOCKED

Try and measure results

Change WIP

TO DO DOING DONE PENDING BLOCKED

WIP = 2

T1 T2

T3

T4

T6

T5

T7

T8

DONE CRITERIA

WIP can be set in other columns

Limit work in progress 5

WIP = 2

T1 T2

T3

T4 T6

T5

T7

T8

DONE CRITERIA

WIP limit can be set in order to make the process more agile

5

WIP = 3

TO DO DOING DONE PENDING BLOCKED

Limit work in progress

WIP = 2

T1 T2

T3

T4 T6

T5

T7

T8

DONE CRITERIA

5

WIP = 3

TO DO DOING DONE PENDING BLOCKED

Limit work in progress

Limiting WIP in TO DO pushes to keep PENDING update

Continuous improvement 6

Plan

Do

Check

Act

Kanban Little law

(why WIP should be limited)

看板

Little law

𝐿𝑒𝑎𝑑 𝑇𝑖𝑚𝑒 =𝑊. 𝐼. 𝑃.

𝑇𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡

Little law

TO DO DOING DONE

T1 T2

Lead Time

T3

T4

T5

T6

T7

T8

Throughput

WIP

𝐿𝑒𝑎𝑑 𝑇𝑖𝑚𝑒 =𝑊. 𝐼. 𝑃.

𝑇𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡

If WIP increases, so does Lead Time

+ +

Little law

𝐿𝑒𝑎𝑑 𝑇𝑖𝑚𝑒 =𝑊. 𝐼. 𝑃.

𝑇𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡

Limiting WIP

-

Increasing throughput

+

Optimizing

𝐿𝑒𝑎𝑑 𝑇𝑖𝑚𝑒 =𝑊. 𝐼. 𝑃.

𝑇𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡

References

1. Kanban and Scrum - making the most of both; Henrik Kniberg & Mattias Skarin; Info Q en http://www.infoq.com/minibooks/kanban-scrum-minibook

2. Priming Kanban; Jesper Boeg; en http://www.infoq.com/minibooks/priming-kanban-jesper-boeg

3. Lean Software Development: An Agile Toolkit; Mary Poppendieck, Tom Poppendieck; Addison Wesley

4. http://www.everydaykanban.com/what-is-kanban/

5. http://www.scrummanager.net/files/flujotableroskanban.pdf

LIDICALSO Laboratorio de Investigación y Desarrollo en Ingeniería y Calidad de Software

LIDICALSO http://www.institucional.frc.utn.edu.ar/sistemas/lidicalso/

Departamento de Ing. en Sistemas de Información UTN FRC Córdoba, Argentina

Álvaro Ruiz de Mendarozqueta

[email protected]

[email protected]

skype: alvaro.rdm

http://www.slideshare.net/AlvaroRuizdeMendaroz