productivity is killing us sdec14
DESCRIPTION
Gave a talk in WInnipeg, here's the deck. :-)TRANSCRIPT
How Effort Metrics and Utilization Constrict the Flow of Value
“PRODUCTIVITY” IS KILLING US
[email protected]@AdamYuret
Please Turn Your Smartphones ON! #SDEC14
@AdamYuret [email protected]
Who Is This Guy?!
Husband, Dad, Humanistic Lean Flow-‐Based Systems-‐Thinking Consultant at CDA Consulting, Sailor
@AdamYuret [email protected]
My Two Favorite People
[email protected]@AdamYuret
My Other Interest
@AdamYuret [email protected]
Learning
[email protected]@AdamYuret
Seriously
[email protected]@AdamYuret
Why Are We Here?
@AdamYuret [email protected]
Seek to understand the relationship between utilization and flow. !Discuss some alternatives to optimizing for busyness.
Oh Right, at This Session
@AdamYuret [email protected]
But First, an Apology
@AdamYuret [email protected]
Resource Efficiency Nightmare: 0% Utilization
Waste@AdamYuret [email protected]
~100% Resource Efficiency
@AdamYuret [email protected]
“Resource” Efficiency Nightmare 0% Utilization
@AdamYuret [email protected]
That Guy Woke Up and Said…
@AdamYuret [email protected]
What Can Happen When “Agile” Turns Up?
@AdamYuret [email protected]
What Are Legalistic Frameworks?
@AdamYuret [email protected]
!!!
● Prescriptive: Follow these rules and Agile hyper-‐productivity will be your reward.
@AdamYuret [email protected]
Some Agile Adoption Antipatterns
@AdamYuret [email protected]
Focus on Compliance to the Framework Over Value
@AdamYuret [email protected]
!!!●What did you do yesterday? !
●What will you do today? !
● Any impediments?
@AdamYuret [email protected]
Status reporting stand-‐up meetings
@AdamYuret [email protected]
Splitting Teams & Creating Dependencies
@AdamYuret [email protected]
Limit WIP/Visualize Flow of Value
@AdamYuret [email protected]
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
If We Measure Busyness, We’ll Create More Busyness.
@AdamYuret [email protected]
Little’s Law
@AdamYuret [email protected]
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]
Typical Example of Failure Demand
@AdamYuret [email protected]
!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]
Pitfalls of Ignoring Failure Demand
@AdamYuret [email protected]
● 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 [email protected]
Value Demand
@AdamYuret [email protected]
Quantify Value
@AdamYuret [email protected]
Make Strategic Intents Visible
@AdamYuret [email protected]
Clear Priorities Are Essential To Distributed Decision-‐Making
@AdamYuret [email protected]
Stephen Bungay: Directed Opportunism
@AdamYuret [email protected]
The Organization is Not a Machine, But an Organism, a Set of Human Relationships.
-‐Steven Bungay
@AdamYuret [email protected]
In Order to Have High Autonomy, High Alignment is Needed. To have High Alignment, Strategic Clarity is Needed.
@AdamYuret [email protected]
Study This Guy’s Work
@AdamYuret [email protected]
Principles of Product Development Flow
@AdamYuret [email protected]
Utilization & Queuing Theory
@AdamYuret [email protected]
Rules Are Waste
@AdamYuret [email protected]
Create Slack
@AdamYuret [email protected]
Slack as Variability Buffer
@AdamYuret [email protected]
Flow Trumps WasteWhat Does That Mean?
@AdamYuret [email protected]
Value Trumps FlowLean Decision Filter
@AdamYuret [email protected]
!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 [email protected]
!
!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]
Slack For Learning
@AdamYuret [email protected]
Read a Book
@AdamYuret [email protected]
Capability Balancing
@AdamYuret [email protected]
Lean Coffee
@AdamYuret [email protected]
Slack For Innovation
@AdamYuret [email protected]
@AdamYuret [email protected]
!● Failure Demand ● Silos:“Pain-‐Killer Teams” ●Overloaded Bottlenecks ●Deadline-‐Driven Development ● Exponential Delays
What Happens Without Slack?
@AdamYuret [email protected]
Play
@AdamYuret [email protected]
65
Total&Story&Lead&Time&&30&days&
Development&Time&5&Days&(~&15%)&
Tes<ng&Time&2&Days&
Defect&Rework&&2&Days&
Release&/&DevOps&Time&1&Day&
Blocked&and&Wai<ng&Time&9&Days&
Wai<ng&Time&3&Days&
Wai<ng&Time&8&Days&
Courtesy Troy Magennis focusedobjective.com
66
Total&Story&Lead&Time&&30&days&
Development&Time&5&Days&(~&15%)&
Tes<ng&Time&2&Days&
Defect&Rework&&2&Days&
Release&/&DevOps&Time&1&Day&
Blocked&and&Wai<ng&Time&9&Days&
Wai<ng&Time&3&Days&
Wai<ng&Time&8&Days&
Courtesy Troy Magennis focusedobjective.com
67
Total&Story&Lead&Time&&30&days&
Story&/&Feature&Incep9on&5&Days&
Wai9ng&in&Backlog&25&days&
System&Regression&Tes9ng&&&Staging&&5&Days&
Wai9ng&for&Release&Window&5&Days&
“Ac9ve&Development”&30&days&
Pre&Work&&30&days&
Post&Work&10&days&
Courtesy Troy Magennis focusedobjective.com
68
Total&
Story&
Lead&
Time&
&
30&
days&
Story&/&Feature&Incep9on&
5&Days&
Wai9ng&in&Backlog&
25&days&
System&Regression&Tes9ng&&&Staging&&
5&Days&
Wai9ng&for&Release&Window&
5&Days&
“Ac9ve&Development”&
30&days&
Pre&
Work&
&
30&
days&
Post&
Work&
10&
days&
9&days&(70&total)&
approx&13%&
Courtesy Troy Magennis focusedobjective.com
A Brief Digression Into Metrics
@AdamYuret [email protected]
Limit WIP, Eliminate Task-‐Tracking
@AdamYuret [email protected]
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 [email protected]
Focus On Value
@AdamYuret [email protected]
A System Is Not The Sum of It’s Parts
@AdamYuret [email protected]
Books
@AdamYuret [email protected]
THANK YOU!
@AdamYuret Sayat.me/ayuret [email protected]