Download - Busyness geekfest

Transcript
Page 1: Busyness geekfest

How  Effort  Metrics  and  Utilization  Constrict  the  Flow  of  Value  

“PRODUCTIVITY”  IS  KILLING  US

[email protected]@AdamYuret

Page 2: Busyness geekfest

Please  Turn  Your  Smartphones  ON!      #Geekfest

@AdamYuret [email protected]

Page 3: Busyness geekfest

Who  Is  This  Guy?!

Husband,  Dad,  Humanistic  Lean  Flow-­‐Based  Systems-­‐Thinking  Consultant  at  Context  driven  Agility  (CDA)  

Consulting,  Sailor

@AdamYuret [email protected]

Page 4: Busyness geekfest

My  Two  Favorite  People

[email protected]@AdamYuret

Page 5: Busyness geekfest

My  Other  Interest

@AdamYuret [email protected]

Page 6: Busyness geekfest

Learning

[email protected]@AdamYuret

Page 7: Busyness geekfest

Learning

[email protected]@AdamYuret

Page 8: Busyness geekfest

Why  Are  We  Here?  

@AdamYuret [email protected]

Page 9: Busyness geekfest

Discuss  how  the  relentless  pursuit  of  productivity  is  constraining  our  ability  to  effectively  deliver  value  to  our  customers  and  businesses.    !Discuss  some  alternatives  to  this  approach  of  optimizing  for  busyness.  

Oh  Right,  at  This  Session

@AdamYuret [email protected]

Page 10: Busyness geekfest

But  First,  an  Apology

@AdamYuret [email protected]

Page 11: Busyness geekfest

Resource  Efficiency  Nightmare:  0%  Utilization

Waste@AdamYuret [email protected]

Page 12: Busyness geekfest

~100%  Resource  Efficiency

@AdamYuret [email protected]

Page 13: Busyness geekfest

“Resource”  Efficiency  Nightmare  0%  Utilization

@AdamYuret [email protected]

Page 14: Busyness geekfest

That  Guy  Woke  Up  and  Said…

@AdamYuret [email protected]

Page 15: Busyness geekfest

What  Can  Happen  When  “Agile”  Turns  Up?

@AdamYuret [email protected]

Page 16: Busyness geekfest

What  Are  Legalistic  Frameworks?

@AdamYuret [email protected]

Page 17: Busyness geekfest

!!!

● Prescriptive:  Follow  these  rules  and  Agile  hyper-­‐productivity  will  be  your  reward.  

@AdamYuret [email protected]

Page 18: Busyness geekfest

!!!

● Castigate  when  the  rules  are  not  followed.  

@AdamYuret [email protected]

Page 19: Busyness geekfest

!!!

● Take  pride  in  following  those  rules.  

@AdamYuret [email protected]

Page 20: Busyness geekfest

!!!

● Measure  success  based  on  compliance  to  the  rules.  

@AdamYuret [email protected]

Page 21: Busyness geekfest

!!!

● Blame  failure  on  lack  of  strict  adherence  to  the  rules.  

@AdamYuret [email protected]

Page 22: Busyness geekfest
Page 23: Busyness geekfest

Some  Agile  Adoption  Antipatterns

@AdamYuret [email protected]

Page 24: Busyness geekfest

@AdamYuret [email protected]

Page 25: Busyness geekfest

Focus  on  Compliance  to  the  Framework  Over  Value

@AdamYuret [email protected]

Page 26: Busyness geekfest

!!!●What  did  you  do  yesterday?    !

●What  will  you  do  today?    !

● Any  impediments?    

@AdamYuret [email protected]

Status  reporting  stand-­‐up  meetings

Page 27: Busyness geekfest

@AdamYuret [email protected]

Splitting  Teams  &  Creating  Dependencies  

Page 28: Busyness geekfest

@AdamYuret [email protected]

Page 29: Busyness geekfest

Limit  WIP/Visualize  Flow  of  Value

@AdamYuret [email protected]

Page 30: Busyness geekfest

Excessive  Work  in  Progress  (WIP)  is  the  enemy  of  flow.  By  setting  limits  to  work  in  progress  we  can  enable  greater  flow.  

@AdamYuret [email protected]

Limit  Work  In  Progress

Page 31: Busyness geekfest

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

@AdamYuret [email protected]

Page 32: Busyness geekfest

Little’s  Law

@AdamYuret [email protected]

Page 33: Busyness geekfest

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 [email protected]

Page 34: Busyness geekfest

Typical  Example  of  Failure  Demand

@AdamYuret [email protected]

Page 35: Busyness geekfest

!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 [email protected]

Page 36: Busyness geekfest

Pitfalls  of  Ignoring  Failure  Demand

@AdamYuret [email protected]

Page 37: Busyness geekfest

Protecting  Silos  From  Failure  Demand  Creates  More…

@AdamYuret [email protected]

Page 38: Busyness geekfest

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

“Dumpster  Teams”

@AdamYuret [email protected]

Page 39: Busyness geekfest

Value  Demand

@AdamYuret [email protected]

Page 40: Busyness geekfest

Quantify  Value

@AdamYuret [email protected]

Page 41: Busyness geekfest

Make  Strategic  Intents  Visible

@AdamYuret [email protected]

Page 42: Busyness geekfest

Clear  Priorities  Are  Essential  To  Distributed  Decision-­‐Making

@AdamYuret [email protected]

Page 43: Busyness geekfest

Stephen  Bungay:  Directed  Opportunism  

@AdamYuret [email protected]

Page 44: Busyness geekfest

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

@AdamYuret [email protected]

Page 45: Busyness geekfest

In  Order  to  Have  High  Autonomy,  High  Alignment  is  Needed.  To  have  High  Alignment,  Strategic  Clarity  is  Needed.  

@AdamYuret [email protected]

Page 46: Busyness geekfest

Study  This  Guy’s  Work

@AdamYuret [email protected]

Page 47: Busyness geekfest

Principles  of  Product  Development  Flow

@AdamYuret [email protected]

Page 48: Busyness geekfest

Utilization  &  Queuing  Theory

@AdamYuret [email protected]

Page 49: Busyness geekfest

Rules  Are  Waste

@AdamYuret [email protected]

Page 50: Busyness geekfest

Create  Slack

@AdamYuret [email protected]

Page 51: Busyness geekfest

!●Variability  Buffer  !

● Learning  !

● Innovation

Three  Types  of  Slack

@AdamYuret [email protected]

Page 52: Busyness geekfest

Slack  as  Variability  Buffer

@AdamYuret [email protected]

Page 53: Busyness geekfest

!!

Flow  Trumps  Waste  !

Value  Trumps  Flow

Lean  Decision  Filter

@AdamYuret [email protected]

Page 54: Busyness geekfest

Flow  Trumps  WasteWhat  Does  That  Mean?  

@AdamYuret [email protected]

Page 55: Busyness geekfest

Value  Trumps  FlowLean  Decision  Filter

@AdamYuret [email protected]

Page 56: Busyness geekfest

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

!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 [email protected]

Page 57: Busyness geekfest

Slack  For  Learning

@AdamYuret [email protected]

Page 58: Busyness geekfest

Read  a  Book

@AdamYuret [email protected]

Page 59: Busyness geekfest

Capability  Balancing

@AdamYuret [email protected]

Page 60: Busyness geekfest

Lean  Coffee

@AdamYuret [email protected]

Page 61: Busyness geekfest

Slack  For  Innovation

@AdamYuret [email protected]

Page 62: Busyness geekfest

!● Failure  Demand  ● Silos:“Dumpster  Teams”  ●Overloaded  Bottlenecks  ●Deadline-­‐Driven  Development  ● Exponential  Delays

What  Happens  Without  Slack?

@AdamYuret [email protected]

Page 63: Busyness geekfest

Play

@AdamYuret [email protected]

Page 64: Busyness geekfest

A  Brief  Digression  Into  Burndowns

@AdamYuret [email protected]

Page 65: Busyness geekfest

Limit  WIP,  Eliminate  Task-­‐Tracking

@AdamYuret [email protected]

Page 66: Busyness geekfest

Team  Testimonials“Limiting  our  work  in  progress  so  we  focused  on  completion  was  a  big  deal  for  us.  It  felt  better  to  have  1  story  than  5  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 [email protected]

Page 67: Busyness geekfest

Focus  On  Value

@AdamYuret [email protected]

Page 68: Busyness geekfest

A  System  Is  Not  The  Sum  of  It’s  Parts

@AdamYuret [email protected]

Page 69: Busyness geekfest

Books

@AdamYuret [email protected]

Page 70: Busyness geekfest

THANK  YOU!

@AdamYuret Sayat.me/ayuret [email protected]