10X: Investment Vs. Actuals

About this report

With the Investment vs. Actuals report, you can view the program increment allocation and the actual spend per theme in one report. Select a program increment from the corresponding drop-down menu to generate the report.

This report has two views: program increment budgeting and epic budgeting. The top three charts show how each theme is assigned a percentage of the PI.

Navigation

  1. Select the Reports icon from the left Navigation menu.
  2. Start typing the report's name in the Search box. 
  3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.

Prerequisites

  1. A PI must exist in the system, and be tied to a program.
  2. Themes must be created, tied to the PI, and have % allocations per program set up. 
  3. Epics must be created, tied to Themes and the PI, and have an estimate set for the PI.
  4. Features must be created and tied to the Epics and the PI. 
  5. Stories, with point values, must be created and tied to Features. 
  6. Teams must be created for the program.
  7. At least one sprint must be completed with completed story points for at least one team.
  8. Team members must be assigned to the completed sprint(s) and have allocations set for the sprint(s).
  9. The Team Burn Hours setting must be set to indicate average daily hours a team member works.
  10. The Teams must have the proper track by setting selected, either:
    1. Track by Hours, for Teams that are using Tasks under Stories and entering hours against them.
    2. Track by Points, for Teams that are only using Story points and not tracking hours against tasks.
  11. An hourly rate must exist. Depending on the Portfolio setting for Costing Method, either:
    1. A blended rate, which is entered on the PI.
    2. Cost center rate, which is determined by the cost centers assigned to the team members.
  12. A budget must exist. There are two options available on the report:
    1. Use Program Increment Budget: Set a budget for the entire PI on the PI edit screen.
    2. Use Epic Budget: Set budgets for the individual Epics on the Epic edit screen.

How are report values calculated? 

Budget Pie Chart:

  1. Budget = Budget of PI, OR Sum of Budget of Epics in the PI, Depending on type of budget selected at the top right
  2. Theme Percentages in Chart = Percent allocation of Themes for the PI and Program(s), set on the Theme Planning View accessed from the Investment by Theme page.
  3. Theme Dollar Amounts in Chart = the Budget, as defined above, times the total Percent allocation for the Theme for the Pi and Program(s)

Estimate Pie Chart:

  1. Estimate = Sum of Epic Estimate Cost for all Epics in the PI (see Epic Cost Formula below)
  2. Theme Percentages in Chart = Divide the sum of Epic Estimate Cost per Theme by the total Epic Estimate Cost for the PI, display as a percent
  3. Theme Dollar Amounts in Chart = Divide the sum of Epic Estimate Cost per Theme by the total Epic  Estimate Cost for the PI, display as a dollar amount

Actual Pie Chart:

  1. Estimate = Sum of Story Actual Cost for only Accepted Stories associated through the backlog hierarchy to Epics in the PI (see Story Actual Cost Formula below)
  2. Theme Percentages in Chart = Divide the sum of Story Actual Cost per Theme by the total Story Actual Cost for the PI, display as a percent
  3. Theme Dollar Amounts in Chart = Divide the sum of Story Actual Cost per Theme by the total Story Actual Cost for the PI, display as a dollar amount

How to interpret this report

Variance

If a theme is pulled from the PI, you will see a red arrow with Pulled next to it. If a theme is added during the PI, Added will appear. If dollars trend down, a red down arrow will appear. If dollars trend up, a green up arrow will appear.

  • Budget vs. Estimate is the variance between the budget and estimate.
  • Budget vs. Actual is the variance between the budget and actual.

Budget vs. Actual financial calculations: if PI work estimates are set on the Epic page, split the dollars between the PIs based on estimates. For example: an epic spans two PIs and is set to 6 member weeks in the first PI and 12 member weeks in the second PI. 1/3 of the epic should be calculated in the first PI and 2/3 in the second PI. If no PI work estimates are set on the epics, then spread the dollars across all PIs evenly. If the PI work estimates are set on some of the epics, the actual for the PI, where the information is entered, will be used and the remaining budget will be spread across the remaining PIs.

Allocation and cost

The Allocation and Cost columns have three values:

  • The Budget values are based on the allocations for each theme associated with the PI and set on the Theme Planning View of the Investment by Theme page. The total budget is set on the Program Increment page. The budget from all epics and stand-alone features assigned to the theme is used. The Budget dollar amount under Cost corresponds to the Budget percentage under Allocation.
  • Estimate is based on the number of stories and their points loaded into the PI. The Estimate dollar amount under Cost corresponds to the Estimate percentage under Allocation.
  • The Actual dollar amount under Cost corresponds to the Actual percentage under Allocation. The estimate shows the percent and the dollar amount the team has spent to date. A dollar amount is tied to each story point. The Actual dollars grows as story points are closed under the theme.

Work

This column shows the number of epics, stand-alone features, and stories that are loaded into the PI. It also shows the team weeks and points spent for implementing these working items. No Estimation sections show the total of epics and stand-alone features and orphan stories.

Distribution charts

  • Value Distribution. This chart shows the current PI and nine previous PIs with the breakdown of value points (LOV) between each PI.
  • Effort Distribution. This chart shows the current PI and nine previous PIs with the breakdown of effort points (LOE) between each PI.
  • Feature Category. This chart shows the features associated with this PI split according to their category setting on the Feature page. Point to a portion of the chart to see the percent and count for that portion.
  • Driver. This chart shows the count of drivers from the selected PI. Point to a portion of the chart to see the percent and count for that portion.

Formula reference

Epic Estimate Cost Formula:

  1. Find all Stories Associated through the hierarchy to the epic
  2. Sum the total Effort points for all Stories
  3. If the Epic is in multiple PIs, divide the Effort Points by the percent of Team Weeks estimated for that PI for the Epic
  4. Epic Estimate Cost = Multiply the resulting Effort Points by the Cost Per Point (see Cost Per Point Formula below)

Story Actual Cost Formula:

  1. If the owning Team of the Story is set for Track By Hours:
    1. Costs Per Team Member = For each team member that logged Hours Done on child Tasks of the Accepted Story, multiply the Hours Done by the configured rate (either PI Blended Rate or Cost Center for that team member)
    2. Story Actual Cost =  Sum the Costs Per Team Member
  2. If the owning Team of the Story is set for Track By Points:
    1. Story Actual Cost = Multiply the Effort Points of the Accepted Story by the Cost Per Point (see Cost Per Point Formula below)

Cost Per Point Formula:

  1. Find the teams assigned to stories associated through the hierarchy to epics in the selected PI
  2. For each person on each team, calculate their burn hours per day – this is their % Allocation for the closed sprint times the Max Burn Hours configured for the sprint
  3. Sum of Costs Per Person Per Day = Multiply the calculated burn hours per day by the configured rate (either PI Blended Rate or Cost Center for that team member, depending on Portfolio settings) and sum for all team members
  4. Average Number of Days in Sprint = sum the total days in the last 5 closed sprints for the teams and divide by the number of sprints to get an average
  5. Average Team Cost Per Sprint = Multiply the Average Number of Days in Sprint times the Sum of Costs Per Person Per Day
  6. Average Velocity = Find the average velocity for the teams for the last 5 closed sprints
  7. Cost Per PointAverage Team Cost Per Sprint divided by Average Velocity 
Was this article helpful?
0 out of 1 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.