Skip to end of metadata
Go to start of metadata


Level Selection

Program Level


Navigation

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. These colors can also be seen in the context tab of your Feature.

The illustration shows a full SAFe configuration with four levels. To access an Agile Release Train drill down to the Program Level and select the desired ART.

ART PI Reports

Introduction

The Agile Hive ART Reports show an automated view of all relevant information about an Agile Release Train in a specific PI.


Usage

You can access the reports in the following ways:

  1. Select the desired ART in the Agile Hive Menu.
  2. Within an ART project, click on the Agile Hive icon in the project sidebar.

The Agile Hive ART Reports consist of a PI Selection dropdown and the following five tiles which are described in more detail below:

  1. ART Members
  2. Overall ART PI Progress
  3. ART PI Overview
  4. ART PI Objectives
  5. ART Risks

PI Selection

The information within the tiles is based on your PI selection. You can access PIs 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 ART Members and ART Risks tiles remain unaffected. You can also filter for PIs using the search field.

The current PI is always displayed automatically.

ART Members

The ART Members tile introduces all ART 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 ART 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 ART 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 ART's teams is shown here. It doesn't matter whether a sprint is in a past PI.

SP Burned (Story Points burned)

Comparison between planned and completed story points of the ART's teams. 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 ART capacity.

ART PI Overview

This section lists all planned ART issues. The parent issue is also shown and can be collapsed. Without parent, issues are categorized in the "Issues without parent" group.

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 team columns you can see which teams are working on which features based on the story points.

To change a team's icon, open the "Details" view in the project settings and upload the desired image. After that, reset the browser cache.

ART PI Objectives

In this widget, issues of the type "Objective" that have been assigned to the selected PI are displayed. (Agile Hive 3.48.1 and older: Only Objectives that have been linked to a scheduled issue in the selected PI will be shown.) 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.


Features can be linked to an ART PI Objective using the "Belongs to Objective" link.

ART Risks

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

In the following, we will show you the four specific risk drop-downs 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.

ART Kanban Board

Introduction

With the help of an ART's Kanban board, the respective ART is able to collect, analyze, review & prioritize Features and other issues as well as hierarchically link Features with issues from a higher level like Capabilities (Large Solution) or Portfolio Epics.


Navigation

An ART Kanban board can be easily accessed via the Agile Hive menu in the top navigation bar. First click on the respective ART 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 Features to Capabilities or Portfolio Epics

In the backlog view of an ART Kanban board, you can hierarchically link Features with higher level issues using drag and drop.

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

Then the relation is shown in the Feature (PRO-3) as Lozenge (Compatible with An...):


If you have linked to the wrong issue, you can simply drag the Feature 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.

Print Features & other Jira issues

Every Jira issue can be printed out with Agile Hive - either individually, in sprints or based on a JQL.

This function is used both during PI planning for the analog program board and in teams that generally want to work with analog boards.


Print individual Features

Open the desired Feature and click on the InstaPrinta button on the right.

In the InstaPrinta Print Wizard, select "Agile Hive Feature" as the template and either click "Save as PDF" or, if set, click Print.

Print individual columns from the ART Kanban Board

Open the "Kanban Board" view of the desired ART and click on the InstaPrinta button on the right.

In the InstaPrinta Print Wizard, select "Agile Hive Feature" as the template.

In the selection field you also have the option to print only issues that are in a certain column.

Finally, either click "Save as PDF" or, if set, click Print.

Print issues based on a JQL

Open the Jira search, insert your JQL and click on the InstaPrinta button on the right.

In the InstaPrinta Print Wizard, select "Agile Hive Feature" as the template and either click "Save as PDF" or, if set, click Print.

Feature Creation

Introduction

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

  • Feature
  • 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 ART 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 ART's Kanban Board.

PI Management

Managing Program Increments (PIs)

With Agile Hive, PIs can be created per ART. The respective sprints / iterations are then automatically created in the teams.
The user who creates the PIs must have the "Manage Sprints" permission in all child projects of the respective ART.

Creating new PIs

  1. Open the desired ART project in which the PIs 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 PI".
  4. Fill in the fields of the PI dialog & click the "Confirm" button.

After creation, PIs can be selected in the dropdown 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 program boards of a specific PI.

Editing PIs

  1. Open the desired ART project in which the PIs should be edited via the Agile Hive menu.
  2. In the reports view click on the PI dropdown at the top right & select the PI which should be edited.
  3. Again click on the PI dropdown and click on "Edit PI".
  4. Make the desired changes & click the "Confirm" button.

Note: Only future PIs can be edited.

Deleting PIs

  1. Open the desired ART project in which the PIs should be deleted via the Agile Hive menu.
  2. In the reports view click on the PI dropdown at the top right & select the PI which should be deleted.
  3. Again click on the PI dropdown and click on "Delete selected PI".
  4. Select whether to delete all corresponding Sprints and click the "Permanently delete PI" button.

Note: All PIs including the current PI and past ones can be deleted. Be careful, this step can not be undone.


Program Board

Introduction

There are two ways to open a Program Board:

Option 1

  1. Select the desired ART from the Agile Hive menu in the top navigation bar which will display the Agile Hive ART Report.
  2. Now click on the "Program" button.

Option 2

  1. Select a team from the Agile Hive menu in the top navigation bar which will display the Agile Hive Team Reports.
  2. Now click on the "Program" button.

This view is designed to facilitate a conversation between two or more teams, working out how best to schedule work based on the desire to fulfill the Feature outcomes of the Increment.

Program Board

The Program Board is generated automatically on the basis of the PI planning. Teams are represented as swimlanes and herein you can view all planned ART work items, their dependencies and the time of the delivery.

Dependency Management

Agile Hive displays dependencies visually in the Program Board and the Breakout Overview.

You can set dependencies with the Agile Hive Dependency Link:

  • This link type links issues to dependent issues.
  • It consists of the two link directions "requires" and "is required by".
  • Link two issues with the desired link direction.

Understanding Dependency Health:

  • A green line indicates the dependent issue is scheduled in a sprint before its dependency (healthy).
  • An orange line indicates the dependent and dependency are scheduled in the same sprint (a risk).
  • A red line indicates the dependent issue is scheduled in a sprint after the dependency (critical blocker).

You can filter the visibility of dependencies via the [...] button.




External Dependencies

The Program Board is also capable of displaying dependent issues that do not belong to the ART or its teams. We call them 'external dependencies'. This means that external dependencies are displayed of other ARTs, other teams or from other projects, that are completely detached from Agile Hive.

In order to achieve this, proceed as follows:

  1. Link an external issue from any Jira project (i.e. also from a Team, ART, Large Solution or Portfolio project) with either 'requires' or 'is required by' with an ART issue that has been planned in a PI.
  2. The external issue must be scheduled in the current PI using the "Due Date" or "Sprint" field.
    a) Set a 'Due Date' for the external issue. (You may have to add the 'Due Date' field in the respective screen first.) The date must be within the PI period.
    b) Alternatively, an iteration from the date range of the current PI can be selected in the "Sprint" field of the external issue. 

This displays the corresponding project as a swimlane with the label 'EXTERNAL'. Within the swimlane all the dependent issues are shown with their individual dependency line and their due date.

This page was last edited on 11/09/2022.