Purpose
Completed Work Items
...
Estimated in
...
Hours shows a percentage of work items
...
estimated in Hours
...
.
How metric helps
Completed Work Items not Estimated in Hours helps to analyze what part of work were not be taken into account during iteration estimation. what work is estimated in Hours and what work missed the estimation and thus overlooked in a team velocity.
How metric works
Chart overview
Chart shows Completed Work Items not Estimated in Hours in shows a percentage of completed items which were not estimated but were should. estimated in hours - 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
Completed Work Items not Estimated in Hours Hours = Number of all completed items in Sprint(Number of "Done" items estimated in hours/Number of items which not actually estimated in Sprint"Done" items)*100%.
RAG thresholds: Amber Red - 5% < metric value < 95%; Green - metric value < 5%value >= 95%. G<5%
A > 5%
| Info |
|---|
Assumptions1 Calculation considers completed items within the last 90 days. 2 Field for estimates is set in Project Settings>Data Sources>Task Tracking System>Fields mapping. 3 Issue/work item types taken into the calculation: those selected in Project Settings>Data Sources>Task Tracking System>Scope Management>Issue types to be estimated in Person hours. |
Data Source
Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|