Versions Compared

Old Version 6

changes.mady.by.user Roopa P

Saved on

compared with

New Version Current

changes.mady.by.user Pragyan Sundarray

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Issue type to identify Story

Overview

Definition (Hover Text)

measures the overall work taken in a sprint

Source Tools

Jira, Azure BoardsBoard

Graph type

Line

Filters

Story Count, Total Count

Hover Format on KPI

Sprint Name: <<Value>>

Fields on OverlayExplore

  1. Sprint Name

  2. Story ID

  3. Issue Description

Business Logic

Calculation Formula

It is calculated as No. of stories tagged to a Sprint

Trend

-

Maturity Levels

-

Instance level thresholds

Target KPI value denote the bare minimum project should maintain for KPI

Global Configurations (Field Mapping)

Processor Fields

NA

Mandatory Fields

Project Settings

  1. Navigate to Project Settings: Start by going to the Project Settings in your application.

  2. Access the Mapping Section: Within Project Settings, find and click on the Mapping option.

  3. Mandatory Field: In the Mapping section, you’ll find the Mandatory Field. This is where you’ll configure the necessary global mapping fields.

  4. Configure the Fields:

  • Sprint Name: Provide the custom field that is linked with the Sprint.

image-20240704-073803.pngImage Added

How to Validate KPI

Suggested ways of working

  1. ‘Story count issue type’ is used to identify issues that are considered for Story count issue type

  2. Issues defined in the configuration filter our the from the issues mentioned in the Sprint Report (Completed and Not Completed category)

Sample JQLs

For Eg : project = Xyz AND sprint = 696 AND issuetype in (Story, Defect, Enabler)

Benefits of KPI

How does the KPI help

...

  1. Progress Visibility: Tracking sprintwise issue count provides clear insights into the team's throughput and how much work is being completed each sprint, helping assess performance.

  2. Capacity Planning: It helps in understanding team capacity, allowing better estimation for future sprints and ensuring the workload aligns with team capabilities.

  3. Early Risk Detection: Monitoring the issue count over sprints can highlight trends such as increasing workloads or unresolved issues, which may indicate potential delivery risks.

  4. Continuous Improvement: Tracking issues sprint by sprint supports retrospectives by revealing patterns in task completion and identifying areas for process optimization.