Purpose
Number of Issues in Backlog (out of Sprints) but Already Completed shows the amount of issues at the moment which are already completed in the backlog but not assigned to any sprint.
How metric helps
Number of Issues in Backlog (out of Sprints) but Already Completed helps to point out a contribution lost from sprint velocity. It is expected that on the project this health indicator value is equal to zero.
Only valid items are counted here i.e. such ones like "Duplicate", "Rejected", "Cannot reproduce" or similar are not taken into consideration.
How metric works
Chart overview
Chart shows Number of Issues in Backlog (out of Sprints) but Already Completed in amount of
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 measured as a number of items in "Closed" status which haven't sprint (sprint is empty) and exclude invalid items (resolution not in "Won't Fix", "Duplicate", "Cannot Reproduce", "Rejected", "Abandoned - No Consensus", "Obsolete", "Expired", "Won't Do", "Project Closed", "Out of scope", "Canceled").
RAG thresholds: Red - metric value > 0; Green - metric value = 0.
Data Source
Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).