Why/What is the ART Backlog Board used for?
The ART Backlog Board in piplanning.io will consist of the Features and Enablers that are being prepared for the upcoming PI planning event.
The ART Backlog is a key input [content readiness] to the PI event as it contains these ART Backlog Items. Just taking the guidance in the SAFe framework, the ART Backlog Board will include:
Highest priority Features/Enablers [in the ART Backlog] for each ART
Read more: ART and Solution Train Backlogs
NEW (October 2024)
You can now filter the Jira Epic or Issue items that will appear on the ART Backlog Board (#5) items based on additional field types. Filtering the ART Backlog Board items (i.e. filtering only the Features that are deemed Ready for the PI Session) can be done with the following fields in Jira:
Labels
Versions (e.g. Fix Versions)
Components
Single-select (customfield)
Multi-select (customfield)
For example, you could filter on just items that have both a Label (eg. “PI24.4”) AND Fix Version (eg. “1.12”).
Scenario 1: ART Backlog Board set up for a PI Session with a single ART
In this scenario, the configuration is as follows:
A single ART Organizational node is added to the #2 Teams tab
The PI Session is being prepared for just this single ART
When configuring the #5 ART Backlog Board, it will be configured to import the backlog work items - Features and Enablers - that will be managed in either a single Jira Project or in multiple Jira Projects. The qualifier here is we are just setting up a PI Session for a single ART. Hint: If you are setting up a session for a Solution Train that consists of multiple ARTs, then scroll down to the next section.
The configuration for a single ART PI Planning event is pretty straightforward, and involves just the configuration in the SAFe PIs > edit the PI Session > tab #5 ART Backlog Board, and the setps are as follows:
Start: RTE Cockpit >> SAFe PIs >> <PI Session Name> >> click Edit
Navigate to tab #5 ART Backlog Board
Edit the existing default Sticky Types or click the +Add another sticky type button
Enter or modify the existing Sticky type Name field.
For example enter 'Feature' or 'Business Feature' or enter the terminology your company uses to identify the unit of work at the ART level
Color / Taken: Select a color for the Sticky Note.
The Taken color allows for the Sticky Note color to change when a Team is assigned to that item.
Sticky function: select Work Item as it will sync to Jira
Mirror: Select the appropriate value from the dropdown field
Select the Jira Project name from the dropdown list
In the Jira issue type field click the dropdown box to select the corresponding Jira object that this Sticky type will sync with in the Jira Project.
Select a value in the Jira WSJF field dropdown
Note: this configuration is optional if you are not using WSJF for prioritization
Enter a value/s in the Filter by Jira Fields section.
Only the highest priority Features are initially included in a PI event.
Single ART PI Session - ART Backlog Board mapped to single Jira Project
Scenario 2: ART Backlog Board set up for a Solution Train (multiple ARTs)
In this scenario, the PI Session supports a Solution Train Organization node, i.e. multiple ARTs.
Prerequisite: RTE Cockpit > ALM Connections > ART Mapping
We will need to complete the ART Mapping tab in the RTE Cockpit > ALM Connections > ART Mapping settings. For a Solution Train PI session, these [ART Mapping] settings are where we configure the linking of the ART Backlogs and their respective Jira Projects (where the Features / Enablers are managed).
Navigate to ALM Connections: RTE Cockpit > ALM Connections
Edit for the ALM Connection
Advance to the ART Mapping tab
Select the ART, and click Edit
Click Add Project, and select the corresponding Jira Project from the dropdown.
Optional, continue adding all the Jira Projects that have the ART Backlog Items Features/Enablers for this ART
IF multiple ARTs share the same 1x Jira Project then use the ART field mapping tab.
Additional details <To Be Provided>.
IF you have 1x Jira Project for the ARTs, use the Team field mapping tab to manage Team assignments on the ART Backlog Items (Features/Enablers).
Additional details <To Be Provided> are here; the ART Backlog Board Team Field Sync documentation.
At this point you can complete the ALM Connection setup, and return to the PI Session > #5 ART Backlog Board to complete the PI Session setup.
Note: See here for the Help Article for details on the ART Field Mapping and Team Field Mapping tabs when setting up the ART Mapping (in ALM Connections).
Filter ART Backlog Board by Jira Fields
Filter the ART Backlog Board to include only the Jira Epics/Issues that meet specific criteria. This is an important step so piplanning.io only synchronizes the Features/Enablers that have a specific value for a certain field in Jira.
For example, you could give the issues a label (eg. “PI6”) or Fix Version (eg. “1.12”).
The following field types may be used to filter session backlog items:
Labels
Versions
Components
Single-select (customfield)
Multi-select (customfield)
In the example above, only Jira Epics in of the ProgramBacklog Jira Project with the Label "PI24.1" AND Fix Version “24.4” will be synchronized on the ART Backlog Board.
An example of the Jira Fields available on the Jira Project that can be used to filter the ART Backlog Board for the specific PI Session.
If you specify multiple Jira Fields, OR multiple values in a field (comma-separated), they will be added together using an AND statement. For example, using the Labels PI6, PI7 will only display Epics which have the Labels PI6 AND PI7 set in Jira.
Keep in mind: Jira Labels do NOT have whitespace characters. Labels containing "/" cannot be used in the Jira Labels field as a filter.
Ranking: ART Backlog Board ranked by WSJF
The stickies on the ART Backlog Board are ranked by the WSJF field value on the bottom right of the Sticky Note. This is the WSJF field for ART Backlog Board items because SAFe® recommends using WSJF for ART Backlog prioritization.
ART Backlog Board with WSJF ranking; highest to lowest.
What if your ART/Solution Train does not use WSJF?
TIP: You can rank the ART Backlog Board by any numeric field, other than the WSJF. A numeric/integer field that is visible on the Jira Epic/Issue screens will be available to select in the Jira WSJF field dropdown.
To configure this setting edit the Jira WSJF field on the #5 ART Backlog Board > Jira WSJF field. The dropdown field will return all numeric fields that are available on the Jira Epic/Issue in your Jira instance.
Assigning Features to Teams
Assign ART Backlog items to Teams, and have that team value synchronize via the Team field mapping tab. Refer to this related article here: Jira Backlog Board team field sync.