First you need to add this report to your dashboard. To do that, click Add new gadget. In the Add new gadget dialog, click Load all gadgets. Search for the Program Predictability Measure report and add it to your dashboard.

To see more instructions about adding a gadget to your dashboard see Atlassian documentation.

Configuring the report

To configure the report, fill out the fields in its settings (see fields description below).

Image Removed

...

After you have installed Agile Reports, you can add its gadgets to your dashboard. This is a standard procedure and you can find details and instructions in Atlassian documentation.

Configuring the report

To configure the report, perform the following operations:

Ensure you are good on the prerequisites;
Fill out the fields in the gadget settings.

Image Added

Prerequisites

For you to have data on the report, check on the following prerequisites. This is critically important because if your setup is not what SAFe and gadget expects, you will not get proper or any data.

Agile Release Train field exists and is properly set up
1. Single select Jira custom field.
2. This custom field must be created and configured in Jira, not by a 3rd party plugin.
3. It has this exact name "Agile Release Train".
4. It has options configured.
5. This custom field is configured for the projects that you want to report on or is global (recommended).
6. You have tickets that have this ART selected.
Program Increments are set up for each project in the ART
SAFe often uses Jira's FixVersion field for the Program Increments. Therefore, the given prerequisites are applied to Jira native FixVersion field.
1. PIs must have the same start and end dates for each team / project in the ART. In SAFe this is usually the first and last days of the quarter, and PIs are often called something like Q1, 2019 Q1, Q1 '19 or similar
  Note that this doesn't require sprints to start and end at the same time, because in practice some teams may be a day or two off from other teams.
2. PI must have the same name across all teams / projects in the ART.
3. Tickets where you indicate the business value (BV) are all assigned to a PI.
4. PIs for the past periods are marked as complete because the report only accounts for the completed PIs. That is you mark the respective version in the Releases section of each project as released.
Issue type for tracking the business value is configured
1. Use the necessary issue type for tracking the business value or create a new one for this.
  Now the gadget supports the following issue types:
  - Feature – this is a Jira's Epic issue type renamed to Feature using the SAFe EPIC to Feature Translator for Jira.
  - Capability – new issue type that you can create in Jira.
  - Portfolio Epic – new issue type that you can create in Jira.
2. Make sure that all projects inside a particular PI use the same issue type for tracking business value because you select one issue type for the report.
Business Value field exists and is properly set up
1. Number Jira custom field.
2. It must have one of the following names "BV" or "Business Value".
3. This field is configured for the projects that you want to report on or is global (recommended).
4. This custom field is configured to appear in one of the issue types that the gadget supports - Feature (renamed Epic issue type), Capability, or Portfolio Epic.
5. You have business value entered for all tickets that you want to track for the report.
6. BV containing tickets must be marked as done to get into the report because it takes into account only completed work.
  It might happen that a BV containing ticket (Feature for instance) is completed but it has children tickets that are not yet completed. In this case the report will count this feature in but will display a warning so that you take a look at those. Maybe children tickets will need to be tied to another Feature or maybe they will need to be closed, or a Feature - reopened.

Fields description

Field	Description
Program (ART)	Agile Release Train (ART) for which you want to build a report. You can see how work is being delivered across several teams that all belong to one and the same ART. An ART

conceptually

is a Team of Delivery Teams (DTs).

This can be

upwards of 120 folks (max by SAFe's recommendations so if each team has 5 people that would be 24 Delivery Teams)

up to 120 people broken down into Scrum, Kanban, or XP Teams of 5 to 7 individuals ideally. Each DT

is

should be on the exact same

candace

cadence in the PI. For example, the entire PI is on the same 2 week

Sprints

sprints all starting and stoping on the same dates.

Every two weeks some portion of or even all of the DTs would be delivering software to their ART. Once included on the ART further testing, etc. is occurring.

A prerequisite is to have an Agile Release Train custom

Field

field created in Jira. This Jira field corresponds to the Program (ART) field in the report.

Make sure all your projects / teams belong to the same ART because a report shows data for one ART at a time.

PI — program increment

This is FixVersion field in Jira. In 99% of cases the PI will be equal to 3 months but this should not influence the report buildup.

Only PIs that appear in the tickets with the selected ART will be shown, not all possible PIs that are configured in Jira.

Issue type

The issue type that is set up in Jira. For example, there's Feature, Capability or Portfolio Epic.

All these are issue types that we configure, they are not provided by a third party app. The gadget should be configurable where a user should be able to select which issue type is used for capturing the BV.

You select the issue type where the business value (BV) is entered

BV — business value

BV can be calculated in the BV field for

Issue Type

Issue type where the business value (BV) is tracked.

Now the gadget supports the following issue types:

Feature – this is a Jira's Epic issue type renamed to Feature using the SAFe EPIC to Feature Translator for Jira.
Capability – new issue type that you can create in Jira.
Portfolio Epic – new issue type that you can create in Jira.

Info
We plan to add support for the Capability and Portfolio Epic issue types that the Portfolio app provides. Stay tuned for the updates!

Make sure that all projects inside a particular PI use the same issue type for tracking business value because you select one issue type for the report.

Start reporting from

Start point for the report.

The gadget shows five latest completed PIs configured for the selected ART. Once you complete the next PI, the oldest (now 6th) Pi will disappear from the available values in this field.

Select a completed program increment (PI) from which you want to start the reporting, for example, you can select "2019 Q1" to see a report on all work performed in 2019 (Q1, Q2, etc).

Lower Point

The point where a delivered Business Value percentage is still considered to be within the norm. The default is 80%.

BV field

This is your custom field where you track business value (BV).

Info
BV field is independent from the Estimate field in stories or tasks and doesn't affect data on the chart.

BV is calculated in a special custom field that you set up and is captured in one of the following issue types: Feature (renamed Epic field), Capability, or

on

the Portfolio Epic.

All these are issue types that consultants configure, they are not provided by a third party app and not by a gadget. The gadget should be configurable where a user should be able to select which issue type to use for the report. For example, all teams inside a particular Jira use the same BV field but some teams use it inside the Capacity issue type and some - inside the Feature issue type. For the gadget we select tickets of which issue type it should be looking for.The gadget should only calculate

The gadget calculates BV when ticket of the selected issue type (Feature, Capability or Portfolio Epic) and having BV indicated is marked as Done. Until then

we assume

the work is considered as planned (counted in the

planned

Planned BV) but not delivered yet (not counted in

delivered

Delivered BV).

For example, while Features should be completed in a single PI, it is possible that the Feature is not completed and gets re-planned in the next PI

; however in this case the Feature should only show as delivered in the PI it is completed in. So, the BV committed would count for both the first PI and the second, but would only show as delivered in the second PI.Start reporting at

Start date for the report.

Select a completed program increment (PI) from which you want to start the reporting. The latest five PIs are available.

Lower pointThe point where a delivered Business Value percentage should be considered to be still within the norm. The default is 80%

. In that case the BV will be counted in the planned but not in the delivered BV. This will help Program Managers see where the teams overcommitted and plan accordingly.
Refresh Interval	The interval at which you want the gadget to be updated

.

Tips for the Program Predictability Measure report

For you to have a meaningful data on the report, check on the following items:

...

Agile Release Train custom field is a global Jira custom field, that must be created and configured in Jira, not by a 3rd party plugin and it has this exact name.
It will be a single select, so one ticket should only be able to have one value for the ART field.
All projects / teams in the report should belong to one ART because a report shows data for one ART at a time.

...

.

...

A proper issue type for these tickets should be created. This can be one of the following:
1. Feature
2. Capability
3. Portfolio Epic
4. "Epic" issue type that is renamed to "Feature" using the E2F plugin
BV containing tickets must be marked as done to get into the report.

...

Versions Compared

Old Version 8

New Version Current

Key