The Spend per Point report displays a program’s rolling Spend per Point value for anchor sprints within a program increment. Program Spend per Point is the average cost of delivering a story effort point, during the previous five anchor sprints (including the current active anchor sprint). This value is a rolling average, and changes as sprints within the PI progress. Program Spend per Point is an important value, as it is used to calculate Forecasted Spend, Estimated Spend, and Accepted Spend values.
You can use the report to identify the program’s Spend per Point value inside of a specific anchor sprint, and see how it moves over time. You can also see what teams in the program contribute to Spend per Point, and identify outliers inside of teams that may negatively impact your calculations.
The Spend per Point Report is available from the Reports landing page. Quick links to the report are also available when viewing detailed info inside of the Forecasted Spend and Estimated Spend panels.
For the report to display data, you must choose one or more programs and one or more program increments in the Configuration bar.
Use and configure the report
Use the Program dropdown to select which program you want to view Spend per Point data for.
Use the Anchor sprint dropdown to select which anchor sprint you want to view Spend per Point data for. This report uses anchor sprints, as they are common time periods used by all teams within a program and PI.
Inside the Teams grid, select the View outliers link to the right of a team’s row to navigate to the Team Spend per Point report, filtered by the selected team. There, you can view and correct team outliers. If you see a Manage sprint link instead, this means multiple team sprints have been associated with the same anchor sprint. Click the link to navigate to the Sprints page where you can correct the issue.
Use the View Portfolio room button in the top-right corner to leave the report and navigate to the Portfolio Room.
You can share the report by clicking the branching icon in the upper-right corner. Next, click Copy link to copy the URL of the page with its Configuration bar settings, which you can share with other Jira Align users.
Values displayed in the report
- The Program Spend per Point value for the selected program and anchor sprint, and the increase or decrease in value since the previous anchor sprint.
- The selected anchor sprint’s name, start date, and end date.
- The count of teams that contributed to the selected anchor sprint, and the number of teams added or removed since the previous anchor sprint.
- The list of teams that contributed to the selected program and anchor sprint.
- The team’s name.
- The team’s scrum master.
- The number of outliers identified for the team. Click to view the Team Spend per Point report for the team.
Interpret the data on the report
The primary use case of the Spend per Point report is to identify any data outliers across teams that may be skewing the program Spend per Point value for a given sprint. Outliers include missing resource rates and incorrect allocations through the info cards at the top of the report and the count of outliers that display to the right of each team row.
Dive into outliers by clicking the View outliers link on a team’s row in the Teams grid. You’ll be navigated to the Team Spend per Point report for that team, where you can view descriptions of outliers for allocations, number of points delivered, and cost settings.