Fundamentals
Epic Cumulative Flow Diagram Example: How to Build and Read One
Part of our guide to business analyst roles and responsibilities.
What an epic cumulative flow diagram shows
A cumulative flow diagram (CFD) is a stacked area chart. The horizontal axis is time. The vertical axis is a count of work items. Each coloured band is one workflow state, such as To Do, In Progress, In Test and Done.
An epic CFD is the same chart, filtered to the child stories of one epic. Instead of looking at everything the team is doing, you look at one piece of business value, for example an online document upload feature, and see how its stories move from idea to finished.
It is called cumulative because the Done band never goes down. Once a story is done, it stays counted. The top edge of the chart is the total number of stories in the epic, so the chart shows scope and progress at the same time.
Business analysts like the epic view because sponsors usually ask about features, not about the whole board. A sponsor wants to know when document upload will be ready, not how many tickets the team closed this week.
Epic CFD compared with burndown and burnup
| Aspect | Epic CFD | Burndown chart | Burnup chart |
|---|---|---|---|
| Main question it answers | Where is work piling up, and is scope changing? | How much work is left? | How much is done compared with total scope? |
| Shows each workflow state | Yes, one band per state | No, only remaining work | No, only done work and total scope |
| Shows scope change | Yes, the top line rises or falls | Hidden inside the remaining line | Yes, as a separate scope line |
| Good for spotting bottlenecks | Strong | Weak | Weak |
| Easy for sponsors to read | Needs a short explanation the first time | Usually easy | Usually easy |
How to read the bands
You only need five reading rules. Practise them on any chart and they become quick.
- Top line: the total number of stories in the epic. If it rises, scope grew. Always ask who added the work and why.
- Band thickness: measured straight up at one date, it is the number of stories in that state. A band that keeps getting thicker means work arrives faster than it leaves.
- Horizontal distance: the gap, measured sideways, between the line where stories enter In Progress and the line where they reach Done gives a rough feel for how long stories take. A wider gap means slower flow.
- Done slope: a steep Done line means the team is finishing work. A flat Done line means nothing is finishing, even if everyone is busy.
- Parallel bands: healthy flow usually looks like bands rising together with a fairly steady thickness.
A middle band that widens while the band below it stays flat is the classic sign of a bottleneck. The work is stuck in that state, and the state just after it is starved.
Remember what the chart cannot tell you. It counts stories, not effort, so one large story and one tiny story look the same. It also does not explain why a band grew. That is the conversation you have with the team.
How to build an epic cumulative flow diagram in seven steps
- Pick one epic and confirm which stories belong to it. Open the epic and check that every child link is correct and that no stray stories from other epics are attached.
- Agree the workflow states you will show. Use the board columns, but merge tiny states (for example Ready for Test and In Test) so each band is readable.
- Choose a snapshot interval. Daily works for an epic that lasts a few weeks. Weekly is clearer for a longer epic. Always take the snapshot on the same day and time.
- Get the data. Many Jira-style tools have a cumulative flow report that you can narrow to one epic with a quick filter or a board filter. If you cannot, export each story's status history and count by date. See Jira for Business Analysts for the basics of epics and filters.
- Count stories per state per snapshot. Then check that the states add up to the total for that date. If they do not, a story is missing or counted twice.
- Stack the bands with Done at the bottom, then In Test, In Progress and To Do at the top. This order makes the top line equal to total scope.
- Annotate events on the chart: scope added, a tester on leave, a release date. Notes turn a pretty chart into evidence.
Diagram in words
- 1. Pick one epic: Confirm the child stories and remove any that belong elsewhere.
- 2. Agree the states: Use board columns and merge tiny states so each band stays readable.
- 3. Set the snapshot rhythm: Daily or weekly, always on the same day and time.
- 4. Get status data: Use the tool's flow report with an epic filter, or export status history.
- 5. Count and check totals: Count stories per state and confirm the states add up to total scope.
- 6. Stack the bands: Done at the bottom, To Do at the top, so the top edge equals scope.
- 7. Annotate events: Mark scope changes, absences and releases directly on the chart.
If your tool cannot draw the chart, a spreadsheet works well. Put dates in rows, states in columns, and use a stacked area chart. The data matters more than the software.
Worked example: an epic CFD at Marigold Home Loans
Marigold Home Loans is a fictional lender. Its epic Online document upload lets loan applicants upload payslips and ID instead of emailing them. Throughout the example, Nadia is the business analyst, Mei is the lead developer, Riya is the QA tester and Helena is the project sponsor.
The epic started with 20 stories. Nadia took a snapshot every Friday for five weeks and counted the stories in each state. Each row below adds up to the total for that week.
Weekly snapshot data for the epic
Epic: Online document upload
Week | To Do | In Progress | In Test | Done | Total
W1 | 16 | 4 | 0 | 0 | 201
W2 | 12 | 5 | 2 | 1 | 20
W3 | 13 | 5 | 4 | 2 | 242
W4 | 10 | 4 | 8 | 2 | 243
W5 | 8 | 4 | 6 | 6 | 244
- Starting point. The epic holds 20 stories. In week 1 the team started 4 of them, so 16 remain in To Do. Nothing has reached test yet.
- Scope grew. Helena added 4 co-applicant stories, so the total rose from 20 to 24. To Do is 12, plus 4 added, minus 3 started, which gives 13.
- Bottleneck in test. 3 stories started and 4 moved into test, but none finished. In Test doubled from 4 to 8, Done stayed at 2, and In Progress fell from 5 to 4.
- Recovery. 4 stories moved from In Test to Done first, then 2 entered test, so In Test is 6, at the new limit. 2 stories started, so In Progress stays at 4.
To check the table, Nadia also listed the movements in each week. Every row in the table can be rebuilt from the row before it using these moves.
- Week 1: 4 stories started. None moved to test, none finished.
- Week 2: 4 started, 3 moved from In Progress to In Test, 1 finished.
- Week 3: 4 new stories added to To Do, 3 started, 3 moved to test, 1 finished.
- Week 4: 3 started, 4 moved to test, 0 finished.
- Week 5: 4 finished, 2 moved to test, 2 started.
Over five weeks, 16 of the 24 stories were started, which leaves 8 in To Do. 12 stories reached test, so 4 are still in progress. 6 finished, so 6 are still in test. These match the week 5 row.
Weeks 1 and 2 look healthy. Stories leave To Do, pass through In Progress and In Test, and the first story reaches Done in week 2.
In week 3 the top line jumps from 20 to 24. Helena added 4 stories for co-applicant documents, a 20% increase in scope. To Do went up from 12 to 13 even though 3 stories were started, because 4 new ones arrived.
Week 4 is the warning. The In Test band doubles from 4 to 8, while Done stays flat at 2. In Progress falls from 5 to 4 (3 started, 4 handed to test), so the developers are not the slow part. Work is piling up in test.
Reading the week 4 chart together
Marigold Home Loans, a fictional lender: the Friday review of the week 4 snapshot for the Online document upload epic.
- Nadia Business analyst
Look at the In Test band. It went from 4 stories to 8 in one week, and Done stayed at 2. Work is arriving in test faster than it leaves.
- Riya QA tester
That matches my week. Each upload story needs checks for PDF files, JPG files and phone photos, and I am the only tester on this epic.
- Mei Lead developer
In Progress dropped from 5 to 4, so development is not the slow part. Next week my developers will help Riya run test cases before anyone moves a new story into test.
- Nadia Business analyst
Then I suggest a limit from next week: In Test holds 6 stories or fewer. Nobody moves a story into test while it already holds 6.
- Riya QA tester
Agreed. Six is a number I can manage with the developers helping.
- Nadia Business analyst
I will add the limit to the board today, mark the week 3 scope change on the chart, and walk Helena through both on Monday.
The people and the company in this scene are fictional.
Week 5 shows the effect. Developers helped finish testing first, and 4 stories moved from In Test to Done, which brought In Test down from 8 to 4. Only then did 2 stories move from In Progress into test, so In Test ended the week at 6, at the new WIP limit and not over it. The team also started 2 stories from To Do, so In Progress stayed at 4 (4, minus 2 sent to test, plus 2 started) and To Do fell from 10 to 8.
Done rose from 2 to 6, which is 6 of 24 stories, or 25% of the epic. The Done line finally has a steep slope. Nadia's note to Helena was short: scope grew by 4 stories in week 3, testing was the constraint in week 4, and the team now has a limit of 6 stories in test to stop it happening again.
Common mistakes with epic cumulative flow diagrams
- Counting sub-tasks as well as stories. One story with three sub-tasks gets counted four times and the bands lie. Count one level only.
- Mixing epics. A loose filter pulls in stories from another epic. Check the child list before every snapshot.
- Too many states. Eight thin bands are unreadable. Merge waiting states into the working state they belong to.
- Ignoring the top line. Progress can look slow simply because scope grew. Always report scope change next to progress.
- Inconsistent snapshot days. Taking one snapshot on Monday and the next on Thursday creates fake bumps in the bands.
- Stale statuses. If people forget to move cards, the chart shows a bottleneck that does not exist. Ask the team to update the board before snapshot time.
- Not reconciling the numbers. If you cannot rebuild each week from the week before using the moves in and out of each state, something is wrong with the data.
- Using the chart to judge individuals. A widening test band is a system problem, often about capacity or story size, not about one tester working slowly.
The last mistake matters most. If people feel blamed by the chart, they will stop updating the board honestly, and the chart becomes useless.
Where the epic CFD fits in a business analyst's work
The epic CFD is a delivery tool, but it often lands with the business analyst. You are the person who knows the epic's scope, talks to the sponsor and understands why stories were added. That makes you well placed to read the top line and explain it.
It also links to other parts of the role. Scope growth on the chart should match a change request or a decision log entry. A testing bottleneck may point back to stories that are too large or acceptance criteria that are unclear. For a wider view of these duties, see What Does a Business Analyst Do?.
If you want to practise, take any small project board, pick one epic and rebuild its chart from status history in a spreadsheet. Doing it by hand once teaches you more than reading many finished charts.
Frequently asked questions
Can I make an epic cumulative flow diagram in Jira?
Many Jira boards include a cumulative flow report, and you can usually narrow it to one epic with a quick filter or a board filter. Menus and options change over time, so check the current Atlassian documentation for your version. If the report does not fit your needs, export status history and build the chart in a spreadsheet.
Should I take snapshots daily or weekly?
Use daily snapshots for a short epic that lasts a few weeks, so you see problems quickly. Use weekly snapshots for a long epic, because daily noise makes the chart harder to read. Whichever you choose, keep the same day and time every time.
What does a flat Done band mean?
It means no stories finished during that period. Look at the band just above Done. If it is widening, work is stuck there. If every band is flat, the team may be blocked, on leave or working on another epic.
Is a cumulative flow diagram only for Kanban teams?
No. Scrum teams can use it too. Within a sprint it shows whether stories are finishing steadily or all at the end. Across sprints, an epic CFD shows how one feature is progressing and whether its scope is growing.
Should the top line ever go down?
Yes, if stories are removed from the epic or moved to another one. A falling top line is a scope change just like a rising one, so mark it on the chart and record the decision.
This article was written by an AI system and published automatically after automated accuracy, safety and quality checks. All companies, people and numbers in the examples are fictional. BA Mentorship does not issue professional certifications and cannot guarantee any job or interview outcome. Spot an error? Email our support team and we will check and correct it.