Invisible work competes with known work. Invisible work blindsides people, leaving teams unaware of mutually critical information. Married to this problem, is the question, how does one plan for, or allocate capacity for the invisible? It’s tough to analyze something you can’t see. Incognito work doesn’t show up well in metrics. Hidden work steals time away from important priorities. Hidden work also masks dependencies across siloed teams and increases total department work-in-progress, which lengthens cycle time.

The State of DevOps 2016 report considers the amount of unplanned work a measure of quality. Data shows that high performers spend 11% more time working on planned work vs. unplanned work — because the more unplanned work, the less time exists to create and deliver value work. Bringing visibility to and measuring unplanned work is a necessary capability for any organization serious about implementing DevOps in order to reduce risk and improve performance.

Risk accumulates from work delivered late and started late. One solution is to expose the hidden work thieves that steal your time away from planned work. This talk exposes five thieves of time that prevent teams from delivering value quick, and provides actionable steps for how to see and how to measure unplanned work.

You must be a Member to view this post and you are currently not logged in.

You can either log in below or sign up here.