DORA Lead Time
Last updated
Last updated
The DORA Lead Time calculation measures the total time taken from the moment a ticket is created to the point when it is released to production. Below are various use cases that demonstrate how Lead Time is calculated across different scenarios.
To learn more, go to DORA Reports
Note that the following examples consider the Merge Stage in the Workflow Profile to be configured for tracking the time taken to merge the last Pull Request.
In this example, we consider a use case where a single pull request (PR) is associated with a single Jira ticket. The Lead Time calculation includes several stages as shown below.
The table provides details on the different stages, their descriptions, formulas, and an example calculation.
The Lead Time calculation in this case consists of the following stages:
| Stage | Description | Formula | Example |
|---|---|---|---|
Ticket In Progress Time | The time taken for a ticket to move from the |
| 10:00 AM - 9:50 AM = 10 minutes |
First Commit Time | The time taken to make the first commit after the ticket is in progress. |
| 10:05 AM - 10:00 AM = 5 minutes |
First Pull Request Creation Time | The time taken to create the first pull request (PR) after the first commit. |
| 10:10 AM - 10:05 AM = 5 minutes |
First Pull Request Approval Time | The time taken for the first approval after the first pull request is created. |
| 10:11 AM - 10:10 AM = 1 minute |
Last Pull Request Merge Time | The time taken to merge the pull request after it is approved. |
| 10:15 AM - 10:11 AM = 4 minutes |
First Continuous Integration Time | The time taken to complete the continuous integration (CI) pipelines for the first time after the last pull request is merged. |
| 10:16 AM - 10:15 AM = 1 minute |
First Continuous Deployment Time | The time taken for the continuous deployment (CD) pipelines to complete for the first time after the CI process is finished. |
| 10:17 AM - 10:16 AM = 1 minute |
First Issue Management Done Time | The time taken to mark the issue as |
| 10:20 AM - 10:17 AM = 3 minutes |
First Release Time | The time at which the |
| 11:00 AM - 10:20 AM = 40 minutes |
Total Lead Time
Total Lead Time is the sum of all the above stages:
Therefore, the Total Lead Time is 70 minutes.
In the case where two pull requests (PRs) are associated with a single Jira ticket in a sequential manner, the Lead Time calculation can be broken down into the following stages.
The following table outlines the different stages, their descriptions, formulas, and example calculations.
| Stage | Description | Formula | Example |
|---|---|---|---|
Ticket In-progress Time | The time taken for a ticket to move from the 'Created' state to the 'In-Progress' state. |
|
|
First Commit Time | The time taken to make the first commit after the ticket is in progress. |
|
|
First Pull Request Creation Time | The time taken to create the first pull request (PR) after the first commit. |
|
|
First Pull Request Approval Time | The time taken to approve the first pull request after it is created. |
|
|
Last Pull Request Merge Time | The time taken to merge the last (second) pull request after it is approved. |
|
|
First Continuous Integration Time | The time taken to complete the continuous integration (CI) pipelines for the first time after the last pull request is merged. |
|
|
First Continuous Deployment Time | The time taken for the continuous deployment (CD) pipelines to complete for the first time after the CI process is finished. |
|
|
First Issue Management Done Time | The time taken to mark the issue as |
|
|
First Release Time | The time at which the |
|
|
Total Lead Time
Total Lead Time is the sum of all the above stages:
Therefore, the Total Lead Time is 99 minutes.
In the case where two pull requests (PRs) are associated with a single Jira ticket in an overlapping manner, the lead time calculation can be broken down into the various stages.
The following table outlines the different stages, their descriptions, formulas, and example calculations.
| Stage | Description | Formula | Example |
|---|---|---|---|
Ticket In-progress Time | The time taken for a ticket to move from the 'Created' state to the 'In-Progress' state. |
|
|
First Commit Time | The time taken to make the first commit after the ticket is in progress. |
|
|
First Pull Request Creation Time | The time taken to create the first pull request (PR) after the first commit. |
|
|
First Pull Request Approval Time | The time taken to approve the first pull request after it is created. |
|
|
Last Pull Request Merge Time | The time taken to merge the last (second) pull request after it is approved. |
|
|
First Continuous Integration Time | The time taken to complete the continuous integration (CI) pipelines for the first time after the last pull request is merged. |
|
|
First Continuous Deployment Time | The time taken for the continuous deployment (CD) pipelines to complete for the first time after the CI process is finished. |
|
|
First Issue Management Done Time | The time taken to mark the issue as 'Done' in the issue management system (e.g., Jira) after the CD process is completed. |
|
|
First Release Time | The time at which the |
|
|
Total Lead Time
Total Lead Time is the sum of all the above stages:
Therefore, the Total Lead Time is 70 minutes.
In this case, two pull requests (PRs) are associated with a single Jira ticket in an overlapping manner, and there is a re-entry into the Jira ticket after the initial completion.
The following table outlines the different stages, their descriptions, formulas, and example calculations.
| Stage | Description | Formula | Example |
|---|---|---|---|
Ticket In-progress Time | The time taken for a ticket to move from the 'Created' state to the 'In-Progress' state. |
|
|
First Commit Time | The time taken to make the first commit after the ticket is in progress. |
|
|
First Pull Request Creation Time | The time taken to create the first pull request (PR) after the first commit. |
|
|
First Pull Request Approval Time | The time taken to approve the first pull request after it is created. |
|
|
Last Pull Request Merge Time | The time taken to merge the last (second) pull request after it is approved. |
|
|
First Continuous Integration Time | The time taken to complete the continuous integration (CI) pipelines for the first time after the last pull request is merged. |
|
|
First Continuous Deployment Time | The time taken for the continuous deployment (CD) pipelines to complete for the first time after the CI process is finished. |
|
|
First Issue Management Done Time | The time taken to mark the issue as 'Done' in the issue management system (e.g., Jira) after the CD process is completed. |
|
|
First Release Time | The time at which the |
|
|
Total Lead Time
Total Lead Time is the sum of all the above stages:
Therefore, the Total Lead Time is 104 minutes.
In this case, two pull requests (PRs) are associated with a single Jira ticket, and the Jira ticket is reopened after the initial release.
The following table outlines the different stages, their descriptions, formulas, and example calculations.
| Stage | Description | Formula | Example |
|---|---|---|---|
Ticket In-progress Time | The time taken for a ticket to move from the 'Created' state to the 'In-Progress' state. |
|
|
First Commit Time | The time taken to make the first commit after the ticket is in progress. |
|
|
First Pull Request Creation Time | The time taken to create the first pull request (PR) after the first commit. |
|
|
First Pull Request Approval Time | The time taken to approve the first pull request after it is created. |
|
|
Last Pull Request Merge Time | The time taken to merge the last (second) pull request after it is approved. |
|
|
First Continuous Integration Time | The time taken to complete the continuous integration (CI) pipelines for the first time after the last pull request is merged. |
|
|
First Continuous Deployment Time | The time taken for the continuous deployment (CD) pipelines to complete for the first time after the CI process is finished. |
|
|
First Issue Management Done Time | The time taken to mark the issue as 'Done' in the issue management system (e.g., Jira) after the CD process is completed. |
|
|
First Release Time | The time at which the |
|
|
Total Lead Time
Total Lead Time is the sum of all the above stages:
Therefore, the Total Lead Time is 164 minutes.
In this case, there are no pull requests (PRs) or commits associated with the Jira ticket, as the ticket ID was not mentioned in the PRs.
The following table outlines the different stages, their descriptions, formulas, and example calculations.
| Stage | Description | Formula | Example |
|---|---|---|---|
Ticket In-progress Time | The time taken for a ticket to move from the 'Created' state to the 'In-Progress' state. |
|
|
First Commit Time | The time taken to make the first commit after the ticket is in progress. |
|
|
First Pull Request Creation Time | The time taken to create the first pull request (PR) after the first commit. |
|
|
First Pull Request Approval Time | The time taken to approve the first pull request after it is created. |
|
|
Last Pull Request Merge Time | The time taken to merge the last pull request after it is approved. |
|
|
First Continuous Integration Time | The time taken to complete the continuous integration (CI) pipelines for the first time after the last pull request is merged. |
|
|
First Continuous Deployment Time | The time taken for the continuous deployment (CD) pipelines to complete for the first time after the CI process is finished. |
|
|
First Issue Management Done Time | The time taken to mark the issue as 'Done' in the issue management system (e.g., Jira) after the CD process is completed. |
|
|
First Release Time | The time at which the |
|
|
Total Lead Time
In this case, since there are no pull requests (PRs) or commits associated with the Jira ticket, several stages in the lead time calculation have zero values. The lead time calculation in this case gets computed based on the time taken for the ticket to move through the "In Progress," "Done," and "Released" states in the issue management system (e.g., Jira).
For the given example, the Total Lead Time is calculated as the sum of all the above stages:
Therefore, the Total Lead Time is 70 minutes.
In this case, a single job is responsible for both the continuous integration (CI) and continuous deployment (CD) processes.
The following table outlines the different stages, their descriptions, formulas, and example calculations.
| Stage | Description | Formula | Example |
|---|---|---|---|
Ticket In-progress Time | The time taken for a ticket to move from the 'Created' state to the 'In-Progress' state. |
|
|
First Commit Time | The time taken to make the first commit after the ticket is in progress. |
|
|
First Pull Request Creation Time | The time taken to create the first pull request (PR) after the first commit. |
|
|
First Pull Request Approval Time | The time taken to approve the first pull request after it is created. |
|
|
Last Pull Request Merge Time | The time taken to merge the last pull request after it is approved. |
|
|
First CI and CD Completion Time | The time taken for the single job to complete both the continuous integration (CI) and continuous deployment (CD) processes after the last pull request is merged. |
|
|
First Issue Management Done Time | The time taken to mark the issue as 'Done' in the issue management system (e.g., Jira) after the CI and CD processes are completed. |
|
|
First Release Time | The time at which the |
|
|
Total Lead Time
Total Lead Time is the sum of all the above stages:
Therefore, the Total Lead Time is 70 minutes.
In this case, a single job handles both the CI and CD processes, so the "First CI and CD Completion Time" stage represents the time taken for this single job to complete both processes. The "First Issue Management Done Time" is zero because the issue is marked as 'Done' immediately after the CI and CD processes are completed by this single job.
In this case, there are separate jobs for the continuous integration (CI) and continuous deployment (CD) processes.
The following table outlines the different stages, their descriptions, formulas, and example calculations.
| Stage | Description | Formula | Example |
|---|---|---|---|
Ticket In-progress Time | The time taken for a ticket to move from the 'Created' state to the 'In-Progress' state. |
|
|
First Commit Time | The time taken to make the first commit after the ticket is in progress. |
|
|
First Pull Request Creation Time | The time taken to create the first pull request (PR) after the first commit. |
|
|
First Pull Request Approval Time | The time taken to approve the first pull request after it is created. |
|
|
Last Pull Request Merge Time | The time taken to merge the last pull request after it is approved. |
|
|
First Continuous Integration Time | The time taken to complete the continuous integration (CI) pipelines for the first time after the last pull request is merged. |
|
|
First Continuous Deployment Time | The time taken for the continuous deployment (CD) pipelines to complete for the first time after the CI process is finished. |
|
|
First Issue Management Done Time | The time taken to mark the issue as 'Done' in the issue management system (e.g., Jira) after the CD process is completed. |
|
|
First Release Time | The time at which the |
|
|
Total Lead Time
Total Lead Time is the sum of all the above stages:
Therefore, the Total Lead Time is 70 minutes.
In this case, the "First Continuous Integration Time" and "First Continuous Deployment Time" stages represent the separate times taken for the CI and CD processes, respectively, as they are handled by different jobs.