Definition (Hover Text)

explains the effectiveness of sprint planning and sprint execution.

Source Tools

Jira, Azure Boards

Graph type

Line + Column Chart

Filters

-

Hover Format on KPI

Sprint Name:  <<Value>>

Fields on Overlay

• Sprint Name

• Story ID

• Issue Description

• Original Time Estimate

• Total Time spent

Business Logic

Calculation Formula

This KPI is calculated based on 3 parameters and showcases 2 views

Available Capacity: It depicts the total hours available for the Sprint . The capacity can defined in KnowHOW. Refer to Capacity Management

Estimated Hours: Sum of the estimation of all issues taken in the sprint is considered as Estimated hours

Logged Hours: The amount of time team has logged within a Sprint. It is derived as sum of all logged work against issues tagged to a Sprint in Jira

Trend

Maturity Levels

Compare Capacity with Logged work

M1: Velocity is 0-40% or >160%

M2: Velocity is 40-60% or 140-160%

M3: Velocity is 60-75% or 125-140%

M4: Velocity is 75-90% or 110-125%

M5: Velocity is 90% -110% - M5

Instance level thresholds

Configurations

Processor Fields

NA

Mandatory fields

NA

How to Validate KPI

Suggested ways of working

1. Logged work will be represented by line graph whereas Estimated hours are represented by bar graph

2. Estimated hours can be manually entered by users from the Capacity screen in KnowHOW (Settings-->Upload Data-->Capacity)

3. An additional configuration allows to exclude spilled issues from Estimated Hours and Logged Hours calculation

4. Enhanced to include the Original Estimate added in subtasks when calculating the estimation for the main story. (Release 8.0.0)

Sample JQLs

NA

Benefits of KPI

How does the KPI help

1. Ensuring teams use their available time and resources effectively during sprints.

2. Helping prevent overloading or underutilizing team members.

3. Optimizing productivity and maximizing output within the sprint timeframe.