Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Purpose

Defects Average Lifetime (all priorities) shows how much time on average a defect spends in a development cycle.

How metric helps

Defects Average Lifetime (all priorities) helps to monitor, analyze and improve a defect processing flow in a project. It's suggested not to keep a defect open for more than 30 days. It may cause a user's satisfaction decrease and an application overall quality and stability.

How metric works

Chart overview

Chart shows a number of days it usually takes for a defect to be fixed - number in the center. Target value is above the chart.

By click on a chart a pop up appears with the following information got from the task tracking system: 

  • Issue ID

  • Type

  • Priority

  • Summary

Calculation

Defects Average Lifetime (all priorities) = (number of days defects were in not "Done" status/ number of all defects).

RAG thresholds:  Red - metric value > 30; Green - metric value = < 30. 

Assumptions

1 Calculation considers closed items within the last 90 days.

2 Defect is an item of a type set in Project Configuration > Data Sources > Task Tracking System> Quality Management > Issue/Work Item type used for defects tracking.

3 "Done" status is a status from "Done" bucket in Project Settings>Data Sources>Task Tracking System>Workflows.

Data Source

Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).

Copyright © 2024 EPAM Systems, Inc.

All Rights Reserved. All information contained herein is, and remains the property of EPAM Systems, Inc. and/or its suppliers and is protected by international intellectual property law. Dissemination of this information or reproduction of this material is strictly forbidden, unless prior written permission is obtained from EPAM Systems, Inc.

  • No labels