Busyness Agile Roots 2015

55
1

Transcript of Busyness Agile Roots 2015

Page 1: Busyness Agile Roots 2015

1

Page 2: Busyness Agile Roots 2015

“PRODUCTIVITY”  IS  KILLING  US

How  Effort  Metrics  and  Utilization  Constrict  the  Flow  of  Value  

[email protected]@AdamYuret

Page 3: Busyness Agile Roots 2015

Please  Turn  Your  Smartphones  ON!      #AgileRoots

@AdamYuret [email protected]

Page 4: Busyness Agile Roots 2015

Who  Is  This  Guy?!

Husband,  Dad,  Humanistic  Lean  Flow-­‐Based  Systems-­‐Thinking  Consultant  at  CDA  Consulting,  Sailor

@AdamYuret [email protected]

Page 5: Busyness Agile Roots 2015

My  Other  Interest

@AdamYuret [email protected]

Page 6: Busyness Agile Roots 2015

Learning

[email protected]@AdamYuret

Page 7: Busyness Agile Roots 2015

Seriously

[email protected]@AdamYuret

Page 8: Busyness Agile Roots 2015

Why  Are  We  Here?  

@AdamYuret [email protected]

Page 9: Busyness Agile Roots 2015

Oh  Right,  at  This  Session

Seek  to  understand  the  relationship  between  

utilization  and  flow.    

!

Discuss  some  alternatives  to  optimizing  for  

busyness.  

@AdamYuret [email protected]

Page 10: Busyness Agile Roots 2015

But  First,  an  Apology

@AdamYuret [email protected]

Page 11: Busyness Agile Roots 2015

Resource  Efficiency  Nightmare:  0%  Utilization

Waste@AdamYuret [email protected]

Page 12: Busyness Agile Roots 2015

~100%  Resource  Efficiency

@AdamYuret [email protected]

Page 13: Busyness Agile Roots 2015

“Resource”  Efficiency  Nightmare  0%  Utilization

@AdamYuret [email protected]

Page 14: Busyness Agile Roots 2015

That  Guy  Woke  Up  and  Said…

@AdamYuret [email protected]

Page 15: Busyness Agile Roots 2015

What  Can  Happen  When  “Agile”  Turns  Up?

@AdamYuret [email protected]

Page 16: Busyness Agile Roots 2015

Some  Agile  Adoption  Antipatterns

@AdamYuret [email protected]

Page 17: Busyness Agile Roots 2015

Focus  on  Compliance  to  the  Framework  Over  Value

@AdamYuret [email protected]

Page 18: Busyness Agile Roots 2015

Status  reporting  stand-­‐up  meetings

!

!

!• What  did  you  do  yesterday?    

!• What  will  you  do  today?    

!• Any  impediments?    

@AdamYuret [email protected]

Page 19: Busyness Agile Roots 2015

@AdamYuret [email protected]

Splitting  Teams  &  Creating  Dependencies  

Page 20: Busyness Agile Roots 2015

@AdamYuret [email protected]

Page 21: Busyness Agile Roots 2015

Limit  WIP/Visualize  Flow  of  Value

@AdamYuret [email protected]

Page 22: Busyness Agile Roots 2015

Limit  Work  In  Progress

Excessive  Work  in  Progress  (WIP)  is  the  enemy  of  flow.

@AdamYuret [email protected]

Page 23: Busyness Agile Roots 2015

If  We  Measure  Busyness,  We’ll  Create  More  Busyness.  

@AdamYuret [email protected]

Page 24: Busyness Agile Roots 2015

What  is  Failure  Demand?

Failure  Demand  is  demand  that  originates  

from  a  failure  to  have  done  something  right  in  

the  first  place.  

@AdamYuret [email protected]

Page 25: Busyness Agile Roots 2015

Typical  Example  of  Failure  Demand

@AdamYuret [email protected]

Page 26: Busyness Agile Roots 2015

Protecting  Silos  From  Failure  Demand  Creates  More…

@AdamYuret [email protected]

QA

Ops

Triage

Page 27: Busyness Agile Roots 2015

Value  Demand

@AdamYuret [email protected]

Page 28: Busyness Agile Roots 2015

Quantify  Value

@AdamYuret [email protected]

Page 29: Busyness Agile Roots 2015

Make  Strategic  Intent  Visible

@AdamYuret [email protected]

Page 30: Busyness Agile Roots 2015

Stephen  Bungay:  Directed  Opportunism  

@AdamYuret [email protected]

Page 31: Busyness Agile Roots 2015

The  Organization  is  Not  a  Machine,  But  an  Organism,  a  Set  of  Human  Relationships.    

-­‐Steven  Bungay

@AdamYuret [email protected]

Page 32: Busyness Agile Roots 2015

Study  This  Guy’s  Work

@AdamYuret [email protected]

Page 33: Busyness Agile Roots 2015

Principles  of  Product  Development  Flow

@AdamYuret [email protected]

Page 34: Busyness Agile Roots 2015

Utilization  &  Queuing  Theory

@AdamYuret [email protected]

Page 35: Busyness Agile Roots 2015

Rules  Are  Waste

@AdamYuret [email protected]

Page 36: Busyness Agile Roots 2015

Create  Slack

@AdamYuret [email protected]

Page 37: Busyness Agile Roots 2015

Three  Types  of  Slack

!

• Variability  Buffer  !

• Learning  

!

• Innovation

@AdamYuret [email protected]

Page 38: Busyness Agile Roots 2015

Slack  as  Variability  Buffer

@AdamYuret [email protected]

Page 39: Busyness Agile Roots 2015

Lean  Decision  Filter!

!

Flow  Trumps  Waste  

!

Value  Trumps  Flow

@AdamYuret [email protected]

Page 40: Busyness Agile Roots 2015

What  Does  That  Mean?  

Flow  Trumps  Waste

@AdamYuret [email protected]

Page 41: Busyness Agile Roots 2015

Lean  Decision  FilterValue  Trumps  Waste

Value  Trumps  Flow

@AdamYuret [email protected]

Page 42: Busyness Agile Roots 2015

Unit  Hour  Utilization!

!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.  

@AdamYuret [email protected]

Page 43: Busyness Agile Roots 2015

Slack  For  Learning

@AdamYuret [email protected]

Page 44: Busyness Agile Roots 2015

Read  a  Book

@AdamYuret [email protected]

Page 45: Busyness Agile Roots 2015

Capability  Balancing

@AdamYuret [email protected]

Page 46: Busyness Agile Roots 2015

Lean  Coffee

@AdamYuret [email protected]

Page 47: Busyness Agile Roots 2015

Slack  For  Innovation

@AdamYuret [email protected]

Page 48: Busyness Agile Roots 2015

What  Happens  Without  Slack?!

• Failure  Demand  

• Silos:“Pain-­‐Killer  Teams”  

• Overloaded  Bottlenecks  

• Deadline-­‐Driven  Development  

• Exponential  Delays

@AdamYuret [email protected]

Page 49: Busyness Agile Roots 2015

Play

@AdamYuret [email protected]

Page 50: Busyness Agile Roots 2015

A  Brief  Digression  Into  Metrics

@AdamYuret [email protected]

Page 51: Busyness Agile Roots 2015

Limit  WIP,  Eliminate  Task-­‐Tracking

@AdamYuret [email protected]

Page 52: Busyness Agile Roots 2015

Focus  On  Value

@AdamYuret [email protected]

Page 53: Busyness Agile Roots 2015

A  System  Is  Not  The  Sum  of  It’s  Parts

@AdamYuret [email protected]

Page 54: Busyness Agile Roots 2015

Books

@AdamYuret [email protected]

Page 55: Busyness Agile Roots 2015

THANK  YOU!

@AdamYuret Sayat.me/ayuret [email protected]