My blog post on Flow Efficiency seems to have been well received and, most importantly, generated some pretty good discussion on Facebook regarding how to distinguish between work time versus waiting time for your actual work.
My blog post on Flow Efficiency seems to have been well received and, most importantly, generated some pretty good discussion on Facebook regarding how to distinguish between work time versus waiting time for your actual work.
One of the questions that working professionals get asked the most is “When will my request be completed?” In order to answer, we often look at lead time metrics to give a predictable answer. Looking at lead times over a period of time can give us a pretty high confidence level in setting delivery expectations. It is a strategy for predictability.
When we look at improving those lead times, we often focus on how to improve the active work we do for the requests we receive. We might improve test automation, implement code review process and/or continuous delivery pipelines. Those are all great endeavors. However, too many teams are not aware that the biggest way to improve the lead times for our work may actually be focusing on reducing the time we spend NOT working on our requests.
I was so excited and honored to get a speaking slot at DevOps Days Salt Lake City 2016. This was the first DevOps days here in Salt Lake City. It has been fun to be at the inaugural events in both Seattle and SLC. Check out the video and slides from this talk and let me know what you think.
© 2024 Everyday Kanban
Theme by Anders Noren — Up ↑