Purpose
Tasks Not Estimated But Effort Logged shows the amount of items without estimates but with a logged effort.
How metric helps
Tasks Not Estimated But Effort Logged metric helps to track cases when effort is tracked for non-estimated or zero-estimated tasks. It can influence the results of iteration because this effort was not taken into account during an iteration estimation. It is expected this indicator value is equal to zero.
How metric works
Chart overview
Chart shows a number of tasks with null or “0” estimate and Logged effort > 0.
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
Tasks Not Estimated But Effort Logged is a number of items, where an item satisfies the criteria: estimate filed (in SP/Hours) of an item is empty or "0", but effort is logged.
RAG thresholds: Red - metric value > 0; Green - metric value = 0.
Assumptions
1 Calculation considers completed items within the last 90 days.
2 "Include sub items into metrics calculation" setting affects this metric.
3 Estimate field for an item to track an estimate absence is taken from Project Settings>Data Sources>Task Tracking System>Scope Management>Issue types to be estimated in Story Points/Man hours.
4 If an issue/work item type is selected in Issue types to be estimated in Story Points, "0" value in Story Points field is to be considered.
5 Field for estimates to be checked is set in Project Settings>Data Sources>Task Tracking System>Fields mapping.
Data Source
Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).