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

Level Selection

Team 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 Story.
The illustration shows a full SAFe configuration with four levels. To access a team drill down to the Team Level and select the desired team.


Team PI Reports

Introduction

The Agile Hive Team Reports show an automated view of all relevant information about a team in a specific PI.


Usage

You can access the reports in the following ways:

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

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

  1. Team Members
  2. Overall Team PI Progress
  3. PI Sprints
  4. Team PI Objectives
  5. Team 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 Team Members and Team Risks tiles remain unaffected. You can also filter for PIs using the search field.

The current PI is always displayed automatically.


Team Members

The Team Members tile introduces all team 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 team 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 Team PI Progress

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


Velocity

The velocity of the last five sprints 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. 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 the Team PI Objectives.

Load vs. Cap (Load vs. Capacity)

Comparison between scheduled story points and team capacity

PI Sprints Overview

Display of all sprints within a PI. Each sprint is represented as a single tile.

The status of a sprint can be recognized by the color of the progress bar at the bottom:

  • Green: Completed Sprint
  • Blue / Gray: Current Sprint
  • No bar visible: Future Sprint

Issues planned by the team are shown indented (for example HONEY-15, 19 or 24). The respective higher-level issue (for example, a feature of the Agile Release Train named "PRO-5") is shown above.

If issues do not belong to a higher-level issue, they are shown under the "Independent Issue" group.

Completed issues are crossed out and the story point value is colored green.

The overall progress is shown in the footer as a colored bar. The values for capacity, planned and burned story points are shown below

Team PI Objectives

Issues of the type "Objective" that have been linked to scheduled issue in the selected PI are shown here.

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.


Stories can be linked to a Team PI Objective using the "Belongs to Objective" link. The "Story Points" column shows how many story points an objective consists of and how many have already been completed.

Team Risks

Regardless of the PI selected, all identified and open team 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.

Team Scrum Boards

Introduction

With the help of a team's Scrum board, the respective team is able to plan, start and close their sprints as well as hierarchically link stories with a feature of their Agile Release Train.

The sprints are created automatically and no longer have to be created manually on team boards (manually created sprints are not supported by Agile Hive).

Kanban teams that are working with Kanban boards are not supported by Agile Hive yet.


Navigation

A team's Scrum board can be easily accessed via the Agile Hive menu in the top navigation bar. First click on the respective team in the Agile Hive Menu. This opens the Agile Hive Reports. Next, click on the Backlog icon in the left project sidebar.

You can view the active sprint using the "Active sprints" icon below


Link Stories to Features

In the backlog view of a team board, you can hierarchically link stories with features from the corresponding ART using drag and drop.

To do this, click on "PROGRAM" in the panel column to open the program panel. This panel shows the features and all other configured issue types of the ART. Now you can drag and drop your stories onto a feature to set the hierarchical link.

Then the relation is shown in the story (AVO-30) as Lozenge (Refresh gentle Ceph...):



If you have linked to the wrong feature, you can simply drag the story again to the correct feature.

Of course, you can still link issues using the standard link button.

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 Stories & 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 story

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

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

Print the active sprint

Open the "Active sprints" view of the desired team and click on the InstaPrinta button on the right.

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

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

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

Print multiple sprints

Open the "Backlog" view of the desired team and click on the InstaPrinta button on the right.

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

In the selection field you also have the option to select which sprints you want to print.

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 Story" as the template and either click "Save as PDF" or, if set, click Print.

Story Creation

Introduction

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

  • Story
  • Enabler
  • Bug
  • Objective
  • Risk
  • Improvement
  • Impediment


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 team 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 team's backlog view.

Team Breakout View (PI Planning)

Introduction

Follow these steps to open the Team Breakout view:

  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 "Breakout" 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 fulfil the Feature outcomes of the Increment.

Setting Sprint Capacity on the Team Planning Board

The planned and set capacity can be found beneath each Iteration's name.

To set the capacity for each Sprint, click on the ( - ) bubble and type your capacity for the Sprint. 

Adding estimates to stories planned in a Sprint will roll the total number of Story Points planned to the top of the Sprint.


Assignment of Features (Feature Lanes)

Open the sidebar to see the top 10 Features from the Program Backlog. These are sorted by WSJF so that the most important Feature is always at the top. The Features can be assigned to the team via drag and drop and will be displayed as Feature Lanes. 

In the background, this has the effect that in the feature itself, the fields 'Teams Involved' and 'Program Increment' are automatically filled with the corresponding values by Agile Hive.

Other teams can still assign these assigned features to themselves in their Breakout Board. A corresponding indicator is then displayed. 

Move Features back into the Program Backlog

If you hover over a Feature Lane, a ... menu appears, with which you can move the feature back into the backlog program. This only works if the feature lane does not contain any issues.

In the next step we break these features down into stories.


Feature Breakdown

There are two options for breaking down a feature into stories. We recommend option 1 as it is much faster and easier.

Option 1 - Create new Stories in the Breakout View

  • In order to break the feature down into stories, team issues can now be created within a Feature Lane. To do this, hover over a free cell in the desired iteration within the Feature Lane. Click on the '+ Add' button that appears and fill in the fields in the Create Screen as you wish. After you have clicked the Create button, the new issue is created, linked hierarchically with the Feature & scheduled in the corresponding iteration.

Option 2 - Assign existing Stories from the Team Backlog

  • Open the backlog sidebar and switch to the team tab. Now you can drag and drop the desired stories into an iteration cell within a feature lane. This option will be released end of January 2021.


Schedule Stories

Stories that have already been inserted within a Feature Lane can either be moved to another iteration using drag and drop or even assigned to a different Feature.


Dependency Management

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

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 dersired link direction

Understanding Dependency Health:

  • red line indicates the dependant issue is scheduled in a sprint after the dependancy (blocker)
  • An orange line indicates the dependant and dependency are scheduled in the same sprint (a risk)
  • green line indicates the dependant issue is scheduled in a sprint before its dependency

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