Lead Time and Cycle Time report
Lead Time report is a metric used in Agile software development to track the time it takes for a team to complete a user story or a feature from the moment it is added to the backlog until it is released to production.
The Lead Time report helps the team to identify and understand the bottlenecks in the development process, to measure the team's productivity, and to estimate delivery times more accurately.
The Lead Time report is different from Cycle Time, which measures the time it takes for a team to complete a user story or a feature once they start working on it.
Lead Time includes Cycle Time, but also takes into account the time a user story or feature spends waiting in the backlog, being reviewed, or waiting for deployment.
By monitoring and analyzing the Lead Time report, the Scrum Master and the team can improve their development process, identify areas for improvement, and deliver value to the customer more quickly and efficiently.
Input parameter | Notes |
|---|---|
Scope |
Project, filter of any JQL to select Jira issues. |
Report Type | "Lead time" - to calculate time between issue creation and the latest completion. or "Cycle time" - to calculate time between any first "In progress" status and the last completion. |
Days previously | The 'Days Previously' parameter defines the number of days, counting from the past until today, to include in the report. Only issues updated during this defined time period will be processed and included in the report. This parameter must be set as a positive number. |
Time Tracking Unit | How will the time difference be displayed? You can choose to show it in 'minutes', 'hours', or 'days'. |
Show Data Table | The 'Data Table' is a structured representation of the data used in the chart. You can select the 'Show Table' option to display the report's data in a tabular format. |
Show Report Sources | The Sources table explains how the report was calculated. It shows all the issues from the 'Scope' that were updated within the last 'Days previously' days. Not all issues are included in the report; any skipped issues are marked as 'skipped' with an explanation provided. |