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.
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.
Every item in a selected cycle has exactly one outcome for that cycle:
| Outcome | Meaning |
|---|---|
| Completed | Moved to a done status while in this cycle. |
| Carried Forward | Left this cycle unfinished and was later added to a cycle that starts after it. |
| Removed | Left this cycle unfinished and has not been added to a later cycle. |
| Not Completed | Still 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.
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 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).
Report: Time Allocation Matrix
Roll recorded time up through your work-item hierarchy or by persona, month by month, and export it to Excel.
Overview
Service Desk turns customer email and form submissions into DevStride work items your team can triage, answer, and track. What it is, the five ideas behind it, and where to start.