Skip to main content
New: 9 PM Courses with hands-on exercises and certificates
← Back to Glossary
DeliveryC

Cumulative Flow Diagram

Definition

A cumulative flow diagram (CFD) is a stacked area chart that tracks the total number of work items in each stage of a team's workflow over time. Each workflow stage (such as Backlog, Ready, In Progress, In Review, Done) is represented as a colored band. The chart is cumulative, meaning items only move upward or stay flat. They never decrease because completed work remains counted.

The CFD originated in lean manufacturing and was adopted by software teams practicing Kanban. It is one of the core metrics tools for flow-based delivery. While burndown charts track progress toward a fixed goal, CFDs track the health of the entire delivery pipeline. They answer questions like: Where is work getting stuck? Is throughput stable or erratic? Are we adding scope faster than we are completing it?

Three key measurements can be read directly from a CFD. The vertical width of any band is the work in progress (WIP) for that stage. The horizontal distance between the top of the "In Progress" band and the top of the "Done" band is the approximate cycle time. The slope of the "Done" band is the team's throughput rate.

Why It Matters for Product Managers

CFDs give PMs a systems-level view of delivery health that individual ticket tracking cannot provide. When your sprint velocity looks fine but features are taking weeks to ship, a CFD will show you exactly where the delay lives. Maybe code review is the bottleneck. Maybe QA is understaffed. The CFD makes invisible queues visible.

This data is essential for making accurate delivery commitments. If your CFD shows a stable throughput of 8 items per week with a cycle time of 6 days, you can confidently tell stakeholders that a 20-item initiative will take approximately 2.5 weeks. That is a data-driven estimate, not a guess based on story points and hope. For more on translating delivery metrics into stakeholder communication, see the stakeholder management term.

How to Apply It

  • ☐ Set up a CFD in your project management tool (Jira, Linear, and Shortcut all support them natively)
  • ☐ Define clear workflow stages that match your team's actual process (not an idealized version)
  • ☐ Review the CFD weekly in your retrospective or team sync
  • ☐ Watch for widening bands (bottlenecks) and take action: add capacity, reduce WIP limits, or simplify the stage
  • ☐ Use the throughput slope to forecast delivery dates for upcoming initiatives
  • ☐ Compare CFDs across sprints to measure whether process improvements are working

If your team uses Scrum, overlay the CFD with sprint boundaries to see whether your sprint cadence aligns with your actual flow patterns. The RICE calculator can help you prioritize which bottleneck to address first based on impact.

Related Terms

KanbanWork in Progress (WIP)Burndown ChartVelocitySprint

Frequently Asked Questions

How do you read a cumulative flow diagram?+
A CFD has time on the x-axis and item count on the y-axis. Each colored band represents a workflow stage (e.g., To Do, In Progress, In Review, Done). The vertical width of a band shows how many items are in that stage at any point in time. If the 'In Review' band is getting wider over time, work is piling up waiting for review. That is a bottleneck. The horizontal distance between when an item enters 'In Progress' and when it reaches 'Done' represents your average cycle time. A healthy CFD shows bands of consistent width with the 'Done' area steadily growing.
What problems can a cumulative flow diagram reveal?+
CFDs reveal four common problems. First, bottlenecks: if any band widens over time, work is accumulating in that stage faster than it is leaving. Second, starvation: if the 'To Do' band narrows to nothing, the team is about to run out of ready work. Third, scope creep: if the total height of the chart is growing, new items are being added faster than old ones are completed. Fourth, inconsistent throughput: if the 'Done' band grows in bursts rather than steadily, the team has a batch delivery pattern that makes planning unreliable.
Should Scrum teams use cumulative flow diagrams or burndown charts?+
Both serve different purposes. Burndown charts are sprint-scoped and answer 'will we finish the sprint commitment?' CFDs are continuous and answer 'where are the bottlenecks in our process?' Scrum teams benefit from both. Use burndown charts during sprint execution for daily tracking, and use CFDs at the weekly or monthly level to identify systemic flow problems. If you had to pick one, a CFD provides richer insight because it shows the health of every workflow stage, not just the aggregate remaining work.
← PreviousCost-Benefit AnalysisNext →Customer Advisory Board (CAB)

Explore More PM Terms

Browse our complete glossary of 100+ product management terms.

Full GlossaryExplore Frameworks