10X: Status Report (Capability)

About this report 

The Status Report (Capabilities) is a drill down of the Status Report main views, Financial and Status, for a selected capability. The report isolates specific capabilities that are tied to your portfolios.  

There are two ways to access these reports: 

  1. Click on a capability within a Status Report. 
  2. Select a capability from the main Status Reports menu. 

These reports display in the form of a data table and 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. Capabilities must be created and tied to epics. 
  8. Features must be created and tied to capabilities. 
  9. Stories, with point values, must be created and tied to features.  

How are report values calculated?  

Capabilities 

Values are pulled from the Capabilities page/Capabilities panel. 

  1. Capability name = Click Edit to open the capability’s page, where you can edit the information about the capability. On the capability’s page in the list on the right, click Status Report to get back to the report’s page. 
  2. Description = A short description of the capability. 
  3. Status = Click the square to set the current health status= on track, some risk, or high risk. 
  4. Health = Click any health icon to set the current health status of your project. 
  5. Progress = Progress is driven from the number of story points accepted for stories belonging to the capability. 
  6. Days remaining = Calculated based on the days remaining until the target completion date. 
  7. Project owner = The owner of the capability. 
  8. Entered funnel = The date when the project entered a funnel, which is the date when the capability was created. 
  9. Start/initiation date = This date indicates when a capability will start. It is used to do the strategic planning activities more effectively. This is not the actual start date of the epic based on when the first story is done. This is the target start date based on intentions of the person submitting the epic. 
  10. Target completion date = This date indicates what the target completion date is. It is used to do the strategic planning activities more effectively. It reflects the date the scheduler believes a capability can actually be completed (versus the Portfolio Ask date which is the date the business wants the capability to be delivered). 
  11. Portfolio ask date = 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. 
  12. Acceptance criteria = All acceptance criteria associated with the capability.  
  13. Objectives = All objectives assigned to the capability. 
  14. Risks = All risks assigned to the capability. The colored box next to each risk is determined by the resolution method associated with the risk= Green indicates Resolved, yellow indicated Owned, and red indicates Accepted and Mitigated risks. 
  15. Dependencies = All dependencies associated with the capability. 
  16. Estimates 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. 
  17. Notes = User-defined notes to annotate the report. 

 How to interpret this report 

Executives should use the data in the reports to review overall status of capabilities in a portfolio. The primary focus should include an evaluation of schedule, budget, risk, scope, quality, and progress. Additionally, the report includes the acceptance and success criteria, objectives, risks, and dependencies the capabilities has, as well as the features associated with this capability.

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.