Measure Performance: Reports

Report: Cycle Carry-Forward

See, cycle by cycle, which work was finished, carried into a later cycle, dropped, or is still open — and export the detail to CSV.

Overview


Cycle Carry-Forward answers what happened to the work we planned into each cycle? For every cycle you pick it sorts that cycle's items into four outcomes, so you can see how much work slips from one cycle to the next, how much is dropped, and why. Use it in retrospectives and when a team's Velocity is falling: a growing Carried Forward band usually explains it.

Open Measure Performance and pick Cycle Carry-Forward under Agile, or press Cmd-K / Ctrl-K and type Report: Cycle Carry-Forward. It uses the same permission as the Velocity report.

Choosing cycles

Click Cycles in the toolbar (it reads Select Cycles until you choose some) to open the Cycle Selector, then pick the cycles you want to compare. Until you choose at least one, the report shows No Cycles Selected.

Outcomes

Every item in a selected cycle has exactly one outcome for that cycle:

OutcomeMeaning
CompletedMoved to a done status while in this cycle.
Carried ForwardLeft this cycle unfinished and was later added to a cycle that starts after it.
RemovedLeft this cycle unfinished and has not been added to a later cycle.
Not CompletedStill in this cycle and not done.

Use Items in the toolbar (All Items, Completed, Carried Forward, Removed or Not Completed) to focus on one outcome, and Show to measure the chart and tables by Count, Time Estimate or Point Estimate. For and Filters narrow the items as on other reports; the Board and Status filters are hidden because the cycles and outcomes set the scope. There is no Range: each cycle's own dates define it.

An item completed while on a cycle stays Completed for that cycle even if it was moved afterwards, and an already-finished item dragged onto a cycle counts as Completed there too.

Reading the report

  • Chart — one column per cycle, stacked by outcome, so a growing Carried Forward band shows work sliding between cycles.
  • Summary table — per cycle: Planned, the count for each outcome, Completion and Spillover percentages, Carried Est. (hrs), Carried Pts, and Actual vs Est. — actual hours divided by the original estimate, over completed items that have an estimate (100% means exactly on estimate).
  • Items — every item with its outcome, current status, Next Cycle (where carried-forward work went) and Original Cycle (where it was first planned), plus its original estimate, actual effort and the variance between them. Actual effort is all the time logged on the item, across every cycle it has been in, so a carried-forward item shows the same total in each cycle's row. Reason is the item's blocker note, shown when it was not completed in that cycle.

Example. Sprint 5 shows 30 planned, 18 completed, 9 carried forward, 3 removed: a 60% completion and 30% spillover. Sprint 6 shows 32 planned, 17 completed, 12 carried forward. The team is finishing about the same amount each sprint while planning more than it finishes, and the carried work is accumulating. Open the Items tab filtered to Carried Forward and read the Reason column (the items' blocker notes) before the next planning session; if the reasons are blank, ask the team to record blockers when work stalls.

Export

Export CSV downloads the item detail. Its columns are: Cycle, Item, Title, Type, Assignee, Outcome, Current Status, Next Cycle, Original Cycle, Original Estimate (hrs), Actual Effort (hrs), Variance (hrs), Points, and Reason for Carry Forward (the blocker note).

Pitfalls

  • Carried forward means moved to a later cycle. Work sent back to the backlog and never replanned is Removed, even if it is picked up months later.
  • Original Estimate is the first non-zero estimate ever recorded, so it reflects what the team believed when the work was first sized, not the latest number.
  • Actual Effort spans every cycle the item was in; a carried item shows the same total in each cycle's row, so do not add rows together.