Cumulative Flow Diagram (CFD): How to Read It [2026]
A. Togay Koralturk, Best-Selling PMP Author
Last updated on July 29, 2026
10 min read
Most agile charts tell you how much is left; a cumulative flow diagram tells you where the work is stuck. By stacking the number of items in each stage of the workflow over time, it turns a team's flow into a set of colored stripes whose shape reveals bottlenecks, growing work in progress, and stalled delivery at a glance. This guide explains the cumulative flow diagram in full — what it is, an example, how to read WIP, cycle time, and throughput from it, what the patterns mean, and how it is tested on the PMP and CAPM exams.
What is a cumulative flow diagram?
A cumulative flow diagram (CFD) is a stacked-area chart that shows the number of work items in each state of a workflow — such as To Do, In Progress, and Done — over time. Time runs along the horizontal axis and the cumulative count of items runs up the vertical axis, with each workflow state drawn as its own colored band stacked on top of the others.
The whole picture is the flow of work through the system. The total height of the stack at any point is the total number of items in the project; the bottom band grows as work is completed, and the top bands shrink as items move through. Because it shows every state at once — not just what is done or what is left — a CFD is the go-to chart for Kanban teams, who use it to watch the flow of work and spot where it is getting stuck rather than just how much remains.
The bands of a CFD
A CFD has one band per workflow state, stacked so the total is always the full scope. In a simple three-state workflow, the bands from bottom to top are Done, In Progress, and To Do. To make it concrete, take a support team that starts an eight-day stretch with 40 work items on a three-column board — 32 waiting in To Do and 8 already In Progress. Here is how its board flows over those eight days:
By day eight, the support team's board reads directly off the chart: the green Done band has climbed to 36 items completed, the blue In Progress band is about 8 items thick, and the grey To Do band has shrunk to 6 — and because the total height rose from 40 to 50, you can see that 10 new items arrived during the eight days. The In Progress band held a steady thickness the whole time, which means the team kept its work in progress under control while it burned through the queue.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
How to read a cumulative flow diagram
A CFD encodes three of the most important flow metrics in its geometry. Once you know where to look, the chart reads like an instrument panel:
| What you look at | What it tells you |
|---|---|
| Thickness of the In Progress band | Work in progress (WIP) — how many items are being worked on at once |
| Horizontal gap between a band's top and the Done line | Approximate cycle time — how long items take to flow through |
| Slope of the Done band | Throughput — the rate at which work is being finished |
| The bands staying parallel | Stable, healthy flow |
So an In Progress band that suddenly gets thicker means WIP is growing, a wider horizontal gap means items are taking longer to finish, and a flatter Done band means throughput has dropped. Reading our support team's chart, the In Progress band is about 8 items thick — that is its WIP — and it finished 36 items over 8 days, a throughput of roughly 4.5 items a day. Those two numbers are linked by Little's law, which says average cycle time ≈ WIP ÷ throughput, so this team's items take about 8 ÷ 4.5 ≈ 1.8 days to flow from start to done. These are the same cycle time and throughput metrics Kanban teams track directly, made visible in one picture, which is why a CFD is often the fastest way to see that flow is degrading before the numbers are even calculated.
Healthy vs. problem patterns
The shape of a CFD is a quick diagnosis of the workflow's health. A healthy CFD has bands that rise together in steady, roughly parallel stripes — work arrives, flows, and finishes at balanced rates. When the bands stop being parallel, something is wrong, and the pattern points to what:
- A widening In Progress band is the classic warning sign: work in progress is piling up faster than it is being finished, which means a bottleneck downstream.
- A flattening Done band means throughput has stalled — little or nothing is reaching done, often the flip side of the bottleneck above.
- A widening To Do band at the top means new work is arriving faster than the team can deliver it — scope or demand is outrunning capacity.
Here is what the first of those looks like. Take the same support team in a later eight-day stretch, again starting with 40 items, but this time with a bottleneck in play:
Read against the healthy chart above: the In Progress band has swollen from 8 to 26 items in eight days, while Done managed only 10 — and most of that in the first two days, before the blockage took hold. The team pulled work at nearly its old pace; it just stopped coming out the other side.
The Kanban maxim these patterns teach is "stop starting, start finishing," and a CFD makes the need for it visible before a deadline does.
CFD vs. burndown chart
A cumulative flow diagram and a burndown chart both track progress over time, but they show different things. A burndown chart plots a single line of work remaining; a CFD plots every workflow state as a stacked band. The difference in what they reveal:
| Cumulative flow diagram | Burndown chart | |
|---|---|---|
| Shows | Items in every state over time | Work remaining over time |
| Reveals bottlenecks? | Yes — a widening band | No |
| Flow metrics | WIP, cycle time, throughput | Pace toward zero |
| Best for | Kanban and continuous flow | Time-boxed sprints |
In short, a burndown answers "will we finish on time?" while a CFD answers "where is our work, and is it flowing smoothly?" A burndown is ideal for a fixed-scope sprint; a CFD is the better tool for continuous-flow work, where spotting and clearing bottlenecks matters more than a sprint countdown. Many teams use a burndown for the sprint and a CFD to keep an eye on the flow underneath it.
Cumulative flow diagrams on the PMP® and CAPM® Exams
Because agile and hybrid approaches are a large part of the PMP exam, the cumulative flow diagram appears as a Kanban flow tool. The facts to lock in: a CFD stacks work items by state over time; the thickness of the In Progress band is WIP; the horizontal gap approximates cycle time; and the slope of the Done band is throughput.
The situational questions give you a CFD pattern to interpret — most often a widening In Progress band — and reward the flow-based response: limit WIP and finish work in progress rather than starting more. The distinction from a burndown, which cannot show bottlenecks, is also fair game. The CAPM tests the same reading skills a little more directly. Our PMP Complete Study Guide, the most complete on the market, covers the Kanban flow metrics and how to read them.
PMP Practice Question: Cumulative Flow Diagram
On a Kanban team's cumulative flow diagram, the In Progress band has widened steadily for two weeks while the slope of the Done band has flattened; the total height of the stack has grown at its usual rate. A stakeholder reviewing the chart concludes the team is simply overloaded and proposes bringing in two contractors to add capacity.
What should the team do first?
a) Add the contractors, so the extra capacity can work through the accumulated In Progress items.
b) Stop pulling new items, set work-in-progress limits, and finish the items already in flight until the Done slope recovers.
c) Re-estimate the remaining backlog and reset stakeholder expectations for the delivery date.
d) Split the board into finer-grained columns so the chart shows more precisely where items are sitting.
Correct answer: B.
Rationale: The chart has already made the diagnosis: a widening In Progress band with a flattening Done slope is the signature of work being started faster than it is finished — a bottleneck — and the steady total height rules out a surge in incoming scope. When the diagnosis is that clear, the first move is the flow fix: cap work in progress and finish what is in flight, which is what restores the Done slope. Adding contractors treats capacity as the constraint before flow has been fixed, and new people tend to raise WIP further while they onboard; re-estimating the backlog re-forecasts the symptom without touching its cause; and finer-grained columns improve visibility the team does not currently lack, since the two signals already say where the problem lives. To drill this kind of agile flow scenario, work through our PMP practice exams or, at the entry level, our CAPM practice exams.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
Frequently asked questions
What is a cumulative flow diagram?
A cumulative flow diagram (CFD) is a stacked-area chart that shows the number of work items in each state of a workflow — such as To Do, In Progress, and Done — over time. Each state is a colored band, and the total height is the total number of items. It is a Kanban tool used to visualize the flow of work and spot bottlenecks.
How do you read a cumulative flow diagram?
Read three things from the geometry: the thickness of the In Progress band is your work in progress (WIP); the horizontal distance between a band's top and the Done line is roughly the cycle time; and the slope of the Done band is throughput. Bands that stay parallel indicate healthy flow, while a widening band signals a problem.
What does a widening band on a CFD mean?
A widening In Progress band means work in progress is growing faster than items are being finished — a bottleneck. It usually appears alongside a flattening Done band, showing throughput has stalled. The Kanban response is to stop starting new work and focus on finishing what is in progress to clear the bottleneck.
What is the difference between a cumulative flow diagram and a burndown chart?
A burndown chart plots a single line of work remaining over time and is ideal for a fixed-scope sprint. A cumulative flow diagram plots every workflow state as a stacked band, so it reveals work in progress, cycle time, throughput, and bottlenecks — which a burndown cannot show. A CFD is better for continuous, Kanban-style flow.
What does a healthy cumulative flow diagram look like?
A healthy CFD has bands that rise together in steady, roughly parallel stripes, meaning work arrives, flows, and finishes at balanced rates. The In Progress band stays a stable thickness (controlled WIP), the Done band climbs at a consistent slope (steady throughput), and no band suddenly widens or flattens.
Is the cumulative flow diagram on the PMP exam?
Yes. Agile and hybrid approaches are a large part of the PMP exam, and the cumulative flow diagram is a Kanban flow tool it tests. You should be able to read WIP from the In Progress band, cycle time from the horizontal gap, and throughput from the Done slope, and recognize that a widening In Progress band signals a bottleneck.
Is the cumulative flow diagram on the CAPM exam?
Yes. The CAPM covers agile flow tools including the cumulative flow diagram, usually a little more directly than the PMP — often defining it or asking what a band or pattern represents. Because the CAPM is scenario-based, you should still be ready to interpret a simple CFD in a short situation.
Burnup Chart in Agile: Example & vs. Burndown [2026]
A burnup chart plots work completed and total scope as two lines, so scope stays visible. An example, how to read it, burnup vs. burndown, and the PMP exam.
Agile Release Planning: Process & Levels [2026]
Agile release planning maps features across sprints toward a release. The planning levels, date vs. scope, how to forecast with velocity, and PMP exam tips.
Minimum Viable Product (MVP): Meaning & Examples [2026]
A minimum viable product (MVP) is the simplest usable version of a product, built to learn from customers. MVP vs. prototype, examples, and PMP exam tips.
