Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Overview

Definition (Hover Text)

Lead Time is the time from the moment when the request was made by a client and placed on a board to when all work on this item is completed and the request was delivered to the client

Source Tools

Jira

Graph type

Line

Y-Axis: Days

X- Axis: < 1 week, < 2 Weeks, <1 Month, < 3 Months, <6 Months

Filters

Issue type

Hover Format on KPI

<X> Days

Fields on Overlay

  1. Issue ID

  2. Issue Type

  3. Description

  4. Created date

  5. Closed date

  6. Lead time (In Days)

Business Logic

Calculation Formula

Lead time considers the Creation date of an issue and the Closed date on an issue. It calculates the working days between the Closed and the Created date. This is the lead time for an issue

Closed here signifies when an issue goes LIVE i.e reaches the users

So, if a user is visualizing lead time for <1 week, it will consider all issues closed in the last 1 week

Trend

Inversely Proportional - Higher lead time is considered bad

Comparison for <2 weeks and < 1 week

Maturity Levels

M1 : > 60 days,

M2 : 45-60 days,

M3 : 30-45 days,

M4 : 10-30 days,

M5 : <10 days

Maturity is based on Lead time of last 3 months. This aligns with the way maturity is calculated with SPEED and QUALITY KPIs

Instance level thresholds

20 Days

Configurations

Processor Fields

KPI Specific fields

Issue type to be included

Status to identify LIVE issues

How to Validate KPI

Suggested ways of working

Sample JQLs

Benefits of KPI

How does the KPI help

C

  • No labels