Cumulative Flow Diagram
What is a Cumulative Flow Diagram?
A cumulative flow diagram is a stacked area chart that shows how many work items are in each stage of a workflow over time, revealing work in progress, throughput, cycle time trends and bottlenecks.
Updated November 2026 · 5 min read
A team board shows where work is today. It does not show whether things are getting better or worse, or where problems have been building for weeks. A cumulative flow diagram, often called a CFD, adds the missing time dimension. Each day, it records how many items have reached each stage of the workflow and stacks those counts as colored bands. Because the counts are cumulative, the bands never shrink: an item that reaches Done stays counted there, so the chart shows the total history of the work rather than a daily snapshot. The shape of the bands then tells a story: whether work is flowing smoothly, where it is piling up and whether the team is starting more than it finishes.
Cumulative flow diagrams come from queueing theory and manufacturing, and they became a standard tool in software delivery through the Kanban method. Most agile tools now generate them automatically. For engineering managers, delivery leads and agile coaches, a CFD is one of the fastest ways to check the health of a workflow, provided people know how to read it.
Definition of Cumulative Flow Diagram
A cumulative flow diagram is a chart in which the horizontal axis shows time, the vertical axis shows the cumulative count of work items and each colored band represents a workflow state, so that the vertical distance between bands shows work in progress and the horizontal distance approximates time in the system.
It is a core Kanban chart, visualizes the relationship described by Little's Law and supports flow metrics analysis.
How to Read a CFD
The top line of each band shows the total number of items that have reached that state or any later one. The Done band grows over time as work is completed.
The vertical thickness of a band at any date shows how many items are in that state. The distance between the line for In Progress and the line for Done shows total work in progress.
The slope of the Done line shows throughput. A steeper slope means more items are finishing each day.
The horizontal distance between the start line and the Done line approximates average cycle time for items finishing around that date. These readings are approximations based on averages. They are most reliable when work is stable and items are of broadly similar size.
Common Patterns
Parallel bands with steady slopes indicate stable, predictable flow.
A band that widens over time shows a bottleneck, since work is entering that state faster than it leaves.
Flat stretches in the Done line show periods when nothing was delivered, often around holidays, release freezes or major incidents.
A top band rising much faster than the Done band means more work is being started or requested than finished. Bands that disappear and reappear usually mean workflow states were renamed or items were moved backward, which is worth checking before drawing conclusions.
Importance of Cumulative Flow Diagrams in Delivery Management
CFDs make bottlenecks visible early. A band that slowly widens can be spotted weeks before delays show up in delivery dates.
They show work in progress and throughput on one chart, so teams can see whether starting more work is helping or just lengthening delivery.
They also support honest conversations with stakeholders. A chart showing intake outpacing delivery explains slipping dates more clearly than any status report. Because the chart is generated from the board itself, it reflects what actually happened rather than what was planned or reported.
Cumulative Flow Diagrams and Financial Management
Widening bands represent growing amounts of partly finished work, which is investment not yet returning value.
A rising gap between requests and completions signals that demand exceeds funded capacity, informing decisions about prioritization or staffing.
Flat periods in the Done line can be linked to their causes, such as freezes or incidents, to estimate their cost.
Comparing CFDs before and after process or tooling changes shows whether those investments improved flow.
Common Challenges
Many people find CFDs hard to read at first. A short explanation of what each part shows helps teams and stakeholders use them.
The chart is only as good as the board behind it. Cards that are not moved promptly, or workflow states that change often, distort the picture. Teams should also avoid comparing CFDs across teams with very different workflows, since band widths depend on how states are defined.
Including backlog items that may never be worked on can make the top band dominate the chart and hide what is happening in delivery.
How to Use a Cumulative Flow Diagram
Using a CFD involves defining clear workflow states, keeping the board current, generating the chart automatically and reviewing it regularly for patterns.
The chart is most useful as a prompt for questions, which the team then investigates using item-level data.
Setting Up the Chart
Define a small number of meaningful workflow states, such as Ready, In Progress, In Review, Testing and Done.
Keep the board current so that each item's movement is recorded on the right day.
Choose a time window, often the last 60 to 90 days, that shows trends without too much noise. Consider excluding the backlog band or showing it separately, so that the delivery stages remain readable.
Acting on What It Shows
When a band widens, look at the items in that state, find what is holding them up and consider a WIP limit for that stage.
When intake outpaces completion, review the backlog and agree on what to stop or defer.
Use the chart alongside a cycle time scatterplot, which shows how individual items are affected. Review the CFD in regular team meetings, so patterns are discussed while they are still small, and share it with stakeholders who depend on the team's delivery.
Examples of Cumulative Flow Diagrams in Practice
The examples below show cumulative flow diagrams in practice.
Both use illustrative figures. The first finds a testing bottleneck, and the second explains slipping dates.
In each, the shape of the chart pointed to a specific action.
Finding a Testing Bottleneck
A team's CFD shows the Testing band growing from 4 items to 19 over six weeks, while the Done line flattens.
Investigation shows that a shared test environment is available only a few hours a day.
The team funds a second environment and sets a limit of 6 items in Testing, and the band returns to its normal width within a month. The Done line steepens as well, showing that throughput recovered once testing stopped holding work back.
Explaining Slipping Dates
A product manager is asked why a release planned for March is now expected in May.
The CFD shows that new items have been added to the release at twice the rate items are being completed.
Stakeholders agree to move 15 lower-priority items to a later release, and the original scope is delivered in early April.
Conclusion
A cumulative flow diagram is a stacked area chart that shows how many items are in each workflow state over time. The thickness of bands shows work in progress, the slope of the Done line shows throughput and horizontal distances approximate cycle time.
In delivery and engineering operations, CFDs make bottlenecks visible early, show work in progress and throughput together and support honest conversations about delivery. Defining clear states, keeping boards current, reviewing the chart regularly and acting on widening bands help teams keep work flowing.
Related terms
Kanban
Visualizing work, limiting work in progress and improving the flow.
Little's Law
Work in progress equals throughput times cycle time, on average.
Flow Metrics
Measures of how much work flows, how fast and where it gets stuck.
WIP Limits
Caps on work in progress so teams finish work before starting more.