Versions Compared

Version Old Version 1 New Version Current
Changes made by

Aleksandr Bogush

Zhanar (Unlicensed)

Saved on

Key

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

Units of Measure for metrics

All of the aggregated metrics are calculated based on the set units of measure per project. For example, if you set it to "Story Points", them Backlog Health will be counted based on story points estimation.

You can change the setting in Project Configuration → Project Settings

...

Backlog Health

This aggregates the values of the metric Backlog Health.

Sprint Scope Change

This aggregates the values of the metric Sprint Plan Change.

Counting method:

Code Block
breakoutModewide
Sprint Scope Change = (abs(added_items) + abs(removed_items))/items_in_sprint_on_sprint_start

Where

  • added_items - number of tickets added to sprint since sprint start

  • removed_items - number of tickets removed from sprint since sprint start

  • items_in_sprint_on_sprint_start - number of tickets in sprint at the moment of sprint start

Aggregation goes by the value of the last sprint for the project 

Commitment Rate

This aggregates the values of the metric Commitment Rate.

Forecast

This aggregates the values of the metric Delivery Forecast via Burn-up.

Info

Calculation notes

  1. Metric displays Forecast with Scope Creep value.

  2. Forecast is calculated for whole project.

  3. Units of Measure is based on setting in "Project Configuration → Project Settings → What is the primary units of measure on this project?"

  4. If Units of Measure is Story Points, then metric is calculated based on issues types according to Data Source Configuration → Task Tracking System → Scope Management →  "ISSUE TYPES EXPECTED TO BE ESTIMATED IN STORY POINTS". If it is not empty, then calculation is performed for this issues. If it is empty, then all issue types available for the project are calculated.

  5. If Units of Measure is Hours or Items, then metric is calculated based Burn-up chart setting → View in

Velocity trend

Velocity trend shows a percentage of changing average velocity within last 4 weeks in comparing to the average velocity in the last 13 weeks (rolling average).

Counting method if unit start date was more than 4 weeks but less than 13 weeks ago:

Code Block
breakoutModewide
Average Velocity Trend = (Average Velocity for the last 4 weeks * 100%)/Average velocity for the all completed weeks from the unit start date

Counting method if unit start date was more than 13 weeks ago:

Code Block
breakoutModewide
Average Velocity Trend = (Average Velocity for the last 4 weeks *100%)/Average velocity for the last 13 weeks
Info

Calculation notes

  1. Only completed weeks are calculated, no future ones;

  2. End of a week is a UTC midnight between Saturday and Sunday (i.e. as per US notation);

  3. Metric value could be different from values on Average Velocity due to Average Velocity is displays rounded values.

  4. Metric is calculated if unit start date more than 4 weeks ago. If less then "No Data" is displayed on a micro-metric.

Closed vs Open Defects

Closed vs Open defects shows a difference of Fixed and Opened defects (over last 4 calendar weeks) as a percentage to a number of all open defects in the backlog as of 4 calendar weeks back.

Counting method if backlog has defects:

Code Block
breakoutModewide
Closed vs Open Defects = (sum(Closed Defects for the last 4 weeks) - sum (Open defects for the last 4 weeks)) / Number of Defects in the backlog on the start of the last 4 weeks *100%

Counting method if backlog has no any defects:

Code Block
breakoutModewide
Closed vs Open Defects (zero backlog) = (sum(Closed Defects for the last 4 weeks) - sum (Open defects for the last 4 weeks)) / 1 *100%
Info

Calculation notes

  1. Only completed weeks are calculated, no future ones;

  2. End of a week is a UTC midnight between Saturday and Sunday (i.e. as per US notation);

  3. Metric Units of measure is items.

Insert excerpt
Integrations
Integrations
nameCopyright
nopaneltrue