Unleash predictability by using Actionable Agile Metrics - 6 Key Learnings from Daniel S. Vacanti

Oct 26, 2026

A blog-style summary of Daniel S. Vacanti’s Actionable Agile Metrics for Predictability, focusing on practical metrics that improve decision-making in agile delivery. It explains definitions and purpose of cycle time, WIP, throughput, flow efficiency, and applies Little’s Law to relate WIP, throughput, and cycle time. It also covers cumulative flow diagrams (CFD) as an introspection tool to diagnose flow problems, emphasize arrivals and departures, and avoid projection and backlog inclusion pitfalls.

LanguageEnglish

CategoryResearch & Report

FormatPDF

Pages8

Reading Time20 min

AccessFree to download

Definitions

Cycle time, WIP, throughput, and flow efficiency

Little’s Law

Cumulative Flow Diagrams (CFD)

What CFDs show

Important properties and assumptions

Unleash predictability by using Actionable Agile Metrics (6 Key Learnings from Daniel S. Vacanti’s awesome book) [ontheagilepath.net](ontheagilepath.net/2015/04/unleash-predictability-by-using-actionable-agile-metrics-6-key-learnings-from-daniel-s)[/2015/04/unleash-predictability-by-using-actionable-agile-metrics-6-key-learnings-from-daniel-s](ontheagilepath.net/2015/04/unleash-predictability-by-using-actionable-agile-metrics-6-key-learnings-from-daniel-s)vacantis-awesome-book.html By Sebastian Radics I just finished reading the awesome book Actionable Agile Metrics for Predictability by Daniel S. Vacanti. For me a must read to get a deep insight in metrics for agile environments. With this blog post I summarize my highlights and key learnings. It’s just a fast overview and maybe provides already some ideas for you too, what to read next 􀁾 Predictability is of high importance! As an important question from our customers, we need to answer: When will it be done? “The only metrics that entrepreneurs should invest in are those that help them make decisions”( Eric Ries – e.g. on Vanity Metrics vs. Actionable Metrics ) “If a metric does not offer predictive power, capturing that metric is waste”(Troy Magennis) 1 – Definitions For me after a longer journey on the web a simple, speaking and coherent definition for cycle time, WIP, throughput and flow efficiency. FLOW: Flow is the movement and delivery of customer value through a process –(as we build for the customer) therefore our whole process should be oriented around optimizing flow. ACTIONABLE METRICS: The set of metrics that will suggest specific interventions that will result in the outcomes you are expecting ARRIVAL POINT: A specific point where a unit of work transforms from being just some arbitrary idea into being a legitimate work item that is to immediately be acted on and completed. DEPARTURE POINT: Defined as delivery to an actual end user or delivery to some other downstream team or process WORK: Any direct or indirect discrete unit of work of customer value is a candidate of work – named as work item (story, epic, feature, requirement, use case, enhancement,…) WORK IN PROGRESS – WIP: The total count of items currently being worked on; the number of items that we are working on at any given time; all discrete units of customer value that have entered a given process but have not exited. predictor of over overall system performance all work items between arrival point and departure point can be segmented across different types CYCLE TIME: The amount of elapsed time that a work item spends as Work in Progress. How long it takes each of those items to get through our process? How long to complete? When will it be done? Can also be used as a predictor of cost The amount of time it takes to get customer feedback Unpredictability lies it the time an items spends waiting to be worked on – that’s why it’sthe elapsed time that is important. THROUGHPUT: The amount of WIP completed per unit of time. How many of those items complete per unit of time? How many features am I going to get in the next release Understanding throughput at each step will help to identify the constraints in the workflow – find spots for process improvements FLOW EFFICIENCY: Ratio of total elapsed time that an item was actively worked on to the total elapsed time that it took for an item to complete. not actively worked = waiting to be pulled, waiting for feedback often a starting point of 15% flow efficiency LITTLE’S LAW: Average cycle time (CT) = Average WIP (WIP)/Average Throughput (TH) TH = WIP/CT WIP = CT*TH implies that increasing WIP leads to a higher CT and vice versa – check to reduce WIP to increase CT … in order to get stuff done faster, you need to work on less (on average) Average items in queue = Average Arrival Rate * Average Wait Time L = lambda * W L = average number of items in the queuing system l

FAQs

What is predictability in agile, and what question should teams answer?

Predictability is about understanding when work will be done. The text emphasizes the key customer question: when will it be completed?

How are cycle time, WIP, and throughput defined and used?

Cycle time is the elapsed time a work item spends as WIP. Throughput is how many WIP items complete per unit of time, and WIP counts items entered a process but not yet exited. Together they help identify constraints and opportunities to improve flow.

What is flow efficiency and why does waiting matter?

Flow efficiency is the ratio of actively worked time to total elapsed completion time. Waiting—such as being pulled or waiting for feedback—reduces active-work proportion, making elapsed time critical for uncovering unpredictability.

What are cumulative flow diagrams (CFD) used for, and what should be avoided?

CFDs visualize the flow metrics of cycle time, WIP, and throughput with cumulative arrivals and departures over time, supporting introspection rather than projection. The text advises avoiding backlog in CFDs and warns against drawing conclusions solely from the diagram’s appearance.

Oct 26, 2026

Upload by BAd apple