6. G RO U P D I S C U S S I O N
Lower costs
Raising productivity
7. What do people look at?
Business Return
Managers Cost
Developers # of features implemented
Testers # of bugs found
Integrators # of integration errors
Customers How it helps them – pain
of use
8. • How can I improve
our time to market?
• How can I improve
visibility?
• How do I get
predictability?
• How do I measure my
success so I can both
ensure it as well as
know I’ve achieved it?
29. Concept
Regional Coordinators New
Business Leaders Requirements Customers
Trainers & Educators
Product Managers Consumption
Customer
Business Product Champion(s)
Capabilities
Support
Product Related
Software Software Shared
Product Release Components
Shared
Product Related Components
Development
The Continuous Flow of Technology
Solution Delivery
30. Principles for Lean-Agile Management
1. Visibility - See the Value
Stream
2. Flow
Limit Work to Capacity
Manage Work in
Progress
Remove Delays
3. Build in Quality
thinking
points
31. Approv
Request Reqts Sign Off Analysis
e
Design Review Code Test Deploy
1. Identify the actions taken in the value stream
32. Approv
Request Reqts Sign Off Analysis
e
0.5 hrs 8 hrs 160 hrs 8 hrs 100 hrs
Design Review Code Test Deploy
120 hrs 2 hrs 280 hrs 240 hrs 8 hrs
1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
33. Approv
Request Reqts Sign Off Analysis
0.5 hr avg
e 60 hrs avg 1 hr avg 40 hrs avg
.1 hr avg
0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs
Design Review Code Test Deploy
40 hrs avg 2 hrs avg 80 hrs avg 40 hrs avg 3 hrs avg
120 hrs 2 hrs 280 hrs 240 hrs 8 hrs
1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
34. Approv
Request Reqts Sign Off Analysis
0.5 hr avg
e 60 hrs avg 1 hr avg 40 hrs avg
320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs
0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs
80 hrs
Design Review Code Test Deploy
40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg
160 hrs
120 hrs 2 hrs 280 hrs 240 hrs 8 hrs
1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
35. Approv
Request Reqts Sign Off Analysis
0.5 hr avg
e 60 hrs avg 1 hr avg 40 hrs avg
320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs
0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs
80 hrs
Design Review Code Test Deploy
40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg
160 hrs
120 hrs 2 hrs 280 hrs 240 hrs 8 hrs
20% rejected 65% defective
Repeat 1X Repeat 3X
1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required
27 September 2010
36. Approv
Request Reqts Sign Off Analysis
0.5 hr avg
e 60 hrs avg 1 hr avg 40 hrs avg
320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs
0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs
80 hrs
Design Review Code Test Deploy
40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg
160 hrs
120 hrs 2 hrs 280 hrs 240 hrs 8 hrs
20% rejected 65% defective
Repeat 1X Repeat 3X
509 hrs
PCE = = 14.9%
1. Identify the actions taken in the value stream 3433 hrs
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required Avg Time Worked
6. Calculate Process Cycle Efficiency: Total Cycle Time
37. Approv
Request Reqts Sign Off Analysis
0.5 hr avg
e 60 hrs avg 1 hr avg 40 hrs avg
320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs
0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs
80 hrs
Design Review Code Test Deploy
40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg
160 hrs
120 hrs 2 hrs 280 hrs 240 hrs 8 hrs
20% rejected 65% defective
Repeat 1X Repeat 3X
509 hrs
PCE = = 14.9%
1. Identify the actions taken in the value stream 3433 hrs
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required Avg Time Worked
6. Calculate Process Cycle Efficiency: Total Cycle Time
38. Approv
Request Reqts Sign Off Analysis
0.5 hr avg
e 60 hrs avg 1 hr avg 40 hrs avg
320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs
0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs
80 hrs
Design Review Code Test Deploy
40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg
160 hrs
120 hrs 2 hrs 280 hrs 240 hrs 8 hrs
20% rejected 65% defective
Repeat 1X Repeat 3X
509 hrs
PCE = = 14.9%
3433 hrs
1. Identify the actions taken in the value stream
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required Avg Time Worked
6. Calculate Process Cycle Efficiency: Total Cycle Time
39. Which gives a better return?
Eliminating
Getting better
delays between
at what you do
what you do
40. Approv
Request
Request Approve Reqts Sign Off
Sign Off Analysis
Analysis
0.5 hr avg
e
.1 hr avg 60 hrs avg 1 hr avg 40 hrs avg
320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs
0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs
80 hrs
Design
Design Review
Review Code Test Deploy
Deploy
40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg
160 hrs
120 hrs 2 hrs 280 hrs 240 hrs 8 hrs
20% rejected 65% defective
65% defective
Repeat 1X Repeat 3X
Repeat 3X
509 hrs
PCE = = 14.9%
1. Identify the actions taken in the value stream 3433 hrs
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required Avg Time Worked
Avg Time Worked
6. Calculate Process Cycle Efficiency: Total Cycle Time
Total Cycle Time
41. kanban by eliminating delays
improves quality and
by managing WIP
lowers cost
42. Approv
Request Reqts Sign Off Analysis
0.5 hr avg
e 60 hrs avg 1 hr avg 40 hrs avg
320 hrs .1 hr avg 80 hrs 320 hrs 80 hrs
0.5 hrs 8 hrs 160 hrs 8hrs 100 hrs
80 hrs
Design Review Code Test Deploy
40 hrs avg 2 hrs avg 80 hrs 80 hrs avg 80 hrs 40 hrs avg 80 hrs 3 hrs avg
160 hrs
120 hrs 2 hrs 280 hrs 240 hrs 8 hrs
20% rejected 65% defective
Repeat 1X Repeat 3X
509 hrs
PCE = = 14.9%
1. Identify the actions taken in the value stream 3433 hrs
2. Calculate calendar time for each action
3. Calculate time actually worked on the action
4. Identify time between actions
5. Identify any loop backs required Avg Time Worked
6. Calculate Process Cycle Efficiency: Total Cycle Time
44. ‐‐ Product Managers ‐‐
Working on approval
Waiting for approval
.1
320 8
visual management for WIP
45. Waiting for approval
320
Working on approval
.1
8
Ready for Requirements
80
‐‐ Product Managers ‐‐
visual management for WIP
46. Waiting for approval
320
Working on approval
.1
8
Ready for Requirements
Requirements
80 160
60
‐‐ Product Managers ‐‐
visual management for WIP
47. Waiting for approval
320
Working on approval
.1
8
Ready for Requirements
Requirements
60
‐‐ Product Managers ‐‐
Ready for sign off
80 160 320
visual management for WIP
48. ‐‐ Product Managers ‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
Ready for Requirements
Working on approval
Waiting for approval
Ready for sign off
Requirements
Sign Off
.1 60 1
320 8 80 160 320 8
visual management for WIP
49. Waiting for approval
320
Working on approval
.1
8
Ready for Requirements
Requirements
60
‐‐ Product Managers ‐‐
Ready for sign off
80 160 320
Sign Off
1
8
Ready for Analysis
Analysis
80 100
40
Ready for Design
Design
40
Ready for Review
80 120 160
Review
2
2
Ready for Code
80
80 280 Code
Ready for Test
Test
80 240
40
Ready for Deplay
80
Deplay
8
3
Done
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
visual management for WIP
50. Waiting for approval
320
Working on approval
.1
8
Ready for Requirements
Requirements
60
‐‐ Product Managers ‐‐
Ready for sign off
80 160 320
Sign Off
1
8
Ready for Analysis
Analysis
80 100
40
Ready for Design
Design
40
Ready for Review
80 120 160
Review
2
2
Ready for Code
80
80 280 Code
Ready for Test
Test
80 240
40
Ready for Deplay
80
Deploy
8
3
Done
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
visual management for WIP
51. Kanban suggests
limit # of items
Lean suggests limit
TIME between steps being worked on in
each step
time
size of queue
52. G RO U P D I S C U S S I O N
Different Ways Available
•Add more resource
•Manage resources
•Improve process
53. Waiting for approval
Working on approval
Ready for Requirements
Requirements
‐‐ Product Managers ‐‐
Ready for sign off
Sign Off
Ready for Analysis
Analysis
Ready for Test Specification
Write Test Specification
Ready for Design
Design
Ready for Review
Review
Ready for Code
Code
Ready for Test
Test
Ready for Deplay
Deploy
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
Done
visual management for WIP
54. Waiting for approval
Working on approval
Ready for Requirements
Requirements
‐‐ Product Managers ‐‐
Ready for sign off
Sign Off
Ready for Analysis
Analysis
Ready for Test Specification
Write Test Specification
Ready for Design
Design
Ready for Review
Review
Ready for Code
Code
Ready for Test
Test
Ready for Deplay
Deploy
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Development Team ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
Done
visual management for WIP
55. Feedback comes in all shapes
and sizes
Dev to self
Dev to self
Dev/QA to
Customer
designer
Dev to
Test to
dev
Deploy to
Analysis Design Code Test Integrate customer
Requirements Define Test Show
Across teams
Specifications customer
Customer
to Dev
Customer to Analyst, et. Al.
56. MMF
MMF
Teams work on
Split MMF
their part
according to team
Teams work on this for
Development teamsintegrating
Eventually split
accordingseveral interations
them together
to components
57. G RO U P D I S C U S S I O N
Teams pull from backlog
work may be over several
sprints
Each team pulls
independently
Coordinate with Scrum-of-
Scrums
Integration happens:
after each team is done
with their entire part of
feature
58. MMF
Split MMF
into sub-features After one iteration, teams
integrate their components
Development teams split
Teams work on
according to components
their part
59. G RO U P D I S C U S S I O N
Teams pull from backlog
functionality done after
each sprint
forces team coordination
can manage across teams
If change metrics to be
feature throughput
then Scrum-of-Scrums
may work because all are
being measured the same
way
60. See the Value Stream
LEAN THINKING
Visual Controls Workflow = Process
Release Planning Minimize Impediments