Purpose
Completed Work Items not Estimated in Story
...
Points shows
...
a percentage of work items
...
estimated in Story
...
Points.
How metric helps
Completed Work Items not Estimated in Story Points helps to to analyze what part of work were not to be taken into account during iteration estimationwork is estimated in Story Points 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 Story Points in shows a percentage of completed items which were not estimated but were should. estimated in Story Points.
<picture>
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 Story PointPoints = (Number of all items with status of "Done" items estimated in Sprintstory points/Number of items which not actually estimated in Sprint"Done" items)*100%
where,
Number of items which not actually estimated in Sprint:
- field for Story Points calculation is defined at Project Configuration -> Data Sources -> JIRA -> Customized fields -> Story Points.
- Issue types estimated in Story Points are specified at Project Configuration -> data Sources -> JIRA -> Scope Management -> "Issue types estimated in Story Points"
RAG thresholds: Green - metric value < 5%, Red - metric value >5%.
...
.
RAG thresholds: Red - metric value > 5%; Green - metric value < 5%.
| Info | ||
|---|---|---|
| ||
1 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 Story Points . |
Data Source
Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).
...