Date post: | 22-Apr-2015 |
Category: |
Business |
Upload: | adam-yuret |
View: | 65 times |
Download: | 0 times |
How Effort Metrics and Utilization Constrict the Flow of Value
“PRODUCTIVITY” IS KILLING US
[email protected]@AdamYuret
Who Is This Guy?!
Husband, Dad, Humanistic Lean Flow-‐Based Systems-‐Thinking Consultant at Context driven Agility (CDA)
Consulting, Sailor
@AdamYuret [email protected]
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]
!!!
● Prescriptive: Follow these rules and Agile hyper-‐productivity will be your reward.
@AdamYuret [email protected]
@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]
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
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]
!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]
● 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]
The Organization is Not a Machine, But an Organism, a Set of Human Relationships.
@AdamYuret [email protected]
In Order to Have High Autonomy, High Alignment is Needed. To have High Alignment, Strategic Clarity is Needed.
@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.
!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]
!● Failure Demand ● Silos:“Dumpster Teams” ●Overloaded Bottlenecks ●Deadline-‐Driven Development ● Exponential Delays
What Happens Without Slack?
@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 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]