Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Purpose

Completed Work Items not Estimated in Hours shows a percentage of work items (e.g. tasks, sub-tasks and whatever applicable in your project) which that are supposed to be estimated in Hours hours but they are not actually estimated. Checked for last 3 months.

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. 

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. in hours.

<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 Hours  = (Number of all items with status of "Done" items estimated in Sprinthours/Number of items which not actually estimated in Sprint"Done" items)*100%

where,

Number of items which are not actually estimated in Sprint:

  • field for Story Points calculation is defined at Project Configuration -> Data Sources -> JIRA -> Customized fields -> Hours;
  • Issue types estimated in Hours are specified at Project Configuration -> data Sources -> JIRA -> Scope Management -> "Issue types estimated in Hours"

.

RAG thresholds: Red - metric value > 5%; Green - metric value < 5%

Info
titleAssumptions

1 Calculation considers completed items within the last 90 days.

2 Issue/work item types selected in Issue types to be estimated in Man hours are to be considered. 

3 Field for estimates 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.).