ManagementManagement
and Changeand Change
avoiding the rocksavoiding the rocks
Rodrigo Yoshima
Rodrigo Yoshima
Software Developer since 1994
RUP (1999 – now)
Agile (2003 – now)
Kanban (2009 – now)
LKU Trainer and Coach
Creator of FlowKaizen and Wiphub
Sailing addicted
WIP Limits
Introduced
More predictable
System
WIP Limits
Introduced
Capacity
Time
Status Quo
New Status Quo
Capacity
20th century
Time
Status Quo
New Status Quo
Capacity
20th century
“Revolution”
Time
Status Quo
New Status Quo
Capacity
20th century
“Revolution”
Time
Status Quo
New Status Quo
Capacity
20th century
“Revolution”
Time
Status Quo
New Status Quo
21st century
Capacity
KAIKAKU
20th century
“Revolution”
Time
Status Quo
New Status QuoKAIZEN
21st century
“Evolution”
Capacity
KAIKAKU
20th century
“Revolution”
Time
Status Quo
New Status QuoKAIZEN
21st century
“Evolution”
J-Curve of ChangeJ-Curve of Change
Virginia Satir’s Change Process Model
“be like water...”
Management Tool
Demand
Management Tool
Demand
Bug Tracking
Bugs
Management Tool
Demand
Bug Tracking
Bugs
32
168
Management Tool
Demand
Bug Tracking
Bugs
32
168
Dissatisfaction
?????
Management Tool
Demand
Bug Tracking
Bugs
32
168
What would
you do?
?????
Management Tool
Demand
Bug Tracking
Bugs
32
168
The real problem:
- HIGH WIP
?????
TEST!DEV!
Kanban:
Like Water...
People's identity and
self-esteem
Management Tool
Demand
Bug Tracking
Bugs
32
168
How do you
feel about these
numbers?
?????
Visual Management
Visual Management
Visual Management
Visual Management
Visual Management
WIP
CommandandControl
Anarchy
$ 300/pound
$ 600/pound
$ 2.500/pound
Example - Boeing 777
Engineer Supervisor Program Manager
Sprint
Backlog
Pronto
Em Andamento
The “Boring” Demand
Sprint
Backlog
Pronto
Em Andamento
You will take care
of the boring demand
on this Sprint.
Sprint
Backlog
Pronto
Em Andamento
Remark: The Cost-of-delay
was sensitive
Sprint
Backlog
Pronto
Em Andamento
Bad Performance
Sprint
Backlog
Pronto
Em Andamento
Bad Performance
What would you do?
(5)
Next Done
(5)
In progress
(5)
Next Done
(5)
In progress
We need
explicit
policies
Manager
The policy is up to you.
I just need it defined.
(5)
Next Done
(5)
In progress
We need
explicit
policies
Manager
New policy:
After doing 3 pink tickets you will select
the next team member to do the 3 tickets
WIP
Decentralized
Control
People's identity and
self-esteem
Decentralization Level
“People don't resist change.
They resist being changed.”
Peter Senge
IOS
Android
C++
Java
Ruby Rails
IOS
Android
C++
Java
Ruby Rails
Module 1 Module 2 Module 3 Module 4 ... Module 17
...
Let's do Scrum...
...
...
...
...
...
...
Process Perspective:
Everything's OK!!!
Management Perspective:
It sucks!!!
Module 1 Module 2 Module 3 Module 4 ... Module 17
Work-in-progress (WIP)
...
CHAOS!!!!
...
What would
you do?
Module 1ule 2
Module 1ule 2
Module 1ule 2
Module 1ule 2
To do Doing Done
Module 1ule 2
To do Doing Done
Module 1ule 2
To do Doing Done
Module 1ule 2
To do Doing Done
Module 1ule 2
To do Doing Done
Tribal Behavior!!!
Tribal Behavior
People's identity and
self-esteem
Decentralization Level
Module 1ule 2
To do Doing Done
Module 1ule 2
To do Doing Done
Problemas:
Tribal Behavior
Low Utilization
(slack)
Module 1
(OK)
To do Doing Done
Module 3
Module 2
To do Doing Done
Module 1
(OK)
To do Doing Done
Module 3
Module 2
To do Doing Done
Module 1
(OK)
To do Doing Done
Module 3
Module 2
To do Doing Done
Tribal Behavior:
Solved with “Time”
Specialization
WIP
Decentralized
Control
Headcount
Risk
Tecnical
Practices
Capacity
Alocation
Variability
in Flow
Process
Policies
Utilization
Specialization
WIP
Decentralized
Control
Obrigado!
Rodrigo Yoshima
blog.aspercom.com.br
@rodrigoy

Management and Change - avoiding the rocks