|
| 1 | +# area-cumulative-flow: Cumulative Flow Diagram for Workflow Analytics |
| 2 | + |
| 3 | +## Description |
| 4 | + |
| 5 | +A cumulative flow diagram (CFD) displays the cumulative count of items in each workflow stage as stacked areas over time. Each band represents a stage (e.g., Backlog, In Progress, Done), and the vertical distance between two adjacent band boundaries shows the number of items currently in that stage (work-in-progress). This is a key visualization in Lean and Agile project management for identifying bottlenecks, monitoring throughput, and assessing flow efficiency across a delivery pipeline. |
| 6 | + |
| 7 | +## Applications |
| 8 | + |
| 9 | +- Monitoring Kanban board throughput and cycle time to assess team delivery performance |
| 10 | +- Identifying bottlenecks in software development pipelines by spotting widening or narrowing bands |
| 11 | +- Tracking manufacturing workflow stages over time to optimize production flow |
| 12 | +- Visualizing support ticket lifecycle stages to measure resolution efficiency |
| 13 | + |
| 14 | +## Data |
| 15 | + |
| 16 | +- `date` (date) - time axis representing the reporting period |
| 17 | +- `stage` (categorical, ordered) - workflow stage name in process order (e.g., Backlog, Analysis, Development, Testing, Done) |
| 18 | +- `count` (int) - cumulative number of items that have entered or passed through that stage by the given date |
| 19 | +- Size: 30-365 days, 4-8 stages |
| 20 | +- Example: daily cumulative item counts across a Kanban board with stages Backlog, In Progress, Review, Done over 90 days |
| 21 | + |
| 22 | +## Notes |
| 23 | + |
| 24 | +- Stages must be stacked in workflow order: earliest stage (e.g., Backlog) on top, latest stage (e.g., Done) on bottom |
| 25 | +- The vertical distance between two adjacent band boundaries represents the number of items currently in that stage (WIP) |
| 26 | +- Cumulative counts are monotonically non-decreasing; each stage's count should always be greater than or equal to the count of the next stage in the workflow |
| 27 | +- Widening bands indicate growing WIP or bottlenecks; narrowing bands indicate stages draining faster than they fill |
| 28 | +- Use a sequential or distinct color palette where earlier stages are visually distinguishable from later stages |
| 29 | +- Include a legend identifying each workflow stage |
| 30 | +- X-axis should display date labels at reasonable intervals |
0 commit comments