Configuring Program Increment Planning in Jira Align for SAFe Teams

The primary challenge in Scaled Agile Framework (SAFe) is aligning high‑level objectives with team‑level execution while maintaining visibility of dependencies and capacity. Jira Align’s Program Increment (PI) Planning feature provides a centralized board where ARTs can allocate capacity, map dependencies, and enforce planning gates before committing to a PI.

Desired outcome

After completing this guide you will have a PI Planning board that:

• Shows each team’s capacity for every iteration without over‑allocation.
• Displays feature‑to‑story breakdowns and visual dependency links.
• Enforces predefined gates (scope, risk, resource) before the PI can be marked complete.
• Provides audit‑ready data for retrospectives and future PI forecasting.

Prerequisites

Before you start, verify the following items are in place:

• Active Agile Release Train (ART): An ART with associated teams and a defined PI cadence (e.g., 5‑iteration PI).
• Jira Software integration: Each team’s Jira project is linked to Jira Align so sprint goals, story points, and custom fields sync automatically.
• Capacity baseline: Historical velocity (story points or hours) from Jira Software for each team is available to set realistic capacity.
• Permissions: You need the "Program" or "Administrator" role to edit PI buckets, capacity, and gate settings.

Procedure

1. Define the PI cadence and create buckets

Navigate to Portfolio > PI Planning. Select the ART and click "Edit PI". Set the PI start/end dates and the number of iterations (buckets) that match your cadence. For example, a 5‑iteration PI would create Bucket 1 through Bucket 5.

Note: Keep the total number of unique bucket configurations per ART below 15 to avoid performance degradation on the planning board.

2. Set team capacity for each bucket

1. On the PI board, select a team from the left‑hand panel.
2. Click the capacity field for Bucket 1 and enter the team’s planned capacity (e.g., 40 story points). Repeat for Buckets 2‑5.
3. After entering values, the board shows a capacity bar; ensure the bar does not exceed 100% for any bucket.
4. Verify that the sum of capacities across all teams aligns with the ART’s strategic target (e.g., ART target 200 story points per iteration).

3. Configure planning gates

Gates act as checkpoints that must be satisfied before the PI can be closed.

1. Go to Administration > PI Planning Gates for the ART.
2. Create a gate named "Scope Validation" with the condition "All Features must have at least one linked User Story".
3. Create a second gate named "Risk Assessment" requiring a completed ROAM (Risks, Owned, Accepted, Mitigated) matrix attached to the PI.
4. Save the gates; they will appear as toggle switches on the PI planning board.

Executing the planning event

Mapping features and user stories

Teams drag Features from the Program backlog into the appropriate bucket. As they break each Feature into User Stories, Jira Align automatically sums the story points against the team’s capacity set in step 2, highlighting any overload in red.

Visualizing dependencies

When a story in Team A requires work from Team B, select the story, click the "Dependency Link" icon, and choose the target story in Team B’s bucket. The board draws a connector; if the dependency points to a later bucket than the dependent story, a program risk flag appears.

Verification and health checks

Before finalizing the PI, run the following checks:

Check type	Method	Expected result
Capacity audit	View the capacity summary at the top of each bucket column	Total story point load ≤ defined capacity for every team and bucket
Sync validation	Export the PI plan (Export > CSV) and compare story points per sprint with Jira Software sprint reports	Numbers match within ±5% tolerance (allowing for rounding)
Health report	Run "PI Planning Health Check" from Reports > PI Planning	No warnings about missing team assignments, misconfigured buckets, or unmet gates

If any check fails, adjust capacity, re‑map work, or resolve dependencies before proceeding.

Recovery options

Because PI planning modifies capacity and gate states, you can revert changes if needed:

• Rollback capacity changes: On the PI board, open the team’s capacity editor and restore the previously recorded values (you can copy them from a prior export or from the audit log).
• Reopen a closed PI: In Administration > PI Settings, change the PI status from "Closed" to "Open" to allow further edits.
• Use audit logs: Navigate to Administration > Audit Reports, filter by "PI Planning" and the relevant date range, then export the log to see who changed capacity or gate settings and revert those actions manually.

Limitations and practical verification

Excessive custom bucket definitions (>15 per ART) can slow the board; monitor performance via the PI Planning Health Check, which flags "Too many buckets" when the threshold is exceeded. Additionally, gate configurations may reset after a Jira Align upgrade; after any version bump, re‑validate gate conditions and capacity sums using the checks above.

To confirm that your PI plan is ready for execution, ensure:

1. All teams show capacity bars ≤100% for every bucket.
2. The health report returns zero errors.
3. Audit log entries for the most recent capacity edits show your user ID and a timestamp.