Lead Time
Overview
Lead time is an important metric in project management. It measures the amount of time it takes for a task to move through the entire process from start to finish, including any time spent in various stages such as coding, testing, and deployment. Thus, teams gain a clear picture of the efficiency of their processes.
Besides that, it’s helpful for identifying bottlenecks in the workflow that may be causing delays or slowing down the delivery of work.
Do you know that you can also measure the Cycle Time? Check it out here Cycle Time
Reporting by
In this section you can select what element of work do you want to measure the lead time: Assignees, Projects, Epics or Filters/Custom JQL:
Assignees. The result will be that of calculating the time of the selected assignees. With this option you can select the issue types you want to exclude from the calculation.
Projects. The result will be that of calculating the time of the selected projects. With this option you can select the issue types you want to exclude from the calculation.
Epics. When reporting by epics, the time of the child issues of the selected epics will be computed, but not that of the epics themselves. With this option you can select the issue types you want to exclude from the calculation.
Filters/Custom JQL. The result will be that of calculating the time of the returned issues by the query.
Statuses included in the Lead Time
This metric indicates the time spent working on an issue, from the moment it was created (any where the Status Category is To Do) to the moment the issue is completed or delivered (any where the Status Category is Done).
Remember that issues follow a workflow (set of statuses and transitions that an issue moves through during its lifecycle). The lead time indicates the time spent working on an issue, from the moment it was created (any where the Status Category is To Do to do ), to the moment the issue is completed or delivered (any where the Status Category is Done done):
Goal
Adding a goal to the lead time gadget provides several advantages such as a baseline to improve efficiency in your processes, encourage teams to work better together and increase transparency and accountability.
You can set a time to beat as your metric goal. If you're doing better or worse, we'll notify you with a visual indicator:
Green ring: The first ring indicates if the lead time is within the range 0% to 100% of your goal.
Yellow circle: The second ring indicates if the lead time is within the range 100% to 150% of your goal.
Red circle: The third ring indicates if the lead time is within the range 150% to 200% (or higher) of your goal.
List individual elements
You can select this option to list the different elements individually to display their times. In the following example, we are displaying all the projects in the bottom part of the gadget:
If you choose Filters/Custom JQL you won’t be able to display the elements individually to avoid really large lists that hinder performance.
Configuration
Name your gadget meaningfully, so everyone knows at a glance what it is about and when to use it. Fill out the rest of the fields as applicable, namely:
The datasource, where the source Jira instance is installed.
The Reporting by, select what element of work do you want to measure the lead time: Assignees, Projects, Epics or Filters/Custom JQL
The Statuses, to measure the lead time:
Status when the issue was created. Any status where the Status Category is To Do.
Status when the issue was delivered. Any status where the Status Category is Done.
The Goal for this metric, he time to beat to reach that goal.
The Time is calculated by means of, this is the calculation:
Average. The arithmetic mean, it sums the values of the grouped items and divides the result by the total number of items.
Median. It returns "the middle" value of the range of items of the group/field. If the number of items is even, then, the mean of the two values in the middle is returned.
The List all the individual report elements, to display in the gadget all the times of the items individually.
Finally, indicate if you want to use the current settings for all the compatible gadgets in the dashboard. This option eases the pain of configuring one by one the rest of the gadgets with the same default configuration
FAQ
Â
Â
Integrations
We are working on our growing catalog of Dashboard Gadgets: KPIs and Metrics and Dashboard Integrations: Supported Products, but contact us you want us to expedite a specific one, visit our Help Center.
Dashboards
This gadget is not included in any pre-defined dashboard, check other orphan gadgets:
See also
Log a request with our support team for:
Dashboard Hub Pro, Dashboard Hub for monday.com and Dashboard Hub for Confluence
Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.