Versions Compared

Version Old Version 9 New Version 10
Changes made by

Pragyan Sundarray

Roopa P (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Applicability

Scrum-based projects

Definition (Hover Text)

Measures the total number of defects (bugs) linked to closed user stories of a sprint.

Source Tools

Jira, Azure Boards

Graph type

Line chart

Filters

<None>

Hover Format on KPI

Sprint Name: <<Percentage Value>>

Defects: <<Value>>

Closed Stories: <<Value>>

Fields on Explore Overlay

  1. Sprint Name

  2. Story ID

  3. Issue Description

  4. Linked Defects

Business Logic

Calculation Formula

No. of defects tagged to all stories closed in an iteration/ Total no. of stories closed in the iteration.
*Please note:- ‘stories’ denote units of work, not to be confused with ‘User Story’ issue type in Jira

KPI Settings

  1. Issue types to identify as Stories:

    1. Primary → ‘Issue types which will have linked defects’

    2. Secondary → 'Labels to identify issues to be included' can be used to filter the desired set of stories considered in primary setting

      image-20240703-143936.pngimage-20240703-144037.png

  2. Defects field mappings

    1. Priority to be excluded

    2. Root cause values to be included

  3. Workflow Status field mappings

    1. Resolution type to be excluded

    2. Status to be excluded

    3. Default start status for defects

    4. Statuses for issue closure (for both stories and defects)

*Please note:- Global mappings and default Jira statuses of sprint reports will apply if the KPI level settings are not used.

Trend

A downward trend is desirable

Maturity Levels

M1: > 175%

M2: 175% -125%

M3: 125%-75%

M4: 75-25%

M5: 25%


*Please note:- KPI widget denotes the average maturity over data points

Instance level thresholds

Set the desired defect injection rate threshold

Configurations

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

  • Issue Type Mapping

    • Issue Type which will have Liked defects eg; Story Enabler Story, Tech Story

    • WorkFlow Status Mapping

    Status considered for Issue closure eg; Closed, Done, Ready for Delivery

    1. .

    2. Configure the Fields:

    Defect Mapping :

    • Issue Type to identify Defect - all the issue type that signify defect

    image-20240704-094534.pngImage Added

    Issue type Mapping :

    • Issue type for subtask Defect - Any specified issue category will be treated as a subtask that is linked to a story.`

    image-20240704-094622.pngImage Added

    How to Validate KPI

    Suggested ways of working

    1. The issues identified as stories and defects should belong to the sprints of the configured project scrum board

    2. Ensure proper linking of defects with the main user stories since unlinked defects will not be considered

    3. Verify the sprint snapshots of closed sprints

    Sample JQLs

    project in ("XYZ") and component ="ABC" and type in (Defect) and issueFunction in linkedIssuesOf("type in (Story) AND sprint in(406)")

    Best Practices

    Automate Testing

    Implement automated testing (unit, integration, and end-to-end tests) to catch defects early in the development process.

    Pair Programming

    Implement pair programming to increase code quality and reduce the likelihood of defects being introduced.

    Adopt TDD/BDD

    Use Test-Driven Development (TDD) or Behavior-Driven Development (BDD) methodologies to write tests before code, ensuring that functionality is well-defined and tested from the start.

    Use Static Analysis Tools

    Implement static code analysis tools to automatically check code for potential defects and enforce coding standards.

    Benefits of KPI

    Quality Measurement

    It helps in measuring the quality of the code being produced and identifying areas where improvements are needed.

    Predictability

    Understanding the defect injection rate can help in forecasting the amount of rework required and in planning more accurately.

    Cost Reduction

    Reducing the defect injection rate can lead to lower costs associated with fixing bugs, especially those found later in the development cycle or after release.

    Process Improvement

    By tracking this metric, teams can identify stages in the development process where defects are commonly introduced and take steps to improve those stages.