10X: Status Report (Status View)

About this report

The Status Report (Status 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 Status view.

In the Status view, you can see a list of projects with health indicators, and track budget, people, quality, risk/issues, and schedule. You can filter the status report either by PI dates or by 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. 

How are report values calculated? 

  1. Status: 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.
  2. Rank: The rank of the epic as defined on the backlog, relative to the current filter being set.
  3. Start / Initiation: This date indicates when the project will start. Start/Initiationis 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.
  4. 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).
  5. Portfolio Ask: The Portfolio Ask date as requested by the business owner during the planning process. This date is set early in the process by the portfolio groups when they do their planning to request the delivery date for an epic.
  6. State: The high-level state of the epic as defined by Not Started, In Progress, or Accepted.
  7. Step: The developmental process step in the value stream the epic is currently in.
  8. Value: The value of the epic on a scale of 1-100 as defined on the Details tab on the epic's page.
  9. Mode: The planning mode set on the epic or capability page on the Finance tab.
  10. Owner: The owner of the project.
  11. Health: The health of the project as subjectively measured by five key indicators: budget, people, quality, risks, and schedule.
  12. Progress: The overall progress of the epic as measured by the percent of defined story points completed to date.
  13. Risks: The number of open risks associated with the project.
  14. Strategy: The strategy the epic is associated with.
  15. Driver: The driver the project is associated with (Strategic Driver for epics or Financial Driver for stand-alone features).
  16. Theme: The theme the project is associated with.
  17. Budget: Budget for the project as entered on the Finance tab of the epic's page.
  18. MVP: Indicator to show if the epic is labeled MVP on the Details tab on the epic's page.
  19. Intake Form fields: The intake form is used to store additional information about an epic. This is the information your organization wants to collect about every project. The data is taken from the Intake Form tab on the epic’s page.
  20. Notes: User defined notes to annotate status report.

Status_reports_status_view.png

 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.