PERF allows to include and exclude sub-items from metrics calculation. This can be helpful if you need calculate metrics for a project duration/release and sub-items estimation and quantity is no object in this case.
- If the sub"Include sub-items included into calculation" turned on then task estimates and their quantity will be taken into account while calculating metrics (it mostly affects Productivity & Scope and Backlog metrics).
- If the sub"Include sub-items included into calculation" turned off then tasks are not included into the calculation in items at all but estimates are summarized in most Productivity metrics.
To including/excluding sub-items in calculation go to Project Configuration → Task Tracking Systems (Jira, Rally, TFS/VSTS) → Workflow.
| Info |
|---|
Sub-item is a sub-bug or a sub-task. What is considered as a sub-item depends on a Task Tracking System: - JIRA sub-items: sub-issues per native JIRA terminology;
- RALLY sub-items: Tasks (in rally tasks are always children of Story or Defect);
- TFS/VSTS sub-items: child items of ANY parents except Feature or Epic.
|
Metrics calculation dependents from sub-items
...
Include sub items checkbox affects calculation in the following metrics:
...
...
...
...
...
...
...
...
Requirements Rewritten After Became Ready
...
...
...
...
...
- Velocity by week (non-defects)
...
...
...
...
...
...
(if UoM is items), (if Uom is Story Points or Hours) ...
...
...
- (depends on units of measure: if unit of measure is Items then sub-items are calculated only when "Include sub-items into metric calculation" is turned-on. If metric is in Story Points or Hours then Story Point and Hours are calculated regardless of "Include sub-items into calculation" check-box)
- Iteration Completion Snapshot (depends on units of measure: if unit of measure is Items then sub-items are calculated only when "Include sub-items into metric calculation" is turned-on. If metric is in Story Points or Hours then Story Point and Hours are calculated regardless of "Include sub-items into calculation" check-box)
- "Not Done" Bucket Review
...
(if UoM is items), (if Uom is Story Points or Hours) ...
...
Work Stoppages Life Time
...
...
...
...
...
...
...
...
...
...
...
(if UoM is items), (if Uom is Story Points or Hours) ...
Cumulative Flow by status buckets or workflow statuses
...
...
Cumulative Flow by status buckets or workflow statuses
...
(if UoM is items), (if Uom is Story Points or Hours) ...
it depends on 'Issue types used for defects tracking' ...
...
...
...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' ...
Time spent on bug fixing by month
...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' ...
it takes all workflow issue types ...
it takes all workflow issue types ...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN MAN-HOURS ...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS ...
it takes all workflow issue types ...
it takes all workflow issue types ...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS ...
Estimated Items in Hours at Sprint Start
...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN MAN-HOURS ...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN MAN-HOURS ...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS ...
it depends on 'Issue types to track scope readiness for development' ...
it depends on 'Issue types to track scope readiness for development' ...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS ...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS ...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS ...
it takes all workflow issue types ...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' ...
it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS ...
it takes all workflow issue types ...
it takes all workflow issue types ...
it takes all workflow issue types ...
it depends on 'Issue types used for defects tracking' and TOP-PRIORITY DEFECTS ...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' and TOP-PRIORITY DEFECTS ...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' ...
it depends on 'Issue types used for defects tracking' ...
it takes all workflow issue types ...
it takes all workflow issue types ...
...
- (depends on units of measure: if unit of measure is Items then sub-items are calculated only when "Include sub-items into metric calculation" is turned-on. If metric is in Story Points or Hours then Story Point and Hours are calculated regardless of "Include sub-items into calculation" check-box)
- Created vs Resolved
- Open Issue Aging
- Throughput
- Time in Status
- First Time Right
- Delivery Forecast via Burn-up(depends on units of measure: if unit of measure is Items then sub-items are calculated only when "Include sub-items into metric calculation" is turned-on. If metric is in Story Points or Hours then Story Point and Hours are calculated regardless of "Include sub-items into calculation" check-box)
- Cumulative Flow by status buckets or workflow statuses()
Example if Include sub items checkbox affects calculation:
...