Cumulative Flow Diagram
A stacked-area chart of work items in each stage over time — the single most informative chart in lean and Kanban flow management.
Definition
A Cumulative Flow Diagram (CFD) is a time-series chart that shows, for every day, the cumulative count of work items in each stage of a workflow — Backlog, In Progress, Review, Done, etc. — stacked from bottom to top. The horizontal distance between two adjacent bands gives you the cycle time; the vertical distance gives you the WIP. A well-read CFD tells you more about a team's flow in 30 seconds than a week of standup reports ever will.
What It Shows
- Throughput: the slope of the Done band.
- WIP: the vertical thickness of any "in flight" band.
- Cycle time: the horizontal distance from when an item entered In Progress to when it became Done.
- Bottlenecks: bands that widen over time (work piling up before a stage).
- Scope creep: the top of the chart rising — new work added.
- Stability: parallel band slopes mean a balanced system; diverging slopes mean trouble.
Real-World Example
A 12-person dev team I coached pulled six months of CFD data from their tracker. The In Review band had been quietly widening for four months — going from an average thickness of 4 items to 11. Cycle time had climbed from 5.5 days to 13 days, and nobody had noticed because the standup focused on To Do and In Progress. Once we showed the CFD in the retrospective, the team added a second reviewer, brought review WIP under control, and cycle time fell back to 6 days in three weeks. The data had been there for months; the chart made it impossible to ignore.
How to Build One
- Every day, count items in each stage and snapshot.
- Plot stacked-area: backlog at the top, Done at the bottom (so completed work grows the visible chart).
- Pick a meaningful time window — 60–90 days is usually right for sprint-cadence teams.
- Most modern trackers (Jira, Linear, Azure DevOps) produce CFDs natively; double-check the band definitions match your actual workflow.
Practical Lessons Learned
- Parallel slopes = stable system. If your bands are parallel, your system is in balance even if cycle time is high.
- A widening band is a leading indicator. By the time it's a problem in standup, the CFD has been warning you for weeks.
- The Done slope is your true throughput. Story points lie; the Done slope doesn't.
- Show it weekly in retros. Trends are invisible day-to-day and obvious week-over-week.
Common Mistakes
- Plotting it once and forgetting it. CFDs are weekly tools, not annual reports.
- Too many bands. 4–6 bands is the sweet spot; 12 bands is unreadable.
- Bands that don't match the actual workflow. "In Progress" that lumps three real stages tells you nothing.
- Reading the CFD without the team. The chart raises questions; only the team can answer them.
- Using points instead of item counts. Item counts are stable; point counts depend on estimation noise.
- Ignoring the top edge. A rising top means scope creep; that's information.
Expert Tips
- Pair CFD with a control chart of cycle time. The CFD shows the system; the control chart shows individual item variance.
- Use it to set WIP limits empirically. If the In Progress band consistently stabilises at 7, your WIP limit is 7, not whatever you guessed.
- Read it before standup, not during. Standup is for unblocking; reading the CFD live wastes 9 people's time.
- Plot it for entire programmes, not just teams. Programme-level CFDs surface cross-team bottlenecks no single team sees.
- Combine with burndown for sprint-internal vs flow-level views.
Key Takeaways
- The CFD is a stacked-area chart of WIP per stage over time; it is the single most informative flow chart in Kanban.
- It reveals throughput, WIP, cycle time, bottlenecks, and scope creep in one glance.
- Widening bands are leading indicators of trouble.
- Use item counts, not story points, for stability.
- Read it weekly with the team; the chart raises questions, the team answers them.
Related Encyclopedia Entries
Related Research Articles, Case Studies & Tools
Frequently Asked Questions
What's the difference between a CFD and a burndown?
A burndown is sprint-internal and shows remaining work over a fixed window. A CFD is continuous and shows the whole system over time. They answer different questions; mature teams read both.How often should we look at it?
Weekly in retros; a glance daily by the team lead. Reading it in standup is overkill.Item counts or story points?
Item counts. Points carry estimation noise; counts don't. CFD readability beats fine-grained sizing.How many bands should we have?
Match real workflow stages, typically 4–6. More is unreadable; fewer hides information.What does a widening band mean?
Work piling up in that stage — a bottleneck. Either capacity is short, WIP limits are absent, or upstream is overproducing.Can CFDs apply outside software?
Yes. Recruitment pipelines, claims processing, support tickets, construction-zone workflow — anywhere work flows through stages.Do tools generate CFDs automatically?
Jira, Linear, Azure DevOps, GitLab all do. Verify the band definitions match your workflow; the default settings sometimes don't.What is a common misconception about Cumulative Flow Diagram?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.Which related encyclopedia entries should I read alongside Cumulative Flow Diagram?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.How does Dr. Hassan Eliwa's research treat Cumulative Flow Diagram?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Cumulative Flow Diagram is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.How is Cumulative Flow Diagram defined on PMMilestone Research & Insights?
A stacked-area chart of work items in each stage over time — the single most informative chart in lean and Kanban flow management. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.
People also ask
Follow-up questions practitioners search for next — each one points to the calculator, template or reference entry that answers it.
Which learning track covers this end-to-end?
Structured tracks from beginner planner to programme controls director. Project Controls Academy ↗
Which book goes deeper than this entry?
Practitioner field handbooks with worked numerical examples. Books & Publications ↗
Which calculator on PMMilestone.org applies here?
The integrated EVM workbook covers most cost-schedule diagnostics. EVM Calculator ↗
Where is this in the glossary?
Quick-lookup definitions across 1,200+ PM terms. PM Glossary on PMMilestone.org ↗
Related Entries
Further reading on PMMilestone.org
Curated companion resources hosted on the flagship platform, PMMilestone.org.
- For practitioners who want to go deeper, the Project Controls Academy.
- Engineers researching this topic typically continue with the Learning Tracks.
- A practical companion to this entry is the Books & Publications.
- Closely related on the flagship platform is the EVM Calculator.
- Useful alongside this article is the Schedule Health Checker.
- Many readers follow this up with the PMMilestone.org knowledge hub.