Purpose
Defects Average Lifetime (all priorities) shows an average lifetime (in days) for defects on a project, all prioritieshow much time on average a defect spends in a development cycle.
How metric helps
Defects Average Lifetime (all priorities) helps to monitor and analyze quality assurance process in the project, 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 Defects Average Lifetime (all priorities) in amount of days. Suggested acceptable indicator value is less then 30 days. 
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 when defects were in open and in progress statuses during last 90 days not "Done" status/ number of these all defects)
where,
Calculation is based on issues in "Open" and "in Progress" states, closed within last 90 days.
RAG thresholds: Red - metric value > 30; Green - metric value = < 30.
| Info |
|---|
Assumptions1 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> Scope Management > Definition of Work Buckets > Defects 3 "Done" status is a status from "Done" bucket in Project Settings>Data Sources>Task Tracking System>Workflows. 4 Invalid defects are excluded from the calculation. Invalid defect is that conforms to Project Settings ->Data Sources ->Task Tracking System ->Quality Management ->Criteria for invalid defects. |
Data Source
Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|