Number of Issues in Backlog (out of Sprints) but Already Completed
- Anastasia Baranouskaya
- Denis Olevanov (Unlicensed)
- Natallia_Mendzel@epam.com
Purpose
Number of Issues in Backlog (out of Sprints) but Already Completed shows the amount of items at the moment which are completed but not assigned to a sprint.
How metric helps
Number of Issues in Backlog (out of Sprints) but Already Completed helps to point out loss in a sprint velocity. The expected metric value is 0.
How metric works
Chart overview
Chart shows a number of completed items without an assignment to a sprint - 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
Number of Issues in Backlog (out of Sprints) but Already Completed is a number of items in a "Done" status where a sprint field value is empty and excluding invalid defects.
RAG thresholds: Red - metric value > 0; Green - metric value = 0.
Assumptions
1 Calculation considers all completed items got from the task tracking system.
2 "Done" status is a status from "Done" bucket in Project Settings>Data Sources>Task Tracking System>Workflow.
3 Invalid defect is a defect with a resolution selected in 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.).