The document discusses lean tools like value stream mapping and Kanban. It provides examples of using value stream mapping to visualize and analyze the flow of work in a software development process and identify areas for improvement like reducing wait times. Kanban is introduced as a tool that uses visual cues and limits on work-in-progress to control flow and facilitate continuous improvement through collaborative experiments. Examples are given of using a Kanban board to visualize different scenarios and how work would flow through the process.

1. Some Useful Lean Tools:
Value Stream Mapping and Kanban
Incontro DevOps Italia,
Bologna 21 feb 2014
1
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2013

2. About me
Roberto Bettazzoni
Agile Coach
eXtreme Programming Trainer
!
roberto.bettazzoni@agile42.it
linkedin.com/in/robertobettazzoni
@bettazzoni
agile42 The Agile train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
agile42 | |We advise,Coaching Company

3. Lean Thinking
3
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

4. (無理: muri)
Overburden
do not overload your
People
4
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2010.

5. Unnecessary
Variations
(斑: mura) keep the Flow
Even
5
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2010.

6. Wasteful
Activities
(無駄: muda)
remove non value adding
Activities
6
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2010.

7. Value Stream Map
7
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2013

8. Value Stream Map: from concept to cash
Request
!
8
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

9. Value Stream Map: from concept to cash
Request
!
Approval
!
Tech
Reqts
!
Analysis
!
Design
!
Review
!
Code
!
Test
!
Deploy
!
Approval
!
9
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

10. Value Stream Map: from concept to cash
Request
5
days
Approval
1
day
Tech
Request
8
days
Analysis
10
days
Design
10
days
Review
1
day
Code
15
days
Test
10
days
Deploy
2
days
Approval
1
day
10
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

11. Value Stream Map: from concept to cash
Request
5
days
20d
Approval
1
day
15d
Tech
Request
8
days
5d
Review
1
day
5d
Deploy
2
days
10d
Approval
1
day
10d
Analysis
10
days
5d
Design
10
days
2X
2d
Code
15
days
5d
Test
10
days
2X
agile42 | The Agile Coaching Company
11
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

12. Value Stream Map: from concept to cash
Request
5
days
0.2
FTE
20d
Approval
1
day
1
FTE
15d
Tech
Request
8
days
0.5
FTE
5d
Review
1
day
0.5
FTE
5d
Deploy
2
days
1
FTE
10d
Approval
1
day
1
FTE
10d
Analysis
10
days
0.5
FTE
5d
Design
10
days
0.5
FTE
2X
2d
Code
15
days
1.5
FTE
5d
Test
10
days
0.5
FTE
2X
agile42 | The Agile Coaching Company
12
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

13. Value Stream Map: from concept to cash
Request
5
days
0.2
FTE
20d
Approval
1
day
1
FTE
15d
Tech
Request
8
days
0.5
FTE
5d
Review
1
day
0.5
FTE
Total time elapsed = 186 days
Deploy
2
days
1
FTE
Value added Time = 78 days!
Wait Time = 106 days!
Value/Total Ratio = 42%
10d
Approval
1
day
1
FTE
10d
Analysis
10
days
0.5
FTE
5d
Design
10
days
0.5
FTE
2X
2d
Code
15
days
1.5
FTE
5d
Test
10
days
0.5
FTE
5d
Value added Time = 99 days!
Wait Time = 87 days!
Value/Total Ratio = 53%
2X
agile42 | The Agile Coaching Company
13
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

14. Value Stream Map - Bug Fixing
Error
report
16 sept.
2 days
Bug
Open
0.2 hr
8 days
agile42 | The Agile Coaching Company
Status
Urgent
Web
UI
Fix
Server
Code
Fix
3 hr
1.5 hr
12 hr
2 days
3 days
Tests
Deploy
4 hr
1.5 hr
3 days
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

15. Value Stream Map - Bug Fixing
Error
report
16 sept.
Bug
Open
0.2 hr
Status
Urgent
Web
UI
Fix
Server
Code
Fix
3 hr
1.5 hr
12 hr
Tests
Deploy
4 hr
1.5 hr
Value added Time = 22 hr
Wait Time = 15 days
2 days
5 days
2 days
3 days
3 days
Value/Total = 18 %
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

16. Value Stream Map - Manufacturing
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

17. Pull Principle
Allows self-organizing teams to pull in work and knowledge as needed in order to
deliver valuable quality software
17
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.

18. Kanban
18
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2013

19. kanban
1950
agile42| |We advise, train and coach companies building software
agile42 The Agile Coaching Company
Kanban
2004
www.agile42.com | All rights reserved. Copyright © 2007 -- 2012.
www.agile42.com | All rights reserved. Copyright © 2007 2009.

20. Kanban Foundational Principles
•Start with what you do now
•Agree to pursue incremental, evolutionary change
•Initially respect the current roles, responsibilities and job
titles
•Encourage acts of leadership at all levels, from individuals
contributors to senior management
agile42 | The Agile Coaching Company
www.agile42.com |
20
All rights reserved. Copyright © 2007 - 2012.

21. Kanban’s 6 core practices...
1.Visualize your actual workflow
2.Limit WIP
3.Measure & Optimize Flow
4.Define explicit policies
5.Implement feedback loops
6.Improve collaboratively, using safe-to-fail experiments
agile42 | The Agile Coaching Company
www.agile42.com |
21
All rights reserved. Copyright © 2007 - 2012.

22. agile42 | The Agile Coaching Company
www.agile42.com |
22
All rights reserved. Copyright © 2007 - 2012.

23. Scenario 1 – one piece flow
Next
Backlog
A
2
Dev
3
Ongoing
In production :o)
Test
B
G
C
F
H
J
M
D
I
L
K
E
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

24. Scenario 1 – one piece flow.
Dev
Next
Backlog
2
3
Ongoing
In production :o)
Test
C
G
D
A
B
F
H
J
M
I
L
K
E
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

25. Scenario 2 – Deployment problem
Backlog
A
PO
Next
2
Dev
3
Ongoing
In production :o)
Test
B
G
C
F
H
J
M
D
I
L
K
E
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

26. Scenario 2 – Deployment problem
Backlog
PO
Dev
Next
2
3
Ongoing
C
Test
A
D
G
In production :o)
B
F
H
J
M
I
L
K
E
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

27. Scenario 2 – Deployment problem
Backlog
PO
Dev
Next
2
3
Ongoing
C
G
D
In production :o)
Test
A
B
F
H
J
M
I
L
K
E
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

28. Scenario 2 – Deployment problem
Backlog
PO
2
D
F
H
M
3
Ongoing
In production :o)
Test
C
G
J
Dev
Next
A
!?
B
I
L
K
E
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

29. Scenario 2 – Deployment problem
Backlog
PO
Dev
Next
2
3
Ongoing
!?
G
In production :o)
Test
A
D
E
F
H
J
M
B
C
I
L
K
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

30. Scenario 2 – Deployment problem
Backlog
PO
Next
2
Dev
3
Ongoing
In production :o)
Test
A
G
D
E
F
H
J
M
B
C
I
L
K
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

31. Scenario 2 – Deployment problem
Backlog
PO
Next
2
Dev
3
Ongoing
In production :o)
Test
A
G
D
F
H
J
M
E
B
C
I
L
K
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

32. Scenario 2 – Deployment problem
Backlog
PO
3
Ongoing
In production :o)
Test
H
A
B
E
F
M
2
D
G
J
Dev
Next
C
I
L
K
agile42 | The advise, train andCompany
We Agile Coaching coach companies building software
www.agile42.com |
All rights reserved. Copyright © 2007 - 2012.
2009.

33. Kanban
It is not a framework, neither a process, but a tool.
33
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2013

34. Thank you
Roberto Bettazzoni
roberto.bettazzoni@agile42.com
@bettazzoni
34
agile42 | The Agile Coaching Company
www.agile42.com |
All rights reserved. Copyright © 2007 - 2013