Page tree
Skip to end of metadata
Go to start of metadata





5 - Portfolio level

5.1 - Creating issues at the Portfolio level

So that the "Portfolio Level Structure" and "Portfolio Board" views can display content, issues must be created first. Use the Create button in the top navigation bar to go to the Create Issue screen. Select the "Portfolio" project.

The default issue types are as follows:

  1. Epic (Portfolio)
  2. Enabler (Portfolio)

The Create Issue dialog has been made as simple as possible, so that you can create issues quickly:

  • Summary - enter a short description of the issue.
  • Epic Owner - Select a person to be the Epic Owner in the user selection field.

Additional fields can be configured by an administrator to meet your requirements.

5.2 - Editing issues at the Portfolio level

Once you have created the issue, click the Edit button to add more information to the respective fields. An administrator can configure additional or different fields to meet your requirements.

To be clearer, the fields are grouped into two tabs:

  1. Business Details
    1. Summary (short description of the issue).
    2. Acceptance Criteria (checklist for specific criteria).
    3. Epic Owner (assign a user here with the standard Jira user picker).
    4. Description (description of the issue)
  2. WSJF
    1. Business Value - select a value from the dropdown list: None,1,2,3,5,8,13,20 or 40. Do the same for:
    2. Risk Value
    3. Time Criticality
    4. Job Size

The Weighted Shortest Job First (WSJF) calculation works as follows:

  • Business Value + Risk Value + Time Criticality = Cost of Delay
  • Cost of Delay / Job Size = WSJF

The Cost of Delay and the WSJF are separate fields that are calculated automatically and cannot be changed by the user.

5.3 - Viewing issues at the Portfolio level

Below, we cover the three tasks related to issues at this level:

  1. Automatic page creation in Confluence
  2. Adding links
  3. Organizing issues hierarchically

5.3.1 - Automatic page creation in Confluence

The "Issue Links" panel contains links to seven Confluence pages. These were created with the AutoPage app. Additional information on the status of automatically created pages, is displayed in the AutoPage panel to the lower right of the issue.

Administrators can configure when Confluence pages should be created, in which space, and using which template. Whole page trees can also be created. In this case, the page tree was created when the process was created, linked to the Jira issue, and populated with dynamic content.

Such dynamic content includes, but is not limited to:

  • names of Confluence pages as based on the Jira issue key and its summary;

  • configuration of Confluence macros such as the Jira macro;

  • embedded Jira fields in Confluence pages with live synchronization and page versioning.

The linking between issues is important for building the SAFe artifact hierarchy. To add a link, select More > Link.

The screenshot of the Link dialog shows you the various links available at the Portfolio level:

  1. relates to
    1. is always available.
    2. has no influence on the SAFe hierarchy.
    3. can link to any issue.
  2. PORTFOLIO TO LARGE SOLUTION LINK (nur bei der Full-SAFe Configuration vorhanden)
    1. is only available at the Portfolio level.
    2. affects the SAFe hierarchy.
    3. can only be linked to issues at the Large Solution level.

Links that affect the hierarchy are always displayed in uppercase letters.

Enter or search for the issues you want to link to. You can add links to several issues at the same time.

Note: Only valid issues can be linked to with the "PORTFOLIO TO LARGE SOLUTION LINK", for example the issue "Epic (Portfolio)" cannot be linked with a story at the Team level. This is indicated with a red error message.

Common error: Trying to link several processes that are on different levels. This is not possible. You need to add links level by level!

5.3.3 - Hierarchy

In addition to the information described above, that you entered when creating or editing an issue, the hierarchy is displayed in the Structure panel.

This panel can be expanded or minimized as required. This functions similarly for all issue types.

5.4 - Portfolio SAFe Hierarchy

The "Full SAFe Hierarchy" view displays the SAFe transactions hierarchically. Depending on which SAFe configuration you use, this structure will increase or decrease in size. The following assumes you are using a full SAFe configuration that contains all four SAFe levels:

  • Portfolio
    • Large Solution
      • Program
        • Team

The following is an example structure in Agile Hive (see the screenshot):

  • Epic (Portfolio)
    • Capability (Large Solution)
      • Groups for program increments 
        • Feature (Program)
          • Groups for each team
            • Groups for active, future and completed sprints
              • Story (Team)

To drill down through the levels, click on an arrow icon before any of the issue type or group icons in the "Summary" column.

Note: The Add button in the toolbar works differently in this dashboard and is preceded by a +. You can create issues as usual. Ignore the error message that may appear in this dashboard

5.5 - Portfolio Board

The Portfolio Board is a Kanban Board in which all Portfolio issues are displayed. The columns correspond to the state that Scaled Agile specifies with the SAFe Framework. In addition, the hierarchically subordinate linked issues and the WSJF values are displayed on the individual cards below the summary. An automatic sorting according to WSJF is deliberately omitted (but this can be configured on request).

In the Funnel view ( accessed via the Backlog button in the left column), the Funnel status is displayed separately so that new Portfolio issues do not overload the Kanban Board. You can use this view to not only change the status from Funnel to Review, but also use the Capabilities panel on the left ( below the Versions ) to drag and drop hierarchical links to issues at the lower level.

Linked issues are then displayed as colored bubbles on the right of the issue cards as in PORTFOLIO-85. If there are several links, these are summarized in grey circles indicating the number of links. Hover over the grey circle to see the issue keys of the linked issues.

5.6 - Portfolio Dashboard

Agile Hive provides you with several customizable reporting gadgets for Jira dashboards that provide SAFe context-specific reporting for the different levels of the framework. These include burndowns and burnups, forecasts and multiple real-time progress charts.

On the right, you can see a sample Portfolio Dashboard, which contains three reporting gadgets:

  1. Epic Progress
    • The Epic Progress gadget displays selected issues at the Portfolio level, including initial & current effort estimates, and allows you to compare them with the actual progress at the Team level (based on Story Points). Learn more about the Epic Progress gadget.
  2. Portfolio Forecast
    • The Portfolio Forecast gadget displays the existing and completed Story Points of a Portfolio epic within a specified period of time on a daily basis and is able to predict its completion. Learn more about the Portfolio Forecast gadget.
  3. Burnup
    • The Burnup Gadget displays the completed Story Points, the generated value and/or the days consumed for a selected number of issues over a time period. Learn more about the Burnup gadget.

Additional reporting gadgets can be added to the Portfolio Dashboard as needed.

See detailed descriptions and configuration options for the reporting gadgets in Agile Hive here.



  • No labels