After the installation and configuration is complete (step 1 - 4), it is time to set up Program Increments (PIs), create issues & plan some work so that the reports and the other Agile Hive views can present the information.
Please ensure the following before you proceed:
Layers were created in the project hierarchies and each provided with the correct SAFe levels
Projects were created using the Agile Hive project templates
These projects were inserted into the correct layers of the project hierarchies according to their SAFe level
The projects were linked hierarchically
Note: Of course, further projects can be created at any time and inserted into the layers
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
Open the desired ART project in which the PIs are to be created via the Agile Hive menu
In the reports view click on the PI dropdown at the top right
Click on "Create new PI"
Fill in the fields of the PI dialog & click the Confirm button
Repeat the process for other PIs.
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.
Open the desired ART project in which the PIs should be edited via the Agile Hive menu
In the reports view click on the PI dropdown at the top right & select the PI which should be edited
Again click on the PI dropdown and click on "Edit PI"
Make the desired changes & click the Confirm button
Note: Only future PIs can be edited
PIs cannot deleted at the moment. We are already working on this feature.
Since no issues have been created yet, the reports can hardly show anything. If you just want to test agile hive or your configuration, it makes sense to create at least one issue in each project.
The following issues should be created in the respective projects for a Full SAFe configuration:
Furthermore we would like to create a risk and an objective in all projects of the teams, ARTs and solutions.
Before we link the created issues with each other, let's take a look at the four Agile Hive links:
(1) Agile Hive Link
This link type links issues hierarchically, that are located on adjacent layers (layers / SAFe levels cannot currently be skipped).
It consists of the two link directions "Parent of" and "Child of".
Purpose: aggregation of progress and statistics for all reports
(2) Agile Hive Objective Link
This link type links Team Objectives to other planned issues of the same team
You have to link an objective with at least one planned story so that the objective can be seen in the respective PI in the reports (this will be improved soon).
It consists of the two link directions "Belongs to Objective" and "Is Objective of".
Purpose: summation of the story points that contribute to the respective objective in the team report as well as progress display based on the completed story points.
(3) Agile Hive Risk Link
This link type links Risks to other issues, that will mitigate the risk.
It consists of the two link directions "Treats" and "Is treated by".
Purpose: Issues that mitigate a risk are automatically displayed in the Team / Program / Solution Reports.
(4) Agile Hive Dependency Link
This link type links issues to dependent issues.
It consists of the two link directions "requires" and "is required by".
Purpose: Visual dependencies in program & breakout boards
Let us link the created issues:
Link the Portfolio Epic, Capability, Feature & Story hierarchically by starting with the Story and linking it to the Feature with the 'Child of' link. Then link the Feature with the Capability and the Capability with the Portfolio Epic, so that there is a strand across all levels. If the custom epic panel from the optional step 4 has been configured for the projects, the child issues can be linked to the parent issues in the respective Jira board using drag and drop.
Link a Team Objective with a Story from the same team with the "Is Objective of" link.
Link a Risk on Team Level to any other issue with the "is treated by" link.
Link an issue that is dependent from any other issue with the "is required by" link.
Of course, you can also create the links from the second issue. Make sure to use the correct link direction.
Now that we have made all the preparations, we can do the PI planning and bring the Agile Hive reports as well as the team breakout views and the program boards to life.
Select a team from the Agile Hive menu. You are now in the Agile Hive Report for the selected team. Now you can easily switch to the Team Breakout Board and the Program Board using the buttons at the top left.
If the Breakout Board is opened from within a team, it is team-specific and represents the respective team in the first row. The capacity for this team can then be entered here.
If the breakout board is opened via the ART project, the teams are displayed alphabetically and consequently no capacity can be entered.
The Program Board is always displayed identically, regardless of which project it was opened from.
Step 1 - Capacity
Enter the capacity for each sprint of your team
Step 2 - Features & Stories
Open up the Scrum Board of a team and plan the Stories into the sprints
Features that are linked to the Stories with the Agile Hive Link, will be shown as swimlanes automatically
Step 3 - Dependencies
Dependencies are shown automatically for all issues that are linked with the Agile Hive Dependency Link
The Program Board is an automatically generated view and therefore no steps are required here.
The completion of features and other ART issues is calculated automatically with Agile Hive. The respective feature is thus represented in an iteration in which it is completed.
Dependencies that were set via the Agile Hive Dependency Link are displayed visually. In addition, all other planned issues are shown on which the ART issues depend.