{"id":20912,"date":"2020-01-20T11:26:00","date_gmt":"2020-01-20T17:26:00","guid":{"rendered":"https:\/\/blog.planview.com\/flow-time\/"},"modified":"2020-01-20T11:26:00","modified_gmt":"2020-01-20T17:26:00","slug":"flow-time","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/flow-time\/","title":{"rendered":"Flow Time \u2013 How Fast are We Delivering Business Value?"},"content":{"rendered":"
\n
\"Flow<\/div>\n<\/figure>\n
\n

Flow time doesn’t stop the clock just because the weekend rolls around. What flow time does do is help quantify the probability of completing x percent of work in so many days – Dominica DeGrandis, author of <\/em>Making Work Visible and Principal Flow Advisor at Tasktop <\/em><\/strong><\/p>\n<\/blockquote>\n

Every second counts in software delivery. That’s why <\/span>Flow Time <\/b>— the other “money metric” alongside <\/span>Flow Velocity <\/b><\/a>— is so important to IT and business leaders. A measure of speed and predictability, this metric tells you if your time to value is getting longer, helping to answer that frequently asked complaint, “Why are things taking so long?” Crucially, Flow Time<\/strong> enables you to be more accurate with your time to market forecasts, improving customer relations and retention, as well as supporting the business in its financial planning.<\/span><\/p>\n

<\/p>\n

Flow Time <\/b>helps clear up the confusion that lingers around time measurement in software delivery. In Lean manufacturing, there are two key metrics used for process improvement: lead and cycle time. The former measures the entire process, from the moment a customer first makes a request to completion (in the customer’s hands), and is the only time a customer cares about. The latter refers to the time it takes to complete a step in the process (such as development). The problem with these metrics in software delivery is they’re too ambiguous. Delivery lead time, for instance, is used by DevOps teams, referring to code-commit-to-deploy, measuring only the delivery pipeline on the “right side” of the value stream (the Release stage). <\/span><\/p>\n

Tasktop connects all the best-of-breed tools that help plan, build and software at scale, from ideation to operation and back through the customer feedback loop.<\/figcaption><\/figure>\n

Instead of developer-centric measure of time, we need a customer-centric measure like <\/span>Flow Time<\/b>, which is simply the elapsed time work takes to be completed from the moment it enters the value stream (approved by business stakeholders) to completion (end-user obtaining value from product), including both active and wait states, including weekends and off-hours. By analyzing trends over time, the metric can tell you if your acceleration investments are actually improving your time-to-value. <\/span>Flow Time<\/b> appeals to business and product owners as it can tell them how long a request takes to be completed once it has been approved, improving the relationship across the aisle. Flow Time<\/strong> enables you to be approximately right, instead of exactly wrong,. <\/span><\/p>\n

Flow Time in Action<\/h2>\n

Cut Waste in your Processes for Happier Employees<\/b><\/h3>\n

One software company observed that <\/span>Flow Time<\/b> for defects was too long. This directly impacted the <\/span>Flow Load<\/b>, with the organization identifying a high defect load across a three week period. <\/span>Flow Time<\/b> to repair was long and the happiness of both users and testers was at risk. The Value Stream Architect examined the underlying factors and found the bottleneck. They found the longest wait state was in “code review.” Working with the Engineering Lead, they decided to initiate a trial whereby they release low risk defects without a code review, while maintaining the process for more complex code changes. They then monitored the reopen rate to see if it had a negative before doing it at scale. Flow Velocity<\/strong> went up, Flow Load<\/strong> went down (ensuring teams didn’t burn out from context switching) and Flow Time<\/strong> was reduced (from 22 days to 11 days over a two-month period).<\/span><\/p>\n

\n

Flow Efficiency<\/a><\/p>\n<\/blockquote>\n