Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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-items included into calculation 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-items included into calculation 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 ConfigurationTask Tracking Systems (Jira, Rally, TFS/VSTS)Workflow.

Sub item is a sub bug or 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

MetricInclude sub items checkbox affects calculation
Backlog Health

YES

Ready for Development

YES

Sprint Plan Change

NO

Sprint Scope Stability

YES

Sprint Scope Creep

NO

Requirements Rewritten After Became Ready

NO

Personal velocity

NO

Velocity by week/month

YES

Velocity by week (non-defects)

YES

Average Velocity

YES

Velocity: Committed vs. Completed

YES

Commitment Rate

YES

Iteration Scope Conversion

YES (if UoM is items), NO (if Uom is Story Points or Hours)

Iteration Completion Snapshot

YES (if UoM is items), NO (if Uom is Story Points or Hours)

"Not Done" Bucket Review

YES (if UoM is items), NO (if Uom is Story Points or Hours)

Number of Open Work Stoppages

NO

Work Stoppages Life Time

NO

Scrum Cycle Time

NO

Reaction/Resolution Target Fulfillment

NO

Created vs Resolved

YES

Lead and Cycle Time

NO

Open Issue Aging

YES

Throughput

YES

Time in Status

YES

Reaction Time

NO

First Time Right

YES

Delivery Forecast via Burn-up

YES (if UoM is items), NO (if Uom is Story Points or Hours)

Cumulative Flow by status buckets or workflow statuses

YES

Cumulative Flow by status buckets or workflow statuses

YES (if UoM is items), NO (if Uom is Story Points or Hours)

Bug Growth

NO it depends on 'Issue types used for defects tracking'

Defect Containment

NO

Defect Density

NO

Defect Leakage

NO

Invalid Defects

NO it depends on 'Issue types used for defects tracking'

Open Bugs Over Time by Priority

NO it depends on 'Issue types used for defects tracking'

Quality Debt

NO it depends on 'Issue types used for defects tracking'

Reopened Defects

NO it depends on 'Issue types used for defects tracking'

Time spent on bug fixing by month

NO it depends on 'Issue types used for defects tracking'

Top Priority Defects Age Alert

NO it depends on 'Issue types used for defects tracking'

Tasks Not Estimated But Effort Logged 

NO it takes all workflow issue types

Number of Issues in Backlog (out of Sprints) but Already Completed

NO it takes all workflow issue types

Completed Work Items not Estimated in Hours

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN MAN-HOURS

Completed Work Items not Estimated in Story Points

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS

Completed Work Items with Remaining Estimate > 0

NO it takes all workflow issue types

Effort Logged on Completion

NO it takes all workflow issue types

Estimated Items in SP at Sprint Start

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS

Estimated Items in Hours at Sprint Start

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN MAN-HOURS

Completed Work Items Estimated in Hours (last 3 months)

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN MAN-HOURS

Completed Work Items Estimated in Story Points (last 3 months)

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS

Scope Readiness for Development in Active Sprints, % 

NO it depends on 'Issue types to track scope readiness for development'

Items not Ready but in Active sprints

NO it depends on 'Issue types to track scope readiness for development'

Items without Story Points but in Active sprints

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS

Stories Which Are Open/Ready State But With All Sub-tasks Already Closed

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS

Stories Which Are Closed But With Any Sub-tasks Still Incomplete

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS

Number of Items with Effort Logged after Items Were Closed

NO it takes all workflow issue types

Bugs not Attached to 'Affects Version'

NO it depends on 'Issue types used for defects tracking'

Bugs Closed Without 'Fix Version'

NO it depends on 'Issue types used for defects tracking'

Items with Story Points Changed During Last Month

NO it depends on ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS

Items with Original Estimate Changed During Last Month

NO it takes all workflow issue types

Items in Progress with no Changes During Last 2 Weeks

NO it takes all workflow issue types

Work Logged With Dates in The Future

NO it takes all workflow issue types

Number of not Completed Defects (top priorities)

NO it depends on 'Issue types used for defects tracking' and TOP-PRIORITY DEFECTS

Total Number of Not Completed Defects (all priorities)

NO it depends on 'Issue types used for defects tracking'

Top Priority vs Total Defects (%)

NO it depends on 'Issue types used for defects tracking'

Unresolved Bugs Older Than a Month (top priorities)

NO it depends on 'Issue types used for defects tracking' and TOP-PRIORITY DEFECTS

Unresolved Bugs Older Than a Month (all priorities)

NO it depends on 'Issue types used for defects tracking'

Time Spent On Bug Fixing (%)

NO it depends on 'Issue types used for defects tracking'

Defects Average Lifetime (top priorities)

NO it depends on 'Issue types used for defects tracking'

Defects Average Lifetime (all priorities)

NO it depends on 'Issue types used for defects tracking'

Capacity

NO it takes all workflow issue types

Estimation metrics

NO it takes all workflow issue types

Workload

NO it takes all workflow issue type

Example if Include sub items checkbox affects calculation:

Given:

Story 1 with estimate 5 SP

Story has 2 sub tasks: 

  • Sub task 1 with estimate 20h
  • Sub task 2 with estimate 5h
UoMSub-items OFFSub-items ON
ItemNumber of parent issues:  1Number of parent issues + number of sub issues: 1+2=3
Story pointSP for parent issues: 5SP for parent issues  + SP for sub issues: 5+0+0=5
HoursHours for parent issues: 0Hours for parent issues  + Hours for sub issues=0+20+5=25
  • No labels