This dashboard provides an overview of the Cycle Time based on Jira or Trello issues. It leverages the "time in column" feature to report the duration of each stage of the product development development flow.

It provides key metrics to understand the company’s ability to deliver new product capabilities or support customers (in case issues are related to a customer support project). The dashboard lets managers and team leaders quickly identify unusual durations across the delivery pipe and gives them a historical view for each stage.

The general recommendation is to keep each stage as short as possible to maintain a proper development and delivery flow.

This dashboard (and each insight) can be narrowed down to a given company, team, or project.

Pickup time: Companies use this Cycle Time insight to measure how long it takes for issues to enter an active working state.

Implementation time: Companies use this Cycle Time insight to measure the time it takes for implementers to complete the core work (e.g. development) on issues.

QA time: Companies use this Cycle Time insight to measure how long it takes for issues to be end-to-end tested and validated by the business.

Release time: Companies use this Cycle Time insight to measure how long it takes for issues to shipped once implemented and tested.

Cycle Time Overview: Companies use these metrics to assess and improve their product development pipeline. The general recommendation is to try to keep each stage of the cycle as short as possible to maintain an agile delivery flow.

Cycle Time Breakdown: This report can be used to review recently delivered issues, identify those with unusual cycle times, and investigate them in more detail.