10X: Status Report (Financial View)

About this report

The Status Report (Financial View) displays a roll-up of your portfolios over time at multiple levels of detail—by organization, portfolio, program, theme, program increment, release vehicle, and epic. The reports have two views: Financial and Status. This article covers the Financial view. 

In the Financial view, you can see the hierarchy: company, portfolio, program, a list of prioritized projects, and totals. This view provides a financial statement, but also shows due dates and health status of work items (for example, epics and features). You can filter the status report either by PI dates or a specific date range. Filtering by PI dates is based on the PI selected on the Configuration bar. If PI selection is set to All, the report will filter by the selected program regardless of a PI.

These reports display in the form of a data table, are aimed at the PMO and executives of your company.

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 parent organization must be created.
  2. A portfolio must be created and tied to a parent organization. 
  3. A program must be created and tied to a portfolio. 
  4. A theme must be created and tied to a PI and program. 
  5. PI must exist in the system, and be tied to a program. 
  6. Epics must be created and tied to a program and theme. 
  7. Features must be created and tied to the PI; data must be added to the Financial tab. 
  8. Stories, with point values, must be created and tied to features. 
  9. You must have at least one Sprint/Iteration closed.

How are report values calculated? 

  1. Theme = The theme associated with the epic.
  2. Start / Initiation = This date indicates when the project will start. Start/Initiation is the target date that the development team intends to begin work on the project. This date is not tied to the actual work objects and the sprints or PIs they are associated to.
  3. Target Completion = The target date as defined on the epic's page. It is used to do the strategic planning activities more effectively. It reflects the date the scheduler believes an epic can actually be completed (versus the Portfolio Ask date which is the date the business wants the epic to be delivered).
  4. Health = Ongoing health of the project as defined by the user. This is a subjective evaluation based on the opinion of the epic owner that is designed to supplement the metrics-based data generated by Jira Align.
  5. Budget = Budget for the project as entered on the Finance tab of the epic's page.
  6. Estimate = The estimated cost of all work assigned to the project. Jira Align calculates this by looking at the historical cost of a story point (or T-shirt size, ideal hour, or others) based on the velocity and relevant cost centers of the team assigned to do the work.
  7. Actual = The actual cost of all work assigned to the project that is completed to date. Jira Align calculates this by looking at the historical cost of a story point (or T-shirt size, ideal hour, or others) based on the velocity and relevant cost centers of the team assigned to do the work. Only stories that have the Approved status are included in the calculation of the actual cost.
  8. Projected variance (%) = The difference between the budgeted dollar value of the epic and the estimated dollar value of the epic.
  9. Projected variance ($) = The difference between the budgeted dollar value of the epic and the estimated dollar value of the epic.
  10. Actual variance (%) = The difference between the budgeted dollar value of the epic to date and the actual amount spent on the epic to date. The budgeted dollar amount to date is calculated by taking the budget from the epic form and spreading it evenly over the full date range of the epic using the Start/Initiation and Target Completion dates from the epic page.
  11. Actual variance ($) = The difference between the budgeted dollar value of the epic to date and the actual amount spent on the epic to date. The budgeted dollar amount to date is calculated by taking the budget from the epic form and spreading it evenly over the full date range of the epic using the Start/Initiation and Target Completion dates from the epic page.
  12. CapEx budget ($) = Capital expenditures budgeted for the project as entered on the Finance tab of the epic's page.
  13. CapEx budget (%) = The calculated portion of the epic-level budget that is allocated to capital expenditures (CapEx dollars/budget).
  14. CapEx loaded = All story points or hours associated with capitalized features under the epic.
  15. CapEx actual = All story points or hours associated with the capitalized features under the epic that are marked as done.
  16. CapEx variance ($) = The difference between CapEx budget and CapEx actual.
  17. CapEx variance (%) = The difference between CapEx budget and CapEx actual.
  18. OpEx dollars = Operational expenditures budgeted for the project as entered on the Finance tab of the epic's page.
  19. OpEx percent = The calculated portion of the epic-level budget that is allocated to operational expenditures (OpEx dollars/budget).
  20. External CapEx $ = External capital expenditures budgeted for the project as entered on the Finance tab of the epic's page.
  21. External CapEx % = The calculated portion of the epic-level budget that is allocated to external capital expenditures (external CapEx/(external OpEx + external CapEx)).
  22. External OpEx $ = External operational expenditures budgeted for the project as entered on the Finance tab of the epic's page.
  23. External CapEx % = The calculated portion of the epic-level budget that is allocated to external capital expenditures (external OpEx/(external OpEx + external CapEx)).
  24. Efficiency dividend ($m) = An annual reduction in resources available to an organization applied in $m.
  25. Revenue assurance ($m) = The use of data quality and process improvement methods that improve profits, revenues, and cash flows without influencing demand. Expressed in $m.
  26. Return on investment ($m) = A performance measure used to evaluate the efficiency of an investment or to compare the efficiency of a number of different investments. Expressed in $m.
  27. Spend to date = An amount that is spent to date on developing this epic as defined on the Finance tab on the epic’s page.
  28. Estimate at completion = An estimated sum for completing an epic as defined on the Finance tab on the epic’s page.
  29. Value 1-100 = The value of the epic on a scale of 1-100 as defined on the Details tab on the epic's page.
  30. CAGR = The compound annual growth rate of the project as calculated using financial forecast entered on the Finance tab of the epic's page. CAGR equals (value in the final year, quarter, or month/value in the first year, quarter, or month)^(1/# of years, quarters, or months)-1. The calculation will use either year, quarter, or month depending on the selection made under Administration > Platform TerminologyCalculate NPV, CAGR, and EBITDA by drop-down menu.
  31. EBIDTA = Earnings before interest, taxes, depreciation, and amortization.
  32. Payback period = The number of years required before the initial investment is returned.
  33. IRR = The discount rate % as defined on the Finance tab on the epic's page.
  34. NPV = The net present value of the project as calculated using the discount rate, initial investment, and forecast period from the Finance tab of the epic's page. (Sum {net period cash flow/(1+R)^T} - initial investment). For period cash flow, the calculation will use either year, quarter, or month depending on the selection made under Administration > Platform TerminologyCalculate NPV, CAGR, and EBITDA by drop-down menu.
  35. Capitalized = Shows if the epic is capitalized or not.

 How to interpret this report

Executives should use the data in the reports to review overall status of a portfolio, and various levels of hierarchy. The primary focus should include an evaluation of schedule, budget, risk, scope, quality, and progress. 

Was this article helpful?
0 out of 0 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.