SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
1.
How
Effort
Metrics
and
Utilization
Constrict
the
Flow
of
Value
“PRODUCTIVITY”
IS
KILLING
US
Adam.Yuret@gmail.com@AdamYuret
2.
Please
Turn
Your
Smartphones
ON!
#SDEC14
@AdamYuret Adam.Yuret@gmail.com
3.
Who
Is
This
Guy?!
Husband,
Dad,
Humanistic
Lean
Flow-‐Based
Systems-‐
Thinking
Consultant
at
CDA
Consulting,
Sailor
@AdamYuret Adam.Yuret@gmail.com
4.
My
Two
Favorite
People
Adam.Yuret@gmail.com@AdamYuret
5.
My
Other
Interest
@AdamYuret Adam.Yuret@gmail.com
8.
Why
Are
We
Here?
@AdamYuret Adam.Yuret@gmail.com
9.
Seek
to
understand
the
relationship
between
utilization
and
flow.
!
Discuss
some
alternatives
to
optimizing
for
busyness.
Oh
Right,
at
This
Session
@AdamYuret Adam.Yuret@gmail.com
10.
But
First,
an
Apology
@AdamYuret Adam.Yuret@gmail.com
14.
That
Guy
Woke
Up
and
Said…
@AdamYuret Adam.Yuret@gmail.com
15.
What
Can
Happen
When
“Agile”
Turns
Up?
@AdamYuret Adam.Yuret@gmail.com
16.
What
Are
Legalistic
Frameworks?
@AdamYuret Adam.Yuret@gmail.com
17.
!
!
!
● Prescriptive:
Follow
these
rules
and
Agile
hyper-‐
productivity
will
be
your
reward.
@AdamYuret Adam.Yuret@gmail.com
18.
!
!
!
● Castigate
when
the
rules
are
not
followed.
@AdamYuret Adam.Yuret@gmail.com
19.
!
!
!
● Take
pride
in
following
those
rules.
@AdamYuret Adam.Yuret@gmail.com
20.
!
!
!
● Measure
success
based
on
compliance
to
the
rules.
@AdamYuret Adam.Yuret@gmail.com
21.
!
!
!
● Blame
failure
on
lack
of
strict
adherence
to
the
rules.
@AdamYuret Adam.Yuret@gmail.com
22.
Some
Agile
Adoption
Antipatterns
@AdamYuret Adam.Yuret@gmail.com
23.
Focus
on
Compliance
to
the
Framework
Over
Value
@AdamYuret Adam.Yuret@gmail.com
24.
!
!
!
● What
did
you
do
yesterday?
!
● What
will
you
do
today?
!
● Any
impediments?
@AdamYuret Adam.Yuret@gmail.com
Status
reporting
stand-‐up
meetings
25.
@AdamYuret Adam.Yuret@gmail.com
Splitting
Teams
&
Creating
Dependencies
27.
Limit
WIP/Visualize
Flow
of
Value
@AdamYuret Adam.Yuret@gmail.com
28.
Excessive
Work
in
Progress
(WIP)
is
the
enemy
of
flow.
By
setting
limits
to
work
in
progress
we
can
enable
greater
flow.
@AdamYuret Adam.Yuret@gmail.com
Limit
Work
In
Progress
29.
If
We
Measure
Busyness,
We’ll
Create
More
Busyness.
@AdamYuret Adam.Yuret@gmail.com
31.
Traditional
management
thinking
treats
all
demand
as
equal.
There
is
work
to
be
done
and
people
who
do
the
work.
Failure
Demand
is
demand
that
originates
from
a
failure
to
have
done
something
right
in
the
first
place.
Not
all
productivity
is
desirable.
What
is
Failure
Demand?
@AdamYuret Adam.Yuret@gmail.com
32.
Typical
Example
of
Failure
Demand
@AdamYuret Adam.Yuret@gmail.com
33.
!
Agile
team
produces
growing
velocity
but,
as
they
speed
features
out
the
door,
bugs
are
introduced.
When
bugs
come
into
the
backlog
they’re
assigned
velocity
points.
It
is
theoretically
possible,
therefore,
to
have
a
team
producing
zero
value
while
increasing
velocity
fixing
bugs.
Product
Development
Example
@AdamYuret Adam.Yuret@gmail.com
34.
Pitfalls
of
Ignoring
Failure
Demand
@AdamYuret Adam.Yuret@gmail.com
36.
● In
order
to
keep
developers
typing
at
maximum
utilization,
we
create
teams
to
absorb
the
failure
demand
caused
by
developers
typing
at
maximum
utilization.
These
teams
often
have
unlimited
WIP
and
must
consume
an
unending
stream
of
demand.
This
also
hides
the
problems
from
the
people
creating
them.
“Pain-‐Killer
Teams”
@AdamYuret Adam.Yuret@gmail.com
52.
Flow
Trumps
Waste
What
Does
That
Mean?
@AdamYuret Adam.Yuret@gmail.com
53.
Value
Trumps
Flow
Lean
Decision
Filter
@AdamYuret Adam.Yuret@gmail.com
54.
!
In
general,
reliability
is
the
ability
of
a
person
or
system
to
perform
and
maintain
its
functions
in
routine
circumstances
as
well
as
in
hostile
or
unexpected
circumstances.
In
the
case
of
emergency
services,
reliability
looks
at
actual
incident
history
data
to
measure
historical
performance
in
accordance
with
adopted
performance
measures.
!
Forecasting
With
Data
@AdamYuret Adam.Yuret@gmail.com
55.
!
!
A
unit
unavailable
for
response
provides
no
service
to
the
community.
The
unit
may
be
out
of
service
for
a
multitude
of
reasons
including;
another
emergency
response,
training,
maintenance,
etc.
If
a
unit
is
not
available
80%
of
the
time,
it
is
not
reasonable
to
expect
the
unit
to
perform
at
the
80th
percentile.
!
….
Poor
availability
negatively
influences
response
times.
Unit
Hour
Utilization
@AdamYuret Adam.Yuret@gmail.com
56.
Slack
For
Learning
@AdamYuret Adam.Yuret@gmail.com
70.
Team
Testimonials
“Limiting
our
work
in
progress
so
we
focused
on
completion
was
a
big
deal
for
us.
It
felt
better
to
have
one
story
than
five
tasks
in
progress.”
–Lead
Developer
!
“Development
was
very
helpful
with
testing,
volunteering
to
clear
impediments
and
helping
us
test
during
the
sprint.”
–Lead
Tester
!
“The
team
is
excited
and
helping
each
other
out
during
stand-‐up
and
working
together
in
the
War
Room”
–PM/SM
@AdamYuret Adam.Yuret@gmail.com
71.
Focus
On
Value
@AdamYuret Adam.Yuret@gmail.com
72.
A
System
Is
Not
The
Sum
of
It’s
Parts
@AdamYuret Adam.Yuret@gmail.com