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




6 - Large Solution Level

6.1 Creating issues at the Solution level

So that the Solution 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 "Large Solution" project.

The default issue types are as follows:

  1. Capability (LS)
  2. Enabler (LS)
  3. Risk
  4. Objective (LS)


6.1.1 - Capability (Solution) issue type & Enabler (Solution) issue type

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. LARGE SOLUTION TO PORTFOLIO LINK
    1. is only available at the Solution level.
    2. affects the SAFe hierarchy.
    3. can only be linked to issues at the Portfolio level.
    4. es können nur Vorgänge aus der Large Solution mit der Portfolio Ebene verlinkt werden
  3. LARGE SOLUTION TO ART LINK
    1. is only available at the Solution level.
    2. affects the SAFe hierarchy.
    3. can only be linked to issues at the Program 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!

6.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.

6.1.3 - Objective (Solution) issue type

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.



6.2 - Editing issues at the Solution level

6.2.1 - Capability (Solution) issue type & Enabler (Solution) issue type

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.


6.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

6.2.3 - Objective (Solution) issue type

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.




6.3 - Viewing issues at the Solution level

6.3.1 - Capability (Solution) issue type & Enabler (Solution) issue type

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.


6.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.


6.3.3 - Vorgangstyp Objective (Solution)



6.4 - Large Solution Board

The Large Solution Board is a Kanban Board in which all Solution 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 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 via drag and drop via the "PORTFOLIO EPIC" panel on the left (below Versions).

Linked issues are then displayed as colored bubbles on the right of the issue cards as in LARGESOL-11. 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.



6.5 - Large Solution 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 Large Solution Dashboard, which contains three reporting gadgets:

  1. Large Solution Progress
    • The Large Solution Progress 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 Large Solution Progress gadget.
  2. Forecast
    • The 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 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.




6.6 - Large Solution Risk Management

All risks at a Solution 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




  • No labels