Skip to main content
System StatusContact Support
VersionOne Community

Portfolio Item Scorecard

This feature is available in Enterprise and Ultimate editions.

editions-eu.png

Overview

The Portfolio Item Scorecard shows metrics to help you understand the progress and impact of an initiative, feature, or for other portfolio items. Using this data, you can:

  • compare actual and expected progress

  • Understand the remaining work and historical trends on work that has already been delivered

  • See the impact of the portfolio item across your organization

ScorecardPortfolioItem.jpg

Accessing the Portfolio Item Scorecard

Understanding the Portfolio Item Scorecard

The Portfolio Item Scorecard is divided into the following sections and shows metrics for the work assigned directly to the selected portfolio item and to all child portfolio items.

Summary Section

The metrics shown in the Summary section (located at the top of the page) shows metrics representing a roll-up of all work associated with the selected portfolio item.

Portfolio Item Scorecard Summary

  • Progress Gauge. Compares the current percent complete by count, against the expected percent compete based on the defined time range. For a project, the start and end dates are taken directly from the project asset. For a program, the start date is the earliest start date for all projects in the program and the end date is the last end date for all projects in the program.  If there is no end date on the project or any project in a program, no expected percent complete value displays.
  • Work Breakdown Pie Chart. Indicates the amount of remaining work in stories, defects, or test sets. This breakdown is based on count in order to capture all work regardless of estimate.

To calculate the percentage for particular type, divide the number of that type by the total number of all three. To calculate this value, you need to first navigate the a level in your project tree high enough to see all projects containing work for the portfolio item in question. Next, filter the backlog grid to the item in question and note the number of items returned in the grid paging control (1-25 of ????). Then, filter the grid to the specific work item type (Story, Defect, TestSet) and note the number of items returned in the paging control. Now divide the second number by the first number and multiple the results by 100. Round this answer to 1 decimal place.

  • Swag. The SWAG attribute value for the selected portfolio item. To find this value, open the Portfolio Item Details page and look at the SWAG attribute value.
  • Total SWAG. The total amount of SWAG for all tracked open and closed portfolio items and child portfolio items in the project or program. This value is also available on the Portfolio Tree as "SWAG Total". Furthermore, you can also expand a portfolio item in the grid to view the immediate children and their SWAG value. Make sure the grid is configured to show SWAG, and that you are filtering to show closed items. You may also need to configure the Project Navigator to show closed projects as well. A question mark (?) indicates that there are portfolio items with no SWAG value.
  • Estimate. A roll-up of the total estimate value for all stories, defects, or test sets regardless of whether the item is open or closed wherever they exist in the system. This value is available on the Portfolio Item Details page and on the Portfolio Tree grid. You can enable the value for cards on the Portfolio Kanban.
  • Unestimated. Percentage of active work that does not have an estimate value. This value is calculated by dividing the total number of active stories without an estimate by the total number of stories and multiplying the answer by 100. Round that answer to 2 decimal places.
  • Productivity. The average number of storiesdefects, or test sets closed per week for the past 4 weeks. To calculate this number, determine how many items were closed per week for the last 4 weeks. You then find the average and round the value to 1 decimal place.
  • Blocked. The total number of active storiesdefects, or test sets that are currently blocked. This value is available today on the Portfolio Tree by adding the "Blocking Issues - Rollup" column.  You can also add this information to cards on the Portfolio Kanban.
  • Teams. The number of teams that own work.
  • Total Effort/Done. The total amount of effort that has been reported.  This metric does not display if effort tracking is disabled
  • Days. The total number of days remaining before the delivery date.
  • Projects. Shows the number of active projects/child projects assigned to the program, project, or team.
  • Done. The total amount of effort that has been reported against work assigned. Ownership of the work item is not considered when calculating this value nor is the value allocated to the current owners. Effort entered by people that do not not own work assigned to the Team displays in the "None" row. This metric is hidden if Effort Tracking is disabled in your instance.

Charts Section

The Charts section, located in the middle of the page, display the Burn Up and Workitem Cumulative Flow charts that allows you to trend the work associated with the selected portfolio item. The Start date for these charts is the Planned Begin Date attribute on the portfolio item. If this value is not set, the Start Date comes from the Begin Date attribute on Project containing the selected portfolio item. The End date on these charts is chart specific.

Burn-Up

Portfolio Item Scorecard Burn-Up Chart

Indicates, by date, the total Estimate value and how much work has been delivered. There is also a linear projection line (an ideal line) from 0 to the total estimate value in the defined time range. The End Date for this chart is either the Planned End Date value from the portfolio item or the End Date attribute value on the Project containing the portfolio item. If both of those dates are blank, this chart will end on the current Date.

Cumulative Flow

Portfolio Item Scorecard Workitem Cumulative Flow Chart

Indicates, by date, the total number of Stories, Defect, and TestSets by status. This chart does not consider any work items closed before the Start Date. The End Date is always the current date.

Breakdown Section

The Breakdown section (located at the bottom of the page) allows you to decompose the selected portfolio item by specific dimensions. 

  • In the Ultimate Edition, portfolio item metrics can be broken down by Team, Project or Child Portfolio Item. 

  • In the Enterprise Edition, portfolio item metrics can only be broken down by Team.  Clicking on a title will take you to a type specific scorecard for the selected item.

Portfolio Item Scorecard Breakdown

Breakdown by Team

The Team Breakdown section provides insight into the performance of each Team responsible for delivering work for the selected portfolio item.  Each row represents a single VersionOne team that owns work assigned to this portfolio item or any child portfolio item.  Additionally, there is also a row to account for work not assigned to a team.

Breakdown by Project

The Project Breakdown section provides insight into how work for the selected portfolio item is distributed across active Projects in your VersionOne instance. Each row represents a single Project that contains work assigned to this portfolio item or any child portfolio item. There is no Project roll-up; if a parent and child project both contain work, both are listed.

Breakdown by Portfolio Item

The Portfolio Item Breakdown section provides insight into how work for the selected Portfolio Item is distributed across active child portfolio items.   Each row represents an open Portfolio Item with a non-blank status value that is an immediate child of the selected portfolio item.  There is also a row, labeled "Other", which represents work assigned directly to the selected Portfolio Item or work under a open child Portfolio Items that has a blank status value.  Metrics in this breakdown are rolled-up;  each value represents all work below the child, including work in subsequent children.

Breakdown Options

  • Title. The project, program, portfolio item, or team name
  • Progress. Actual percent of completed work.  This value is based on count to account for unestimated items.
    • Actual percent complete is determined by dividing the number of closed work items by the total number of work items multiplied by 100.  

    • The expected percent complete is date based. Therefore it is only displays when an end date is specified. To calculate this value, we divide the number of workdays remaining by the total working days and multiple the result by 100. In this context, a working day is any weekday between the start and end date.

  • Contribution. The amount of total work assigned to the project, portfolio item, or team.  This value is based on count to account for unestimated items.
  • Estimate. A roll-up of the total estimate value for all stories, defects, or test sets regardless of whether the item is open or closed wherever they exist in the system. This value is available on the Portfolio Item Details page and on the Portfolio Tree grid. You can enable the value for cards on the Portfolio Kanban.
  • Unestimated. Percentage of active work that does not have an estimate value. This value is calculated by dividing the total number of active stories without an estimate by the total number of stories and multiplying the answer by 100. Round that answer to 2 decimal places.
  • Breakdown. The remaining work by type (storiesdefects, or test sets). This value is based on count in order account for unestimated items.
  • Productivity. The average number of storiesdefects, or test sets closed per week for the past 4 weeks. To calculate this number, determine how many items were closed per week for the last 4 weeks. You then find the average and round the value to 1 decimal place.
  • Blocked. The total number of active storiesdefects, or test sets that are currently blocked. This value is available today on the Portfolio Tree by adding the "Blocking Issues - Rollup" column.  You can also add this information to cards on the Portfolio Kanban.
  • Total Effort. This value represents the total amount of Effort reported against any workitems that rolls-up to this portfolio item.  Workitems in this context can be Task, Test, Defect, Story, or TestSet.  This value is available today on the Portfolio Item Tree by adding the "Total Done" column.  You can also add this information to cards on the Portfolio Kanban.  This metric is hidden when Effort tracking is disabled in your instance.

Sav

Save

  • Was this article helpful?