Kanban SPEED KPIs

KPI Name

Representation (Single Project)

Tools

Maturity level values

KPI Calculation

On Hover

KPI Name

Representation (Single Project)

Tools

Maturity level values

KPI Calculation

On Hover

Ticket Velocity

 

Line Graph

 

  • Y- Axis - Story Points

  • X- Axis - Weeks

  • Aggregation Method - Sum

Agile Project Management

 

  • Jira

  • Azure

N/A

Ticket velocity measures the size of tickets (in story points) completed in a defined duration

Date Range- <<Velocity>>

Team Capacity

 

Line Graph

 

  • Y- Axis - Hours

  • X- Axis - Weeks

  • Aggregation Method - Sum

Agile Project Management

 

  • Jira

  • Azure

N/A

Team Capacity is sum of capacity of all team member measured in hours during a defined period 

Date Range- <<Capacity Hrs>>

 Number of Check-ins  

helps in measuring the transparency as well the how well the tasks have been broken down. 

Line Graph

  •  Y- Axis - Count 

  • X- Axis - Days

  • Aggregation Method - Sum'

  • Positive trend indication - Increase

Agile Project Management

 

  • Repos

M1: 0-2

M2: 2-4

M3: 4-8

M4: 8-16

M5: >16

  • It is calculated as a Count. Higher the count better is the ‘Speed’

  • Maturity of the KPI is calculated based on the latest value

Date: <<Value>>

Code Build Time 

measures the time a job takes to build the code. 

 

 

Line Graph

  • Y- Axis - Min

  • X- Axis - Weeks

  • Aggregation Method - Average

  • Positive trend indication - Decrease

Agile Project Management

 

  • Jenkins

  • Bamboo

  • Azure pipelines

M1 : > 45 min

M2 : 30-45 mins

M3 : 15-30 min

M4 : 5-15 min, 

M5 : <5 min

  • It is calculated in  ‘Mins’. Lesser the time better is the ‘Speed’

  • Maturity of the KPI is calculated based on the average of last 5 values that corresponds with the maturity scale

Date Range: <<min>>

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

 

Visualization: Text + Table

  • Y- Axis - Percentage

  • X- Axis - N/A

  • Aggregation Method - Average

  • Positive trend indication - Decrease

Agile Project Management

 

  • Jira

  • Azure

Lead time

M1 : > 60 days

M2 : 45-60 days

M3 : 30-45 days

M4 : 10-30 days, 

M5 : <10 days

Open to Triage

M1 : > 30 days

M2 : 20-30 days

M3 : 10-20 days

M4 : 5-10 days, 

M5 : < 5 days

Triage to Complete

M1 : > 20 days

M2 : 10-20 days

M3 : 7-10 days

M4 : 3-7 days, 

M5 : < 3 days

Complete to Live

M1 : > 30 days

M2 : 15-30 days

M3 : 5-15 days

M4 : 2-5 days, 

M5 : <2 day

It is calculated as the sum following

Open to Triage: Time taken from ticket creation to it being refined & prioritized for development

Triage to Complete: Time taken from start of work on a ticket to it being completed by team

Complete to Live: Time taken between ticket completion to it going live.

Each of the KPIs are calculated in 'Days' 

 

© 2022 Publicis Sapient. All rights reserved.