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 5 Next »

Purpose

Portfolio metrics give a bird's-eye view and immediate understanding of the status of the projects in portfolios, programs, or complex projects with several streams based on key metrics.


1. Navigate across portfolio and instantly check delivery status

  1. Browse your organizational structure by scrolling and expanding or collapsing the units to "zoom in" to the projects that caught your eye
  2. Check the delivery status across the units on these metrics: Backlog Health, Sprint Scope Change, Commitment Rate, Burn-up Forecast, Velocity trend, Closed vs Open defects

2. Understand delivery status of the portfolio, its programs and projects


Overview

Let's start with an overview.

On Portfolio Metric Page you can see the following elements:

  1. Metric Name. Currently 6 metrics are tracked across all projects: Backlog Health, Sprint Scope Change, Commitment Rate, Burn-up Forecast, Velocity trend, Closed vs Open defects.
  2. Goals Dialog Button. This button shows the dialog where you can set the Red, Amber or Green threshold for projects, based on the respective Metric Values. Select metrics to display and its order on the board.
  3. Expand/Collapse Structure Button. By clicking this button you can expand/collapse the structure to "zoom in" to Org Units and Projects that caught your eye
  4. Name & Type of Org Unit. By clicking on the name of Org Unit you will open this Unit in a New Tab
  5. Aggregated Metric Bar. This is a simplified view of distribution of all projects in that Organizational Unit into 4 buckets: Red, Amber, Green, Grey
  6. Aggregated Trends for each Metric. It shows how many projects improved this metric and how many have degraded it. 
    1. "▲" means Improved, "▼" means Degraded
    2. "6%" means the percentage of projects among all projects in that unit
    3. "(2)" means the actual number of projects that have improved/degraded this metric
  7. Micro Metric. It shows the following information:
    1. The current value of the metric
    2. If the metric improved/degraded compared to last quarter (average value of a metrics throughout the whole quarter)
    3. "New Red Dot" is shown in the top-right corner if Metric became RED for this project, and it was not RED in the last quarter
  8. Include/Exclude Metric. This button includes/excludes a metric from calculation of aggregation (available in tooltips).
  9. Show More/Show less. By clicking this button you can expand/collapse available metrics  if Unit tracks more than 4 metrics.

Aggregated Micro Metric Explanation

This Stacked bar chart shows the percentage of projects/streams/squads/etc.by status of a respective metric.

All projects in the unit are counted, no matter what the underlying hierarchy is.

In this particular example we can see that

  • around 30% of projects have the metric value in a red zone,
  • around 5% in amber zone,
  • around 5% in green zone,
  • and around 60% either don't track this metric or are excluded from aggregation

If you hover over the stacked bar, you will see the tooltip:

Here you can see (top to bottom):

  1. Quantity of projects that have the metric in red, amber, green zone or do not track the metric
  2. Average value of the metric across all projects in this unit
  3. Table describing changes since last quarter
  4. Button Include/Exclude metric from aggregation.

Goals Settings

Aggregation settings are available by clicking "Goals" button. This is a group of controls to set right context for Portfolio Metrics:

  • Display on the board. It applies to select metrics for displaying them on the Portfolio Metrics board. The selection impacts the whole units list. 
  • Change metrics order. Drag and Drop rows of metrics to select order to display them on the Portfolio Metrics board.
  • Metrics name.  Currently 6 metrics are tracked across all projects: Backlog Health, Sprint Scope Change, Commitment Rate, Burn-up Forecast, Velocity trend, Closed vs Open defects.
  • Thresholds. Set thresholds to track metrics values.

Available Metrics

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:

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.

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:

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:

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



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:

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:

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

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.

Usage Scenarios

The best way to explain the interface is by walking through the usage scenarios

Scenario 1. Quickly find the project that has problems

Starting from the Aggregated Metrics Page in your Portfolio

I see that in Quality Assurance there are a lot of grey projects that don't track the metrics I'm interested in, and there are some red projects that I need to review

Let's expand the structure to see which project contribute the most to the red status

I've expanded the structure and saw that there is a Stream named  2/1/13 that has 0 sprints Backlog Health, so I'll click that stream and see the metrics, and then talk to the Delivery Manager on that Project.

Scenario 2. What if my standards are higher? How will the colours change?

I see these metrics on the page.

I click "Goals" on top of the page

And see the dialog where I can change Thresholds for Red, Amber and Green Values

Let Me change the Commitment Rate Red threshold to 70 and see what happens to my aggregated metrics

As you see, aggregation for Backlog Health Metric has changed, and this happens to all of the units, allowing you to see how your program/organization will look if you set different standards

Scenario 3. Some project needs to be excluded from aggregation

I see a project that clearly needs to be excluded from aggregation because it's unique in some way and aggregated metrics are not applicable to it.

So I just click "Exclude from aggregation" for all metrics in the project and this project is no longer counted in aggregation (value of metrics is "Not Applicable")


  • No labels