Page Comparison

Definition (Hover Text)

measures the percentage work completed at the end of a sprint in comparison to the total work in the sprint

Source Tools

Jira, Azure

Graph type

Line

Filters

Commitment type/Scope, Issue Type

Hover Format on KPI

Sprint Name: <<Percentage Value>>

Delivered: <<Count/Size>>

Committed: <<Count/Size>>

Fields on Overlay

• Sprint Name

• Story ID

• Issue Status

• Issue type

• Initial Commitment

• Size

Business Logic

Calculation Formula

It is calculated No. of issues or Size of issues completed/No. of issues or Size of issues committed

Trend

Higher the percentage during a sprint, better forecasting can be done for future sprints

Maturity Levels

M1 - <40%

M2 - 40-60%

M3 - 60-75%

M4 - 75% - 90% , 

M5 - > 90%

Instance level thresholds

-

Configurations

Processor Fields

NA

Mandatory Fields

NA

How to Validate KPI

Suggested ways of working

1. Users can ‘Filter by Issue type’. Upon selection of an issue type from the filter, the trend graph shows the commitment reliability for selected issue type

2. Another filter allows the user to see the delivered percentage w.r.t either

   1. Initial commitment based on Issue count

   2. Initial commitment based on Story Points

   3. Final Scope based on Issue Count

   4. Final Scope based on Story Points

Sample JQLs

NAJQL Query to get the issues committed at the start of a sprint: project = "Your Project Name" AND Sprint in openSprints() AND issueFunction in addedDuringSprint("Your Board Name", "Your Sprint Name")
JQL query to get the completed issues in a sprint: project = "Your Project Name" AND Sprint in closedSprints() AND status in (Done, Closed)

Benefits of KPI

How does the KPI help

1. Making sure the team delivers what they promised on time.

2. Building trust with stakeholders by sticking to commitments consistently.

3. Helping teams stay accountable and focused on achieving sprint goals.