Introduction

All views and information are immediately accessible via the Agile Hive menu in the Top Navigation Bar.
The Agile Hive menu updates itself automatically based on the settings made in the project hierarchies, which are maintained by Jira administrators.

Usage

Click on the Agile Hive menu so that the fly out appears.
Here you can directly access the views provided for each SAFe level. The layers use different colors for better differentiation.
The illustration shows a full SAFe configuration with four levels. To access a Solution Train drill down to the Solution Train Level and select the desired Solution Train.

Managing Planning Intervals (PIs)

With Agile Hive, PIs can be created per Solution Train for its associated ARTs. The respective sprints / iterations are then automatically created in the teams.

The user who creates the PIs must have the "Manage Sprints" and "Browse Projects" permissions in all child projects of the respective ARTs.

Creating new PIs

1. Open the desired Solution Train project in which the PIs for its associated ART projects are to be created via the Agile Hive menu.
2. In the reports view click on the PI dropdown at the top right.
3. Click on "Create new PIs".
4. Fill in the fields of the PI dialog & click the "Confirm" button.

After creation, PIs can be selected in the dropdown of all associated ARTs at the top right. This means that every user can switch to past, future and current PIs in order to view the reports, Breakout Boards or ART boards of a specific PI.

Notes

• All PIs including the current PI and past ones can be deleted. Be careful, this step can not be undone.
• Start and end times of PIs and Iterations are displayed in the local time of the currently logged-in user. Agile Hive uses the timezone information configured in the Jira user profile to calculate local times.
• When the last remaining PI on ART level is disconnected from its Solution Parent PI, either by deleting the PI or by disconnecting via editing, the Solution PI is going to be deleted.

Introduction

The Agile Hive Solution Train Reports show an automated view of all relevant information about a Solution Train in a specific PI / time span.

Usage

You can access the reports in the following ways:

1. Select the desired Solution Train in the Agile Hive Menu
2. Within a Solution Train project, click on the Agile Hive icon in the project sidebar

The Agile Hive Solution Train Reports consist of a Time Span Selection dropdown and the following five tiles which are described in more detail below:

1. Solution Train Members
2. Overall PI Solution Train Statistics
3. Solution Train PI Progress Overview
4. Solution Train PI Objectives
5. Solution Train Risks

PI / Time Span Selection

The information within the tiles is based on your PI / Time Span selection. You can access those via the dropdown at the top right.

As soon as you select a different PI, all information within the tiles is updated based on your PI selection.

The Solution Train Members and Risks tiles remain unaffected. You can also filter for PIs using the search field.

The current PI is always displayed automatically.

Solution Train Members

The Solution Train Members tile introduces all Solution Train members with avatar, name and role.
Clicking on the respective avatar takes you to the Jira profile view of a team member.

You can add new Solution Train members by hovering over the tile and clicking the pen that appears in the upper right corner.

This opens the editing dialog. Here you can add new members using the "+ Add team member" button.
Of course you can also edit oder remove existing members.

Overall Solution Train PI Progress

This tile shows you five easy-to-read metrics and their progress (except velocity).

Velocity

The velocity of the last five sprints of the entire Solution Train is shown here.

SP Burned (Story Points burned)

Comparison between planned and completed story points of the entire Solution Train. The progress is also shown in percent.

Days Passed

Shows how many days the PI has in total and how many have already passed.

Business Value

The generation of the business value is calculated on the basis of the planned and the actual business value of each Team's PI Objectives.

Load vs. Cap (Load vs. Capacity)

Comparison between all scheduled story points and Solution Train capacity.

Solution Train PI Overview

This section lists all planned Solution Train issues. The parent issue is also shown and can be collapsed. Without parent, issues are categorized under "Independent Issues".

The progress (in percent) as well as the planned, open and completed story points are visible line by line. The overall progress is shown in the last total line.

In the ART columns you can see which ARTs are working on which Capabilities based on the story points.

To change an ART's icon, open the "Details" view in the project settings and upload the desired image.

Filter issues in the Solution Train PI Overview

To tailor the Solution Train PI Overview widget more to your specific needs, you have the option to filter the data shown here using a JQL filter query. The textbox is an autocomplete field that helps you writing a valid query, as it gives you suggestions while you write your JQL clause. In the example, the issues shown are reduced to issues where ART Wiesbaden is involved. But you could also ask for a specific issuetype, status or only issues with other customfield values.

On the right side of the textfield, you find a dropdown with the available quick filters from the Primary Board of the current Solution Train project. These can be applied to the data, too. They will be shown in the textfield and can also be altered or even chained together using the AND operator.

Due to the implementation of the Report data, the "Team and ART issues without parents" can not be filtered. The filter query will only affect the Solution Train PI Overview. Data in other widgets is unaffected!

Hide parent issue groups

With the "Hide parents" button, the issues in the Solution Train Report can be shown in a single, flat list without being grouped by their parent issues. After toggling, the text will show "Show parents". This will restore the view to the standard view with issue groups.

Solution Train PI Objectives

Solution Train PI Objectives that have been linked to a Solution Train issue (i.e. Capability, Enabler) scheduled in the selected PI using the "Belongs to Objective" are shown here. The linked Solution Train issue receives the assignment to the PI via the "Parent of" link to an ART issue that has either been assigned to a PI itself or has a child issue that has been scheduled in a Sprint or PI.

Furthermore all ART PI Objectives and their Team PI Objectives are directly accessible via tabs. In each of those tabs, a distinction is made between Planned and Uncommitted Team PI Objectives. This is important because only the "Plan Business Value" of Planned Objectives is summed up.

This information as well as the plan and actual business value are set directly in the objective issue.

Solution Train issue like capabilities can be linked to a Solution Train PI Objective using the "Belongs to Objective" link.

Solution Train Risks

Regardless of the PI selected, all identified and open Solution Train risks are shown here.

In the following, we will show you the four specific risk dropdowns with their options:

• #1 Impact / #2 Residual impact
  1. Unspecified
  2. Catastrophic
  3. Major
  4. Moderate
  5. Minor
  6. Insignificant
     
     
• #3 Probability / #4 Residual Probability
  1. Unspecified
  2. Almost certain
  3. Very likely
  4. Likely
  5. Unlikely
  6. Very unlikely

Impact and probability are combined as exposure for better readability. Same goes for residual impact and residual probability which are combined as residual exposure.

Introduction

With the help of a Solution Train's Kanban board, the respective Solution Train is able to collect, analyse, review & prioritize Capabilities and other issues as well as hierarchically link Capabilities with issues from a higher level like Portfolio Epics.

Navigation

A Solution Train Kanban board can be easily accessed via the Agile Hive menu in the top navigation bar. First click on the respective Solution Train in the Agile Hive Menu. This opens the Agile Hive Reports. Next, click on the Backlog icon or the Kanban icon in the left project sidebar.

Link Capabilities to Portfolio Epics

In the backlog view of a Solution Train Kanban board, you can hierarchically link Capabilities with higher level issues using drag and drop.

To do this, click on "PORTFOLIO" in the panel column to open the panel. This panel shows the higher level issues. Now you can drag and drop your Capabilities onto a higher level issues to set the hierarchical link.

Then the relation is shown in the Capabilities (GAMEDEV-10) as Lozenge (Construction of ne...).

If you have linked to the wrong issue, you can simply drag the Capabilities again to the correct issue.

Context

If issues have been linked hierarchically, this can be seen in the respective issues via the context tab.

All parents are shown and at hover also the SAFe levels.

Introduction

The Solution Train Roadmap offers an intuitive way to schedule Capabilities and Enablers and show the projected duration of these issues.

Navigation

You can access the Solution Train Roadmap from the Agile Hive View navigation.

• First, move to the respective Solution Train project through the Agile Hive Navigation in Jira
• This opens the Solution Train Reports
• Click on the "Solution Train Reports" in the view Navigation and choose "Solution Train Roadmap"

Usage

Find out more about using the Roadmap by looking on the documentation for the ART Roadmap here.

Roadmap View

Introduction

The following Jira issue types for teams are delivered as standard with Agile Hive (of course, jira administrators can edit the standard configuration.):

• Capability
• Enabler
• Objective
• Impediment
• Risk

Creation

To create one of the above issues, click on the "Create" button in the top navigation bar. Make sure in the "Create Issue" dialog that the desired Solution Train project is selected.

Based on the issue type selection in the dropdown "Issue Type", the fields displayed in the form below may vary.

Example: Only risks contain typical risk fields such as impact or probability.

After the issue has been created, it can be found in the Funnel (Backlog view) of the Solution Train's Kanban Board.