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





7 - Program Level

7.1 - Creating issues at the Program level

So that the Program level 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 Program project. If you have more than one Agile Release Trains (ARTs), select the specific "ART" project you want to work with.

The default issue types are as follows:

  1. Feature (Program)
  2. Enabler (Program)
  3. Risk
  4. Objective (Program)
  5. Impediment (Program)


7.1.1 - Feature (Program), Enabler (Program) and Impediment (Program) issue types

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

  • Summary (enter a short description of the issue)
  • Description (detailed description)
  • Linked Issues (link issues directly )

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

Available link types include:

  1. relates to
    1. is always available.
    2. has no influence on the SAFe hierarchy.
    3. can link to any issue.
  2. ART TO LARGE SOLUTION LINK
    1. is only available at the Program level.
    2. affects the SAFe hierarchy.
    3. can only be linked to issues at the Large Solution level.
  3. ART TO TEAM LINK
    1. is only available at the Program level.
    2. affects the SAFe hierarchy.
    3. can only be linked to issues at the Team 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 in the hierarchy, 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!


7.1.2 - Risk issue type

The following fields are available by default when you create an issue of this type:

  • Summary (short description of the issue)
  • Description (detailed description)
  • Impact (consequences should the risk come to pass)
  • Probability (probability that the risk will occur)
  • Residual Impact (Impact of the risk after all measures have been taken)
  • Residual Probability (probability of occurrence of the risk after all measures have been taken)
  • Linked Issues (link issues directly)
  • Fix Version/s

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

7.1.3 - Objective (Program) issue type



7.2 - Editing issues at the Program level


7.2.1 - Feature (Program), Enabler (Program) and Impediment (Program) issue types

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. Description (detailed description)
    4. Affects Version/s
    5. Fix Versions/s
    6. Linked Issues  (link issues directly)
  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.

7.2.2 - Risk issue type

The following fields are available:

  • Summary (short description of the issue)
  • Description (detailed description)
  • Impact (consequences should the risk come to pass)
  • Probability (probability that the risk will occur)
  • Residual Impact (Impact of the risk after all measures have been taken)
  • Residual Probability (probability of occurrence of the risk after all measures have been taken)
  • Linked Issues (link issues directly)
  • Fix Version/s

7.2.3 - Objective (Program) issue type



7.3 - Viewing issues at the Program level


7.3.1 - Feature (Program), Enabler (Program) and Impediment (Program) issue types

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.

7.3.2 - Risk issue type

In addition to the information described above, that you entered when creating or editing an issue, you will see a "Risk assessment" panel where the following information is visualized: Impact, Probability, Residual Impact and Residual Probability.

7.3.3 - Objective (Program) issue type



7.4 - Program Kanban Board

The Program Board is a Kanban board in which the status of all issues at the Program level for an Agile Release Train (ART). 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 issues do not overload the Kanban Board. You can use this view to change the status from Funnel to Review. You can also add hierarchical links to issues at the higher level using drag and drop via the "Capabilities" panel on the left (below Versions).

Linked issues are then displayed as colored circles on the right of the issue cards as in HOUSE-55.  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.



7.5 - Program 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 Program Dashboard for one Agile Release Train (ART), which contains these reporting gadgets:


  1. ART Progress
    • The ART Progress gadget displays a progress overview of an Agile Release Train in a selected Program Increment. You can also forecast how many of the planned and open Story Points can still be implemented. Learn more about the ART Progress gadget.
  2. Feature Progress
    • The Feature Progress gadget displays selected issues at the Program level for an ART, along with 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 Feature Progress gadget.
  3. Release Burndown
  4. ART Burnup
    • The ART Burnup gadget displays the completed Story Points, the generated Value and/or the days consumed for a selected number of issues over a period of time. Learn more about the ART 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.




7.6 - Program Risk Management

All risks at a Program level are displayed as a list together with their status and impact. Click the "Risk matrix" button to switch the view to a Risk Matrix. You can create and edit new risks in both views. The workflow follows the ROAM method:

  • Resolved
  • Owned
  • Accepted
  • Mitigated



7.7 - Program Roadmap

The Program Roadmap view of an Agile Release Train displays the individual Program Increments and the scheduled issues in a scrollable timeline.

The PIs are visualized as blue boxes with their names in front (e.g. 2019 Inc. 1). The start and end dates can be read on the timeline.

The issues contained in the timeline include the following information:

  • Issue key (crossed out if issue is completed)
  • Summary
  • Issue type icon
  • Status color

7.7.1 - Add a new PI (Button: New Increment)

Click on the blue button "New Increment" on the right to add new PIs. You must enter a PI name in the "Increment Name" field, which is then displayed in the blue boxes described above. The "Start date", "Sprint length" and "Sprint count" fields are used to set the time frame and the desired sprint timing. Clicking the "Create Increment" button creates the PI and it appears immediately in the Roadmap.

7.7.2 - Plan and edit the PI (Button: Edit Roadmap)

Each blue PI box has a an "Edit Roadmap" button that you can use to fill the PI with issues. Existing issues can also be removed from or moved within the PI.

On the right is the Roadmap Backlog, which shows all Program level issues from the selected Agile Release Train. These issues can be allocated to a PI or deallocated using drag and drop.


7.7.3 - View a PI (Button: View Increment)

Each blue PI box has a a "View Increment" button, which displays the selected PI including all scheduled issues at the Program and Team levels.

In this read-only view, the primary goal is to provide you with a complete overview of all scheduled Team issues and their dependencies. The Teams are represented through their Boards and also subdivided according to them (e.g. Team Queen Board or Team Prince Board).

In the "Increment Roadmap" section, click on individual issues, which then also filter the Team Issues to display only their associated issues.

Click the "Dependencies" button to enable or disable displaying dependencies. The button with the three colors next to it allows you to display only certain dependencies.




7.8 - PI planning for Teams

The Teams can access their PI boards as described above and plan their sprints for the selected PIs. The sprints are automatically created and titled. The following actions are explained below:

  1. Define the sprint capacity
  2. Create issues or drag them from the backlog to the sprints
  3. Define & display dependencies

7.8.1 - Define the sprint capacity

The sprints are displayed as columns and are titled accordingly (e.g. Sprint 3 - 2019 Inc. 1). Below the sprint name, the respective sprint capacity must be entered in the grey circles. The sum of the planned Story Points is placed directly in front for comparison. If more Story Points are scheduled in a sprint than the capacity can handle, the sum is shown in red, as you can see in the screenshot.


7.8.2 - Create issues or drag them from the backlog to the sprints

The easiest and fastest way to create issues at the team level and link them directly to program issues hierarchically is as follows:

  • Select the Program level issue in the "Increment Roadmap" section (marked blue as HOUSE-7 in the screenshot)
  • Then move the mouse cursor to the appropriate sprint and click on "New Issue" and fill out the short dialog - done.

If Team issues have already been created but not yet scheduled, click on the "Backlog" button to see them (see second screenshot). Drag and drop these issues to the sprints to schedule them. Use the filter field and "Quick filters" to find the issues you want to plan.

You can quickly define Story Points for all scheduled issues by clicking on the grey circle on the issue and filling it in.

7.8.3 - Define & display dependencies

To define dependencies, you must first display at least one other team from the Agile Release Train. Select one from the "Teams " dropdown list, as shown in the first screenshot. Colored indicators behind the team names show the dependencies that already exist (described below).

Now the team issues can be dragged and dropped onto non-team issues and the dependency is set automatically. Dependencies can have the following three colors:

  1. Green - issue A was planned before issue B (Healthy)
  2. Yellow - issue A and issue B are in the same sprint (At Risk)
  3. Red - issue A was planned after issue B. (blocker)

When you move the affected issues, the color changes automatically. Use the dropdown "Dependencies" to display only specific dependencies, as shown in the second screenshot.





  • No labels