Kanban Reports

Two reports are available for flow-based teams using the Kanban Board app. Teams that bundle work into releases may also use a status page to manage sets of work items:

Cycle Time report

The Cycle Time report shows you how long it takes for work to pass through your team's process. Cycle time is defined as the number of days it takes a card to move from the In-Progress schedule state to the Accepted schedule state. High-performing teams often use their average cycle time to estimate how long a new request may take to complete.

Cycle Time

The average cycle time for each of the past 12 months will display on a chart. The line on the chart shows the average cycle time trend.

The Summary Metrics section provides additional statistics for the past 12 months.

  • Average: Cumulative cycle time for all work items
  • Count: Number of work items that have flowed through your process
  • Standard Deviation: The average variance in cycle times; the larger this value, the more varied times are for individual work items
  • Minimum: The shortest cycle time for any work item
  • Maximum: The longest cycle time for any work item

Map schedule states

If your Kanban Board app is configured to display values of a custom field as columns, you must map those values to the Schedule State field to collect cycle time data. Access the settings menu of your board to configure mapping.

Group By Column Picker

Map the value that represents the beginning of your process to the In-Progress schedule state. Map the end of your process to the Accepted schedule state, or any custom value (if present) after Accepted.

When cycle time calculation resets

For example, a defect is marked In-Progress, then handed off by a team and placed back in Defined. The new team later sets it back to In-Progress. Where does the clock start? The clock restarts once it crosses the boundary the second time. It is measured from the last time that it crosses the first boundary to the last time it crosses the second boundary.

If a work item crosses both the start and end boundaries at the same time, it is included, but its cycle time is zero.


Use this chart to detect trends and consider questions like:

  • How long does it take, on average, for a work item to pass from an idea to completion?
  • Has our team increased speed since adding new members last month?
  • Our average time jumped last month, is the huge request we handled during week one to blame?
  • How many stories or defects of similar size should we be able to accept in a given time period?

Cycle time is often linked to work-in-progress. If your team is struggling to reduce the time it takes to complete work, consider lowering the team WIP limits. The fewer items the team is working on simultaneously, the quicker work flows through your process.

Throughput report

The Throughput report shows you the number of work items the team is able to accept each month. Items are included in the report when their Schedule State field is set to Accepted, or any custom schedule state that exists after Accepted.


The bar chart displays the number of user stories and defects that your team has accepted for each of the past 12 months.

The Summary Metrics section provides additional statistics for the past 12 months.

  • Average: All work items accepted, divided by 12; use this value to estimate how much work a team can accept in an average month
  • Count: Number of work items that have been accepted
  • Standard Deviation: The average variance in throughput; the larger this value, the more varied through put is month-to-month
  • Minimum: The smallest number of work items accepted in a month
  • Maximum: The largest number of work items accepted in a month


The chart helps you detect trends and consider questions like:

  • How many work items of similar size should we be able to accept in a similar, future time period?
  • Why were we able to accept several more user stories last month than usual?
  • How did the large influx of defects in June affect our story output?
  • What factors might affect our throughput?

Work Item Status page

The Work Item Status summary page displays work items and any scheduled items associated with a specific release.
When using a project hierarchy, this page reflects any view scoping settings that you have indicated in the project drop-down. All charts and columns display the cumulative totals for all projects that have the same active release name and end date.

The Work Item Status page to view release information such as:

  • All parent-level work items: Including user story, defect, and defect suite that are either scheduled or have child work items scheduled into the displayed release.
  • Iteration: If an item has been scheduled into an iteration, the iteration name displays here. Click the iteration name to navigate to the detail view of the iteration.
  • Status: The status for both the work item and the scheduled items display. The color-coded display gives a quick assessment of each item scheduled for the release. You can easily view the progress of each work item and its children as it moves toward completion in relation to the release date.
  • Accepted: The number of items that have been accepted out of the total number of items scheduled for the work item, and the percentage this represents for the entire parent work item. The total for all work items in the release is rolled up and displayed at the top of the column.
  • Active defects: The number of active defects related to each work item is displayed in this column.

On the Work Item Status page, you can:

  • Quickly locate a specific work item by typing its number directly into the ID# text box. Use the following delimiters with a specific number to refine your ID search: <= , >= , = , < , > .
  • Edit any work item.
  • Print a Work Item Status summary or detail report from the Actions menu. All work items and their scheduled items are printed in a hierarchical display for both reports.
  • Click the hyperlinked ID, Name, or iteration on each line of the display to navigate to the detail of the listed work item or iteration.
  • Use drag-and-drop ranking. Select the work item and prioritize it by dragging it up or down relative to other work items on the page.
  • Filter on fields such as Package and Status for the work item.
  • Sort on the Rank, ID, Name, or Status fields of the work item.
  • View predecessor and successor relationships by hovering over the related inline icon.


Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.