4. #onetimeatAgileCamp
11 minutes before interrupted
25 minutes to regain the point before interruption
9% margin of error rate (uninterrupted)
15% margin of error rate (interrupted)
5. #onetimeatAgileCamp
Arrive at 9 am Monday morning… Read emails, get coffee, warm up
9:30 am… Begin a complex task
9:41 am… Interruption, “How was your weekend?”
9:51 am… Get back at your complex task
10:16 am… finally back in your “groove”
That’s 35 minutes of lost time by a single interruption!
In the first 76 minutes, only 11 minutes of
productive task work
23. #onetimeatAgileCamp
• If you don’t use WIP limits, start!
• Let WIP limits be a creative friendly constraint
• Limit WIP to the team’s capacity
• Remember: High WIP = high wait times because
other items sit waiting for attention
Take charge of WIP
24. #onetimeatAgileCamp
• Make work visible
• Yes, even the “drive-by” requests
• Understand the source of all work done by the
team and what slows FLOW
Measure All Work
Poll Title: What are some of the more common "thieves of time" for you and your teams?
https://www.polleverywhere.com/free_text_polls/fcHqWoJrb1tgMK6
“Can you help me?” – we are eager to help teammates and don’t want to let them down
Optimize for fun
Everything always takes longer than we think it should
Yes is easier than No
We overload ourselves and our teams
Multi-tasking is NOT a thing
It is simply switching tasks
We cannot switch tasks efficiently
Leads to more mistakes
What is it that steals time away from our teams?
When demand exceed capacity
Take on more than what is possible
Possibly due to the reasons before
Won’t take so long
Couldn’t possibly impact my sprint
Boss asked me
Biggest impact to FLOW is too much WIP
FLOW = fast and smooth movement of work across the VALUE Stream
Value Stream = activities done from beginning to end for a product/service in order to provide business value.
Improve FLOW:
Reduce batch size
Build in quality
Unfinished work is waste
To improve your flow, start by making the work visible
Honor WIP limits
Look for Traffic Jams – understand the cause, change behaviors
Defined as NOT PLANNED – typically takes us away from our goal
Most common in IT that I hear about is Support Work
We take time and effort to lay out the best plans
Set goals and intend to deliver value to our customer
Constant interruptions create context switching
Delays planned work
Make it visible
Start visualizing dependencies
Work closely with teams where there are dependencies
What about SCRUM teams? Should we setup WIP limits?
William Edwards Deming was an American engineer, statistician, professor, author, lecturer, and management consultant.
Poll Title: Impact of Hidden and Unplanned Work
https://www.polleverywhere.com/surveys/k0mp6uN2Q