Epic progress tracking

Epic progress tracking is the measurement of how much of a large body of work, an epic, is complete at a point in time, expressed as the share of its scope that is done. An epic is a big initiative made of many stories, often running across several sprints. Tracking its progress means knowing what proportion of the total work is finished, what is in flight, and what has not been started, so the picture is current rather than a guess.

Progress tracking matters because epics hide trouble well. Individual stories close on schedule, the team feels busy, and the epic still drifts because no one is watching the whole. A clear completion percentage, updated as work lands, turns a vague sense of being on track into a number that can be challenged. It is the difference between we are nearly there and we are at 62% with three stories blocked.

The honest version of this metric tracks completed scope against current scope, not original scope. If an epic grows from 60 to 90 points as the team learns, finishing 45 points is half of the real work, not three quarters of the original. Measuring against current scope keeps the percentage truthful even as the epic changes shape.

The headline calculation divides completed scope by total current scope. The inputs below make that number trustworthy, and several of them are worth tracking in their own right because each reveals a different kind of trouble underneath the percentage.

1. 1

   Completed scope

   The points or items that meet the definition of done. Be strict here. Work in review or testing is in progress, not complete, and counting it early is what produces a misleading percentage.

2. 2

   Total current scope

   All scope in the epic right now, including work discovered after kickoff. Use current scope as the denominator so the percentage stays honest as the epic grows or shrinks.

3. 3

   Work in progress

   Items started but not finished. A large gap between started and completed signals flow problems and a likely future stall, even when the headline percentage still looks fine.

4. 4

   Blocked work

   Items that cannot move because of a dependency or decision. Blocked scope often hides inside the in-progress count and is the most common reason an epic plateaus.

5. 5

   Scope added since start

   Net new scope introduced after the epic began. Tracking this separately explains why progress can stall even as the team keeps completing work, because the target itself is moving.

Worked example: an epic started at 60 points and has since grown to 90 as new stories were discovered. The team has completed 45 points, with 20 in progress and 25 not started. Against original scope the team would claim 75% done, which sounds reassuring. Against current scope the true figure is 45 divided by 90, or 50%. The 25-point gap between those two numbers is scope growth made visible, and it is exactly what a naive percentage would have buried.

A metric tree decomposes epic completion into the work states and flow drivers beneath it, so a stalled percentage traces back to a specific cause and a specific owner. The headline is epic completion percentage. The first level splits the epic into its work states: done, in progress, blocked, and not started. That split alone explains most stalls, because a high in-progress count with little movement is a flow problem dressed up as activity.

Each state then decomposes further. Completed work breaks into stories closed per sprint and average story size, which together set the real pace. In-progress work breaks into items being built, items in review, and items in test, so a queue forming at one stage becomes obvious. Blocked work breaks into the kind of blocker: a dependency, a decision pending, or a defect. When progress flatlines, the tree shows whether the team is blocked, overloaded with started work, or simply facing more scope than it began with.

This turns the percentage from a status light into a diagnosis. A delivery lead can see not just that the epic is at 50%, but that 20 points sit in review behind a single reviewer, which is a bottleneck someone can clear this week.

Benchmarks for progress tracking are not about a target percentage, since the right value depends entirely on where the epic is in its life. They are about flow health: how linear progress is, how much work piles up in progress, and how much scope churns. The ranges below describe what healthy and unhealthy tracking tend to look like.

The shape of the progress line tells you more than its current value. A healthy epic burns up steadily, gaining a few percentage points each sprint, while an unhealthy one sits flat then lurches forward near the end, which usually means work was sitting unfinished rather than genuinely progressing. The in-progress share is the companion signal. When more than 40% of scope is started but not done, the team is spread across too many items and completion will stall regardless of how busy everyone looks.

Improving progress tracking is partly about measuring more honestly and partly about fixing the flow the measurement exposes. The cards below cover the levers that keep an epic moving and the percentage trustworthy.

The fastest way to unstick an epic is to find the work state holding it up and put a named owner on clearing it, rather than asking the whole team to go faster. KPI Tree supports this by giving each branch of the progress tree a RACI owner, so the in-review queue has an owner distinct from the dependency blockers. When completion plateaus or scope jumps, the platform pushes the movement to the accountable owner of the responsible branch instead of leaving it in a sprint board no one is watching, and the verified impact loop confirms whether clearing a blocker actually moved completion forward. That is what separates a burn-up chart from progress that someone is on the hook for.

1. 1

   Measuring against original scope

   Tracking completion against the scope at kickoff overstates progress as the epic grows. Always measure against current scope so the percentage reflects the real size of the work.

2. 2

   Counting in-progress as done

   Treating started or in-review items as complete inflates the number and produces the epic that sits at 90% for weeks. Only fully done work belongs in the numerator.

3. 3

   Watching the value, not the shape

   A single percentage hides whether progress is steady or stalling. Track the burn-up line over time so a flat stretch raises a flag before the deadline does.

4. 4

   Ignoring blocked work

   Blocked items often hide inside the in-progress count and quietly freeze an epic. Track blockers as their own state so a stall has a visible, addressable cause.

5. 5

   Letting work in progress balloon

   Starting many items at once feels productive but spreads the team thin and slows completion. Limit work in progress so the percentage climbs steadily instead of in late lurches.