Page tree
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 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 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.

ART PI Objectives

Issues of the type "Objective (Program)" that have been scheduled in the selected PI are shown here. Furthermore all ART's Teams 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.


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.

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

ART Kanban Board

Introduction

With the help of an ART's Kanban board, the respective ART is able to collect, analyse, review & prioritize Features and other issues as well as hierarchically link Features with issues from a higher level like Capabilites (Large Solution) or Porftolio 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 colums 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 teams are delivered as standard with Agile Hive (of course, jira administrators can edit the standard configuration.):

  • Feature (Program)
  • Enabler (Program)
  • Objective (Program)
  • Impediment (Program)
  • 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 Planning

Introduction

Under the 'Boards' dropdown in the Global Navigation, select 'View all programs'.

Click on the name of the Program you want to open.

Program Roadmap

The Program Roadmap is a timeline view in which all PIs and their planned features can be seen.

The following actions should be performed in this view:

New Increment Edit Roadmap + Milestone View Increment


Creating a new Program Increment


A Program Increment is a collection of Sprints. You can choose existing Sprints from your team's board, or where there are no existing Sprints, Easy Agile Programs will automatically create them for you. 

Click on "New Increment" to create a new Program Increment:

  1. Give your Increment a Name
  2. StartDate: When does this Program Increment start?
  3. Sprint Length: Are your Sprints 1 or 2 weeks in length?
  4. Sprint Count: Are there 5 or 6 Sprints in your Increment?

Increment Roadmap

In this view you can carry out your desired planning.
To do this, drag and drop ART issues from the right backlog column into the respective sprints of the PI.

Add Milestones

To create a milestone, click the "+ Milestone" button and enter a name and a start date and optionally an end date in the dialog.

Increment Overview

The Increment Overview shows each team, their scheduled work and the dependencies between them. It consists of the Feature Roadmap, a swimlane for each Board in the Program, and is broken up into columns for each Sprint in the Increment. 

This view is an overview of the Program and is not designed for the scheduling of work or creation of dependencies. Team's schedule their work and create dependencies in the Team Planning View. 

Configuring Increment Sprints

The Sprint Length and Sprint Count properties are stored at the Increment level rather than at the Program level. 

This allows a change of cadence during the life of the Program. 

Each team is able to independently manage their Sprints as of the v1.2.0 release. Any future Sprints the team has already created on their board, can be adopted by the Program. All the work scheduled in those Sprints will be reflected in the Program. 

When there are no pre-created Sprints in a Team's board, Easy Agile Programs will automatically create them for you. 


** Please note: for users upgrading from a version before v1.2.0, this is a breaking change. Any Programs created in previous versions will need to be recreated.

To configure Sprints, click on the Name of the Team or the Open this team board text beneath the team name.


If the Team Board has no pre-created Sprints, Easy Agile Programs will automatically create them for you. If there are pre-created Sprints, the Sprints Configuration dialogue will appear.

Each Sprint can be configured via their corresponding dropdown. Here is where you can configure your existing future Sprints, or create new Sprints for the Increment. 


  • No labels