See the table below for a quick view of the different financial values displayed for various work items and timeboxes in Jira Align. For a more detailed walkthrough, see Financial Values and Calculations.
Financial value | Where to view | How it's calculated |
Epic Forecasted Spend |
|
Sum of: (Program PI forecast estimate) * (Program Spend per Point) For each program / PI combination the epic is associated with. |
Capability Forecasted Spend |
|
Sum of: (Program PI forecast estimate) * (Program Spend per Point) For each program / PI combination the capability is associated with. |
Feature Forecasted Spend |
|
Sum of: (Program PI forecast estimate) * (Program Spend per Point) For each program / PI combination the feature is associated with. If a feature is associated with more than one program, the estimate from each program row in the Forecast tab of the feature’s Details panel is used to calculate this value. |
Theme Estimated Spend |
|
Sum of: (Feature’s estimate) * (Primary program’s Program Spend per Point) For each child feature parented by the theme. |
Epic Estimated Spend |
|
Sum of: (Feature’s estimate) * (Primary program’s Program Spend per Point) For each child feature parented by the epic. |
Capability Estimated Spend |
|
Sum of: (Feature’s estimate) * (Primary program’s Program Spend per Point) For each child feature parented by the capability. |
Feature Estimated Spend Stand-alone Feature Estimated Spend |
|
(Feature’s estimate) * (Primary program’s Program Spend per Point) The estimate can be found in two locations on a feature’s Details panel:
|
Program Increment Estimated Spend |
|
Sum of: (Feature’s estimate) * (Primary program’s Program Spend per Point) For each child feature or stand-alone feature planned for the program increment. |
Theme Accepted Spend |
|
Sum of: Story Accepted Spend (point-based) and/or Story Accepted Spend (hourly-based) For each accepted child story parented by the theme. |
Epic Accepted Spend |
|
Sum of: Story Accepted Spend (point-based) and/or Story Accepted Spend (hourly-based) For each accepted child story parented by the epic. |
Capability Accepted Spend |
|
Sum of: Story Accepted Spend (point-based) and/or Story Accepted Spend (hourly-based) For each accepted child story parented by the capability. |
Feature Accepted Spend |
|
Sum of: Story Accepted Spend (point-based) and/or Story Accepted Spend (hourly-based) For each accepted child story parented by the feature. |
Story Accepted Spend (point-based) |
|
(Story’s effort point estimate) * (Team Spend per Point from the sprint the story is planned for) A story’s Accepted Spend value is calculated as point-based when the team that delivers it has Points selected in the team’s Track By setting. |
Story Accepted Spend (hourly-based) |
|
(Total hours logged for tasks parented by the story) * (Weighted Cost Rate) A story’s Accepted Spend value is calculated as hourly-based when the team that delivers it has Hours selected in the team’s Track By setting. |
Program Increment Accepted Spend |
|
Sum of: (Story’s effort point estimate) * (Team Spend per Point from the sprint the story is planned for) For each accepted child story planned for the program increment. |
Team Cost per Sprint (Also known as Team Spend per Sprint) |
|
Sum of: (Team member’s allocation percentage) * (Burn hours set in team’s Details panel) * (PI Blended Rate or Cost Center Rate) * (Number of days in sprint) For each team member. This value is stored on the last day of the sprint. |
Team Spend per Point |
|
(Team Cost per Sprint) / (Sum of effort points from stories accepted in the sprint) Team Spend per Point is a value unique to each sprint. |
Program Spend per Point |
|
Sum of: (Sum of normalized Team Spend per Point values from each team in the program) / (Number of teams in the program) From the previous five sprints, divided by 5.
This value is a rolling average. *Normalized means that the Team Spend per Point values are averaged on a common scale in order to make them comparable between teams. This is common in mathematics when comparing multiple values of different sizes on different scales. |
Weighted Cost Rate |
|
Sum of: ((Team member task hours logged for a story) / (Total task hours logged for a story)) * (Team member’s Cost Center Rate or PI Blended Rate) For each team member that logged hours working on a story's child tasks. |
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.