Kanban for generic use Ă lvaro Ruiz de Mendarozqueta July 2015
Kanban A visual guide
看板 Versión 1.1 Alvaro Ruiz de Mendarozqueta; review Diego Rubio
Kanban Visual card
看板
Kanban Basics 看板
Basic board TO DO
DOING
DONE
Basic board TO DO
To do list
DOING
List of just doing tasks
Lines that separate columns
Whiteboard
DONE
Finished tasks
To do tasks TO DO
T1
DOING
T2
T3 T4
DONE
To do tasks TO DO
T1
DOING
T2
T3 T4
Tasks
Adhesive card
DONE
Doing TO DO
T1 T2
T3
T4
DOING
T1 T2
DONE
Doing TO DO
T1 T2
DOING
T1 T2
T3
T4
When you start working on a task, you move the card
DONE
Doing TO DO
DOING
DONE
T1 T2
T3 T3 T4 T4
T1
T2
Doing and Done TO DO
DOING
DONE
T1 T2
T1
T2
T3 T3 T4 T4
When the task is finished you move it to “done”
Done TO DO
DOING
DONE
T1
T2
T3 T3 T4 T4
Task basic information TO DO
Name:
To do date: Finished date:
DOING
DONE
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
Number of finished taks: 4 T3
T4
We can measure throughput TO DO
DOING
DONE
T1
T2
Throughput T3
T4
We can measure lead time TO DO
T1
DOING
DONE
T1
Time “t” in order to finish T1
T1
We can measure lead time TO DO
T1
DOING
T1
Lead Time
DONE
T1
We can measure net work TO DO
T1
DOING
DONE
T1
Time “t” for T1 net work
T1
We can measure net work TO DO
T1
DOING
DONE
T1
T1
Cycle time
We can measure the work-in-progress TO DO
DOING
DONE
T1 T2
T1
T2
T3 T3 T4 T4
Work in progress: 2
We can measure the work-in-progress TO DO
DOING
DONE
T1 T2
T1
T2
T3 T3 T4 T4
W.I.P
Kanban Some problems and their solutions 看板
Do you have too many tasks? Problem #1 DOING
TO DO
T1
T2
T3 T4
DONE
Do you have too many tasks? TO DO
T1
DOING
DONE
T2
T3 T4
Kanban helps but can’t do miracles You have to sort, delete and prioritize!
Pending column PENDING
TO DO
DOING
DONE
Pending column PENDING
TO DO
New column for pending tasks
Place here all new tasks
DOING
DONE
Pending column PENDING
TO DO
DOING
DONE
Pending column PENDING
TO DO
DOING
T1 T2 T3 T4
Pending task
Task ready to start working on it
DONE
Pending column PENDING
TO DO
T1 T2 T3 T4
What we choose?
DOING
DONE
Board with erased tasks PENDING
TO DO
DOING
DONE
Task is ready to start and it’s important
T4
The task is not ready to get started and is not important
ERASED
We can keep them visible or delete
Board with erased tasks PENDING
TO DO
T4
ERASED
DOING
DONE
More information about the task TO DO
Task name: Responsible: Importance: “To do” date: Finished date:
DOING
DONE
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
Task name: Responsible: Importance: Complexity: “To do” date: Finished date:
DOING
DONE
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 PENDING
TO DO
+
DOING
Importance High to Low
Ordered tasks using importance
-
DONE
Choosing with importance PENDING
TO DO T1
DOING
Importance = 5
T2
Importance = 4
T3
Importance = 3
T4
Importance = 2
DONE
Choosing with importance PENDING
TO DO
+
DONE
DOING
Importance High to Low
Ordered tasks using importance and complexity
-
+
Complexity Low to High
Choosing with importance PENDING
TO DO
+
DOING
DONE
-
Lower importance and high complexity tasks, are candidates for deletion
-
+
Choosing with importance and complexity PENDING
TO DO T1
DOING
Importance = 5
T2
Importance = 4
T3
Importance = 3 Complexity= 1
T4
Importance = 3 Complexity= 2
DONE
Not finished Problem #2 TO DO
DOING
DONE
T1
T2
Not ready T3
T4
Not finished TO DO
DOING
T1
DONE
T1
T2
T3
T4
Task goes back to DOING
Not finished TO DO
DOING
DONE
1
T1
T1
2
T1
T1 3 Still not ready, pending things to do
Adding done criteria TO DO
Name: Responsible: Done criteria: Importance: Complexity: “To do� date: Finished date:
DOING
DONE
Adding done criteria in order to know that the task is done.
Done criteria TO DO
DOING
DONE
T1
T2
T3
T4
T1
Done criteria is fulfilled
Done criteria TO DO
DOING
T1
DONE
T1
T2
T3
T4
Done criteria
If all tasks have the same done criteria, it could be placed in the section
Blocked tasks TO DO
DOING
Problem #3 DONE
T1
T2
T3
T4
The task can not be completed (usually depends on third party activities)
Blocked tasks TO DO
DOING
DONE
T1
T2 Mark the blocked task T3
T4
Colored sticker or any other sign
A section for blocked tasks can be added TO DO
DOING
T1
BLOCKED
DONE
T1
T2 Task is moved to the blocked section
T3 T4
A section for blocked tasks can be added DOING
TO DO
BLOCKED
DONE
T1
T1
Goes back to DOING when block is released
T2
T3 T4
Blocked or waiting a response TO DO
DOING
BLOCKED
Problem #3, with waiting TERMINADO
T1
T2
Blocked by a problem
T3 T4 Waiting a response
Blocked or waiting a response TO DO
DOING
BLOCKED
DONE
T1 Elapsed time until the problem is resolved is recorded
T2
T3 T4 Waiting time is recorded
Working in too many tasks TO DO
DOING
Problem #4
T1 T2 T3
Working on all of them and no finished tasks
T4 Blocking Multitasks Procrastinate
Work in progress TO DO
DOING
BLOCKED
DONE
T1
T2 Limiting work in progress in DOING
T3 T4
Work in Progress (WIP) = 2
Work in progress TO DO
DOING
BLOCKED
DONE
T1
T2 T3 T4 Work in progress limit (WIP) = 2 Showed in the board
WIP = 2
Work in progress TO DO
DOING
BLOCKED
DONE
T1
T2 T3 T4
WIP = 2
The goal is to keep a sustainable pace
Work in progress DOING
TO DO
BLOCKED
DONE
T1
T3
T3
T2
T4
WIP = 2
T2
New task enter in column only if WIP is below limit
Kanban All together 看板
PENDING
TO DO
DOING
BLOCKED
DONE
T1 T5 T2 T6 T3 T7
T4 T8
DONE CRITERIA
WIP= 2
Kanban Different tasks 看板
Different tasks PENDING
TO DO
DOING
T5 T6
BLOCKED
T2 T3
T7 T4 T8
Some tasks are different
DONE CRITERIA
WIP = 2
DONE
T1
Different tasks PENDING
TO DO
DOING
T5
T6 T7
BLOCKED
DONE
T2
T1
T3
T4
we can identify task type with different colors
T8
DONE CRITERIA
WIP = 2
Done criteria will vary for each task type
Different tasks PENDING
TO DO
DOING
BLOCKED
DONE
T2
T5
T6
T3
T7
T4
T8
T1
Different tasks can be separated with swim lines WIP= 2
Kanban When DOING is complex 看板
Several steps in DOING TO DO
DOING
BLOCKED
Steps are needed in order to finish the task
T1
T3
DONE
T3
T2
T4
WIP = 2
T2
Analyzing the process The output of a process must add value to the input
Input
P1
O1 = I2
P2
O2 = I3
P3
Value added chain
Output
Split DOING PENDING
TO DO T5
T6
DOING P1
BLOCKED
P2
P3 T2
P1
P2
DONE
T1
P3
Split DOING based on the value chain T7 T8
T4
T3
C1
C2
Done criteria will be different for each step C3
Kanban Who is working 看板
Who is working PENDING
TO DO T5
DOING P1
BLOCKED
P2
P3 T2
T6 T6 T7 T8
T4
T3
Responsible for each task is identified C1
C2
C3
DONE
T1
Kanban Fundamentals 看板
Visibility
1 PENDING
TO DO T5
DOING P1
BLOCKED
P2
P3 T2
DONE
T1
T6 White board shows what is happening T7 T8
T4
T3
C1
C2
C3
1
Visibility
TO DO
DOING
DONE
Task name: Responsible: Done criteria: TO DO date: DONE date: Priority: Complexity:
Management key information
2 PENDING
Focus on the flow
TO DO T5
T6
DOING P1
BLOCKED
P2
P3 T2
P1
P2
DONE
T1
P3
Focus on the added value flow T7 T8
T4
T3
C1
C2
C3
3 PENDING
Explicit quality policy as done criteria TO DO T5
T6
DOING P1
BLOCKED
P2
P3 T2
P1
P2
DONE
T1
P3
T7 T8
T4
Each process has its done criteria T3
C1
C2
C3
3 PENDING
Explicit quality policy as done criteria TO DO T5
T6
DOING P1
BLOCKED
P2
P3 T2
P1
P2
T4 T7
T3
C1
C2
T1
P3
T1 T8
DONE
C3
T1 If done criteria is fulfilled, task is considered done
4
Measurement
We recorded how many tasks are in each stage of the process
For each day Date
TODO 01/03/2015 02/03/2015 03/03/2015 04/03/2015 05/03/2015 06/03/2015 07/03/2015 08/03/2015 09/03/2015 10/03/2015 11/03/2015
DOING 10 8 5 7 7 6 8 9 10 9 10
BLOCKED 0 1 2 3 3 3 3 4 2 1 2
DONE 0 1 1 2 0 1 0 0 2 3 2
0 0 2 2 4 4 5 5 7 8 9
2
4
5 5 8 9 10
7 12 14 18 19 23 21 22 25 27
24/03/2015
2
23/03/2015
Work in progress
22/03/2015
2
21/03/2015
25
20/03/2015
2 1
19/03/2015
2
18/03/2015
4 16
17/03/2015
2
16/03/2015
20
15/03/2015
1 2
14/03/2015
15
13/03/2015
3
12/03/2015
3
11/03/2015
3
10/03/2015
10
09/03/2015
4
08/03/2015
5 3
07/03/2015
30
06/03/2015
2
04/03/2015
35
05/03/2015
2
03/03/2015
0 0 1 0
02/03/2015
01/03/2015
4
Measurement
40
3 2
2 1
2 29 30
Process steps
2
2
1 TO DO
DOING
BLOCKED
DONE
Effective work average 2
5
4 8 9 10
7 12 14 18 19 23 21 22 25 27
24/03/2015
2
23/03/2015
30
22/03/2015
2
21/03/2015
25
20/03/2015
2 1
19/03/2015
2
18/03/2015
3 16
17/03/2015
2
16/03/2015
20
15/03/2015
1 2
14/03/2015
15
13/03/2015
3
12/03/2015
3
11/03/2015
5
08/03/2015
3
10/03/2015
4
07/03/2015
10
09/03/2015
4
06/03/2015
2
04/03/2015
5
05/03/2015
2
03/03/2015
0 0 1 0
02/03/2015
01/03/2015
4
Measurement
40
35 3 2
2
2
1
2 1 TO DO
2
DOING
29 30 BLOCKED
DONE
2
5
Possible bottle neck due to 35 much blocks too
8 9 10
7 12 14 18 19 23 21 22 25 27
24/03/2015
2
23/03/2015
30
22/03/2015
2
21/03/2015
25
20/03/2015
2 1
19/03/2015
2
18/03/2015
4 16
17/03/2015
2
16/03/2015
20
15/03/2015
1 2
14/03/2015
15
13/03/2015
3
12/03/2015
3
11/03/2015
5
08/03/2015
3
10/03/2015
4
07/03/2015
10
09/03/2015
4
06/03/2015
2
04/03/2015
5 3
05/03/2015
2
03/03/2015
0 0 1 0
02/03/2015
01/03/2015
4
Measurement
40
3 2
2
2
1
2 1 TO DO
2
DOING
29 30 BLOCKED
DONE
Possible impediment
5
Limit work in progress TO DO
DOING
BLOCKED
DONE
T1
T3
T2
T4
WIP = 2
Looking for a sustainable pace
5
Limit work in progress TO DO
DOING
BLOCKED
DONE
T1
T2 T4
Try and measure reulus results
T3
Change WIP WIP = 3
5 PENDING
Limit work in progress TO DO
DOING
BLOCKED
DONE
T5 T2 T6 T3 T7
T4 T8
WIP can be set in other columns DONE CRITERIA
WIP = 2
T1
Limit work in progress
5 PENDING
TO DO
DOING
BLOCKED
DONE
T2
T5
T3
T6 T4
WIP limit can be set in order to make the process more agile
T7 T8 DONE CRITERIA
WIP = 3
WIP = 2
T1
Limit work in progress
5 PENDING
TO DO
DOING
BLOCKED T2
T5
T6
T3
Limiting WIP in TO DO pushes to keep PENDING update T4
T7 T8 DONE CRITERIA
WIP = 3
WIP = 2
DONE
T1
6
Continuous improvement Plan
Act
Do
Check
Kanban Little law (why WIP should be limited) 看板
Little law 𝑊. 𝐼. 𝑃. 𝐿𝑒𝑎𝑑 𝑇𝑖𝑚𝑒 = 𝑇𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡
Little law 𝑊. 𝐼. 𝑃. 𝐿𝑒𝑎𝑑 𝑇𝑖𝑚𝑒 = 𝑇𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡 TO DO
DOING
T7
T2
T8
T5
DONE T1 WIP
T6
Lead Time
T3 T4
Throughput
Little law If WIP increases, so does Lead Time
+
đ?‘Š. đ??ź. đ?‘ƒ. + đ??żđ?‘’đ?‘Žđ?‘‘ đ?‘‡đ?‘–đ?‘šđ?‘’ = đ?‘‡đ?‘&#x;đ?‘œđ?‘˘đ?‘”â„Žđ?‘?đ?‘˘đ?‘Ą
Optimizing
Limiting WIP
-
đ?‘Š. đ??ź. đ?‘ƒ. đ??żđ?‘’đ?‘Žđ?‘‘ đ?‘‡đ?‘–đ?‘šđ?‘’ = đ?‘‡đ?‘&#x;đ?‘œđ?‘˘đ?‘”â„Žđ?‘?đ?‘˘đ?‘Ą + Increasing throughput
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-jesperboeg 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 aruiz@sistemas.frc.utn.edu.ar aruizdemendarozqueta@fundacionsadosky.org.ar skype: alvaro.rdm http://www.slideshare.net/AlvaroRuizdeMendaroz