Cumulative Flow Diagram — Agile Techniques Library

What it is

A Cumulative Flow Diagram (CFD) is a stacked area chart that shows how work items accumulate in each workflow state over time. It is one of the most powerful diagnostic tools in Kanban.

Horizontal axis = time. Usually days or weeks.
Vertical axis = cumulative items. The total number of items that have entered each stage since tracking began.
Each band = workflow stage. "To Do," "In Progress," "In Review," "Done."
Width of band = WIP in that stage. A widening band means work is accumulating there.
Healthy CFD shows smooth, roughly parallel lines. This indicates stable WIP and predictable flow.

The top line shows total work entered. The bottom line of the "Done" band shows total work completed. The vertical distance between any two lines is the WIP in that stage.

When to use it

Review the CFD weekly, either in standups or retrospectives. It takes 30 seconds to scan and reveals more about flow health than a full status report.

Use it to spot trends before they become crises. A band that has been widening for two weeks is a bottleneck forming in real time.

Key concepts

Bands

Each coloured band represents a workflow stage. The area of the band shows how many items were in that stage at each point in time.

Widening / Narrowing

A band that gets wider over time means work is entering that stage faster than it is leaving. A narrowing band means the stage is draining.

Flat Lines

A flat top line means no new work is entering the system. A flat boundary between two bands means no work is moving between those stages. Both are signals to investigate.

Approximate Lead Time

The horizontal distance between the "To Do" entry line and the "Done" completion line at any vertical point gives a rough visual indication of lead time.

Do not expect perfectly parallel lines. Some variation is normal. What matters is the trend: are the bands stable over weeks, or is one consistently widening?

Worked Example: Reading a Real CFD

Scenario: A 6-person team has been tracking their CFD for 4 weeks. Their workflow has 4 stages: "To Do," "In Progress," "In Review," "Done."

Week 1: All bands are narrow and roughly parallel. 5 items per week flowing through smoothly.
Week 2: The "In Review" band starts widening. Items are moving slowly through code review.
Week 3: "In Review" band is now 40% wider than "In Progress." A clear bottleneck.
Week 4: Team investigates. Discovery: one senior developer is the only code reviewer, and they are away 2 days per week. Solution: train a second reviewer.

Without the CFD, the team would have felt busy (coding new features) but not realised their real constraint was code review capacity. The CFD made it visible in 2 weeks instead of learning about it from frustrated POs a month later.

Step-by-Step: Interpreting a CFD

Look at the overall shape. Do lines run parallel (healthy) or is one band widening (bottleneck)?
Scan the vertical distance between lines. A large gap between "In Progress" and "In Review" means items are piling up waiting to be reviewed.
Check the slopes. A steep slope means work is moving fast through that stage. A flat slope means work is stuck.
Look for trends over 2+ weeks. One bad day is noise; a band widening for 2 weeks is a signal.
Identify which band is the bottleneck. The widest band is where your constraint lives. That's where to focus improvement effort.

Metrics Extracted from a CFD

Work In Progress (WIP): The vertical distance between any two lines at a given time shows how many items are currently in that stage. If "In Progress" shows 15 items when WIP limit is 10, you are overloaded.

Throughput: How fast is the top line moving up? A steep slope means you are completing lots of work. A flat slope means nothing is reaching "Done."

Lead Time: The horizontal distance from entry to completion. A wide CFD (left to right) means long lead times. A narrow CFD means quick delivery.

Cycle Time per Stage: How long does an item spend in "In Progress" vs "In Review"? Draw a vertical line at a point and measure the width of each band. If "In Review" is much wider, that stage is slow.

Team Problems a CFD Reveals

Review bottleneck: "In Review" band widens while "In Progress" drains. Not enough reviewers, or review is too slow.
Testing backlog: "In Test" band widens. QA is understaffed, test environment is unstable, or tests are too slow.
Too much WIP: All bands are very wide. Team is starting too much work before finishing what's in progress. Solution: lower WIP limits.
Blocked work: One band widens suddenly then flattens. A blocker (missing dependencies, tool outage, stakeholder approval) is holding items hostage.
Uneven distribution: Some bands are narrow and fast; others are wide and slow. Team is not balanced across stages.

CFD vs Burndown Chart

Burndown: Shows how many items are left (one line going down). Good for sprints; hides flow problems.

CFD: Shows how items move through stages (multiple bands). Good for continuous flow; reveals bottlenecks. A CFD shows *where* work is getting stuck; a burndown just shows *how much* is left.

Common pitfalls

Pitfall	Why it hurts	What to do instead
Only looking when things go wrong	Misses gradual degradation of flow.	Review the CFD every week as a habit.
Not understanding band meanings	Misdiagnoses which stage is the problem.	Label bands clearly and ensure the team knows what each colour represents.
Comparing across teams	Different workflows produce different shapes.	Use CFDs for internal trend analysis only.
Ignoring the diagram	The team flies blind to flow problems.	Make the CFD visible on a dashboard or wall.
Failing to act on patterns	Data without action is waste.	When a band widens for two weeks, discuss it in the retrospective and run an experiment.

NZ context

Cumulative Flow Diagrams are built into the tools most New Zealand teams already use: Jira, Azure DevOps, and GitHub Projects. Despite this, many teams never look at them.

Set a recurring calendar reminder to review the CFD before standup. In five minutes you can confirm flow is healthy, or identify a column that needs the team's attention that day.

Career level guidance

Senior: Learn to read a CFD at a glance. Be the person in the retrospective who can say, "The 'In Review' band has widened 30% over the last three sprints. That's our bottleneck." Bring the CFD to planning meetings to justify WIP limit adjustments.

Test Lead: Monitor the "In Test" band specifically. If it widens while "In Progress" narrows, the test stage is absorbing pressure. Use the CFD to demonstrate testing capacity constraints to leadership with objective data rather than anecdote.