Cumulative Flow Calculator
KanbanVisualize and analyze workflow efficiency, identify bottlenecks, and optimize process performance
Project Settings
Workflow Data
| Period | Backlog | In Progress | Testing | Done | Actions |
|---|---|---|---|---|---|
| 1 |
What is a Cumulative Flow Diagram?
A Cumulative Flow Diagram (CFD) is one of the most powerful visual management tools available to project managers working in Agile and Kanban environments. It plots the cumulative number of work items in each workflow stage over time, giving you an at-a-glance view of how work flows through your system. The PMBOK Guide recognizes CFDs as essential tools for monitoring and controlling project performance, particularly in adaptive life cycles where flow efficiency directly impacts delivery predictability.
Think of a CFD as an X-ray of your delivery pipeline. Each colored band represents a workflow stage, and the width of those bands tells a story. When bands expand, work is accumulating faster than it is being processed, which is a leading indicator of bottlenecks. When bands remain relatively uniform in width, your system is in a healthy, stable state. For PMP holders, understanding CFDs bridges the gap between traditional earned value management and modern flow-based metrics, giving you a richer picture of project health than schedule variance alone.
In Kanban specifically, the CFD is one of the three primary metrics charts alongside lead time histograms and throughput run charts. Together, they form the analytical backbone of continuous improvement. Teams that consistently review their CFDs can spot problems days or weeks before they surface as missed deadlines, making proactive course correction possible rather than reactive crisis management.
CFD Formula Explained
Average WIP is the mean number of work items residing in intermediate workflow stages (excluding the initial backlog and final done state) across all measured time periods. You read this directly from the vertical distance between the top of the first intermediate band and the bottom of the last intermediate band on your CFD.
Average Throughput is the mean number of items completed per time period, calculated from the slope of the bottom-most band (the "Done" line) on the diagram. A steeper slope indicates higher throughput, while a flattening slope signals slowing delivery.
Cycle Time is the result: the average elapsed time a single work item spends inside the delivery system from the moment work begins until it is marked complete. This relationship, known as Little's Law, holds true for any stable system where items enter and eventually exit.
Step-by-Step Guide to Reading a CFD
Define your workflow stages clearly. A typical software project might use Backlog, In Progress, Code Review, Testing, and Done. Each stage will become a colored band on the diagram.
Record cumulative item counts per stage at regular intervals (daily or weekly). Each row in the data table represents one time period with counts for every workflow stage.
Plot the data as stacked areas, stacking from the bottom (Done) upward. The vertical distance between any two adjacent lines represents the number of items in that particular stage.
Analyze the bands. A widening band means items are accumulating in that stage, signaling a bottleneck. Parallel, evenly spaced bands indicate a stable, predictable flow.
Calculate WIP limits using Little's Law. If your target cycle time is 5 days and your throughput is 4 items per day, your WIP limit should be around 20. Enforce this cap to keep flow predictable.
Real-World Example
Scenario: A software team tracking a 6-week Kanban board
• Week 1: 30 items total (Backlog: 20, In Progress: 5, Testing: 3, Done: 2)
• Week 3: 35 items total (Backlog: 15, In Progress: 8, Testing: 7, Done: 5)
• Week 6: 40 items total (Backlog: 10, In Progress: 6, Testing: 4, Done: 20)
• Average WIP across intermediate stages: 9 items
• Throughput: (20 - 2) / 5 = 3.6 items per week
Result: Cycle Time = 9 / 3.6 = 2.5 weeks. The widening Testing band in Week 3 flagged a bottleneck that was resolved by adding a QA resource, which is why the band narrowed again by Week 6.
Common Mistakes to Avoid
- Ignoring band widening — A growing band is your earliest warning sign. Teams that only look at throughput miss the fact that WIP is quietly increasing, which will eventually cause lead times to spike.
- Setting WIP limits too high — If your WIP limit exceeds what your team can realistically process, you lose the flow benefit entirely. Start with a limit equal to the number of team members and adjust from there.
- Not updating the CFD regularly — A CFD is only valuable when data is current. Stale data gives a false sense of stability. Update at least weekly, preferably daily.
- Treating all work items as equal size — Large epic-sized items distort the diagram. Break work into roughly same-sized items for more accurate flow analysis.
PMP Exam Tips
For the PMP exam, understand that cumulative flow diagrams fall under the Monitor and Control Process Group and are specifically tied to the Monitor Communications and Control Schedule processes. You may encounter scenario-based questions where you must interpret a CFD to identify which stage has a bottleneck or determine whether a project is on track. The key is to look at band widths: stable bands mean stable flow, widening bands mean accumulating delays.
Little's Law is testable material. Remember the three forms of the equation: Cycle Time equals WIP divided by Throughput, Throughput equals WIP divided by Cycle Time, and WIP equals Throughput multiplied by Cycle Time. Exam questions often give you two of the three variables and ask you to calculate the third. Also know that Little's Law only holds when the system is stable, meaning items are neither being added to nor removed from the system at an accelerating rate.
Finally, be prepared to distinguish between lead time and cycle time on the exam. Lead time is measured from the customer's request to delivery, while cycle time is measured from when the team actually starts working on the item. The CFD can help visualize both: the horizontal distance from when an item enters the top band to when it reaches the bottom band represents lead time, while the horizontal distance through intermediate bands represents cycle time.