Skip to main content
Version: Next

Requirement Lead Time

What is this metric?

The amount of time it takes a requirement to deliver.

Why is it important?

  1. Analyze key projects and critical points, identify good/to-be-improved practices that affect requirement lead time, and reduce the risk of delays
  2. Focus on the end-to-end velocity of value delivery process; coordinate different parts of R&D to avoid efficiency shafts; make targeted improvements to bottlenecks.

Which dashboard(s) does it exist in

How is it calculated?

This metric equals resolution_date - created_date of issues in type "REQUIREMENT".

Data Sources Required

This metric relies on issues collected from Jira, GitHub, or TAPD.

Data Transformation Required

This metric relies on the 'type-requirement' configuration in Jira, GitHub or TAPD's transformation rules while adding/editing a blueprint. This configuration tells DevLake what issues are requirements.

SQL Queries

The following SQL shows how to find the lead time of a specific requirement.

-- lead_time_minutes is a pre-calculated field whose value equals 'resolution_date - created_date'
lead_time_minutes/1440 as requirement_lead_time_in_days

If you want to measure the mean requirement lead time in the screenshot below, please run the following SQL in Grafana.

with _issues as(
DATE_ADD(date(i.resolution_date), INTERVAL -DAY(date(i.resolution_date))+1 DAY) as time,
AVG(i.lead_time_minutes/1440) as issue_lead_time
FROM issues i
join board_issues bi on = bi.issue_id
join boards b on bi.board_id =
-- $board_id is a variable defined in Grafana's dashboard settings to filter out issues by boards in ($board_id)
and i.type = 'REQUIREMENT'
and i.status = "DONE"
and $__timeFilter(i.resolution_date)
-- the following condition will remove the month with incomplete data
and i.resolution_date >= DATE_ADD(DATE_ADD($__timeFrom(), INTERVAL -DAY($__timeFrom())+1 DAY), INTERVAL +1 MONTH)
group by 1

date_format(time,'%M %Y') as month,
issue_lead_time as "Mean Requirement Lead Time in Days"
FROM _issues

How to improve?

  1. Analyze the trend of requirement lead time to observe if it has improved over time.
  2. Compare the requirement lead time of each project/team to identify key projects with abnormal lead time.
  3. Drill down to analyze a requirement's staying time in different phases of SDLC. Analyze the bottleneck of delivery velocity and improve the workflow.