Skip to end of banner
Go to start of banner

PPM - Configuring Program Predictability Measure report

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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

PPM - Fields description

FieldDescription
Program (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) broken down into Scrum, Kanban, or XP Teams of 5 to 7 individuals ideally.  Each DT is on the exact same candace in the PI.  For example, the entire PI is on the same 2 week 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 created in Jira. This Jira field corresponds to the Program (ART) field in the report.

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 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 BV when ticket of the selected issue type (Feature, Capability or Portfolio Epic) is marked as Done. Until then we assume the work is planned (counted in the planned BV) but not delivered yet (not counted in 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%.
Refresh IntervalThe 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:

  1. Agile Release Train
    1. 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.
    2. It will be a single select, so one ticket should only be able to have one value for the ART field.
    3. All projects / teams in the report should belong to one ART because a report shows data for one ART at a time.
  2. Program Increments are set up
    1. PI = Jira's FixVersion field
    2. PIs start and end on the same day for each team. Sprints should also ideally begin/end at the same time for all teams, but in practice some teams may be a day or two off from other teams. This does not impact the way the gadget calculates data. 
    3. PI (FixVersion) must have the same name for every project in the chart.
  3. Tickets for the BV tracking should be configured
    1. 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
    2. BV containing tickets must be marked as done to get into the report.
  4. Business Value
    1. BV field - global custom field in Jira that is previously configured. This field is used to enter business value in one of the three issue types - Feature (renamed Epic issue type), Capability, or on the Portfolio Epic.
    2. BV is manually entered into the BV field, no calculations or additional automation here. 
    3. BV field also is independent from the Estimate field in stories. 

See also

PPM - Using Program Predictability Measure report

  • No labels