Versions Compared

Old Version 7

changes.mady.by.user Roopa P

Saved on

compared with

New Version Current

changes.mady.by.user Roopa P

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
The Created vs Resolved KPI measures the balance between new issues or tasks created and those resolved, helping teams track productivity, identify bottlenecks, and ensure efficient work management. By maintaining a healthy balance, teams can improve efficiency, meet deadlines, and deliver high-quality results

Overview

Definition (Hover Text)

gives an idea about The Created vs Resolved KPI measures the speed at which the team closes the defects that are raised during a sprint. It provides insights into the team’s efficiency in handling and resolving defects.

Source Tools

Jira, Azure Boards

Graph type

Line + Column Chart

Filters

Total Defects, Added defects

Hover Format on KPI

Created Defects - <<Value>>

Resolved Defects - <<Value>>

Resolved Percentage -

Fields on Overlay

  • Sprint Name

  • Created Defect ID

  • Issue Description

  • Defect added after Sprint

  • Resolved Status

Business Logic

Calculation Formula

  1. Created

defects consider

  1. Defects:

    • This includes all defects

which

    • that are initially tagged to the

Sprint

    • sprint or are added to the sprint

in between

    • during its duration.

  2. Closed Defects:

    • This includes the defects

are the completed defects i

    • that are resolved and closed within the sprint out of the created count.

Trend

Higher the Resolved trend, better is the qualityA higher trend in resolved defects indicates better quality and efficiency, as it shows the team is effectively closing the defects they raise.

Maturity Levels

Compare Resolved defects with Created Defects

M1: Velocity is 0-40%

M2: Velocity is 40-60%

M3: Velocity is 60-75%

M4: Velocity is 75-90%

M5: Velocity is >90%

Instance level thresholds

-Target KPI Value denotes the bare minimum a project should maintain for a KPI.

Configurations

Processor Fields

  • Defect Mapping

    • Issue Type to identify defects 

Mandatory fields

  • Workflow Status Mapping

    • Status to identify Completed Issue

How to Validate KPI

Suggested ways of working

Sample JQLs

Benefits of KPI

How does the KPI help

project = "Your Project Name" AND issuetype in standardIssueTypes() AND resolved >= startOfDay(-7) AND resolved <= endOfDay()

Best Practice

Consistent Tracking

  • Ensure that all defects are consistently tracked and updated in the system to maintain accurate data.

Regular Reviews

  • Conduct regular reviews of the created and resolved defects to identify trends and areas for improvement.

Effective Communication

  • Maintain open communication between the development and testing teams to ensure defects are addressed promptly.

Benefits of KPI

Efficiency Measurement

  • Helps identify bottlenecks in the defect resolution process, allowing for targeted improvements

Quality Assurance

  • A higher resolved trend indicates that defects are being addressed quickly, leading to higher overall product quality.

  • Helps in reducing the backlog of unresolved defects, ensuring a cleaner and more stable codebase.

Customer Satisfaction

  • Faster resolution of defects leads to fewer issues for end-users, enhancing customer satisfaction.

  • Improves the reliability of the product by ensuring that defects are not left unresolved for long periods.

C