Page Comparison

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.

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 date for the report.

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