This dashboard provides an overview of the Cycle Time, used to assess and track efficiency during each stage of the development.

It provides key metrics to understand the company’s ability to deliver features. This is done by evaluating the bottlenecks in the Software Development Lifecycle (SDLC) by highlighting unusual durations across all stages of the development and providing a historical view of these metrics.

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, project, or pull request.

Note that the review time stage of the Cycle Time relies on the review_requested_at field that is gradually populated after the project has been connected to Keypup (learn more here). The values of these stages will automatically be refined s as Keypup observes new data points.

Coding time: Companies use this stage of the Cycle Time to measure the duration of the first development pass, which is composed of the development time and the review wait time.

Review time: Companies use this stage of the Cycle Time to measure the duration of the complete review cycle (i.e. time to perform all the reviews required to approve a pull request).

Merge time: Companies use this stage of the Cycle Time to measure the duration required to deliver finished work to production (i.e. time to merge a pull request to a specific branch).

Cycle Time Overview: Companies use these metrics to assess and improve their software 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 shipped PRs, identify those with unusual cycle times, and investigate them in more detail.