Most PI Planning problems in Jira Align are visible two weeks before the event. The backlog is not ready, capacity is a guess, dependencies live in a spreadsheet, and the Program Room in Jira Align shows a plan nobody trusts. This checklist is the one we use with Release Train Engineers to get Jira Align and the train ready, so the two days of planning are spent on decisions instead of data cleanup.
Why PI Planning readiness in Jira Align matters more than the event
Atlassian’s own guidance for the planning meeting lists the inputs a train should bring: the program vision, the Feature backlog, architectural context, the Program Board, team-level story backlogs, and the risk ROAM report from Jira Align. If any of those inputs is stale, the outputs (team objectives, a dependency map, a ROAMed risk list, and a confidence vote) will be stale too. Readiness is where the real work happens.
Three weeks out: structure and permissions
- Create the Program Increment record with correct start and end dates, iterations, and the IP iteration. Confirm every team on the train is linked to the program and has its iterations generated.
- Check role permissions. The Start Program Increment and Close Program Increment buttons in the Program Room only appear when the role has Save rights for Program Increments, and when the PI is in the right status (Planning to start, In Progress to close). Fix this now, not on day one.
- Confirm the Jira connector sync. Make sure Jira projects, boards, and sprints map cleanly to Jira Align teams and iterations, and that sync errors are cleared.
- Agree on the working agreements for estimation units, feature states, and what “committed” means for objectives.
Two weeks out: backlog and capacity
- Rank the Feature backlog with Product Management, using WSJF or your agreed method. The top features should have acceptance criteria, a business owner, and a rough size.
- Load team capacity for every iteration, including holidays, training, and known support load. Capacity in Jira Align should reflect people, not hopes.
- Pre-split the top features into candidate stories so teams can start breakouts with something real.
- Publish the architectural runway and enablers the System Architect wants in this PI.
One week out: dependencies, risks, and logistics
- Seed known dependencies on the Program Board so teams confirm or reject them during breakouts instead of discovering them late.
- Clean the risk register. Close stale risks from the last PI and add the ones leadership already knows about, ready to ROAM.
- Share the agenda and pre-reading through a Confluence meeting page: vision, business context, architecture briefing, planning context, breakouts, draft plan review, management review, final plan review, and confidence vote.
- Run a dry run of the Program Room and Program Board views with team Scrum Masters, so nobody learns the tool live in front of executives.
During the event: keep the tool honest
Assign one person per team to keep Jira Align current during breakouts. Objectives, dependencies, and risks should be entered as they are agreed, not typed up afterward. After the final plan review and confidence vote, move the PI from Planning to In Progress so the Program Room starts tracking execution against the commitments the train just made.
Common warning signs
| Warning sign | What it usually means | Fix before the event |
|---|---|---|
| Teams load more than 100 percent in the first iteration | Capacity was not updated | Refresh capacity with each Scrum Master |
| Dozens of red dependency lines | Features were not split across teams early | Pre-split top features two weeks out |
| Objectives with no business value scores | Business owners are not engaged | Book business owners for the management review |
| Program Room numbers disagree with Jira | Connector sync errors | Clear sync errors three weeks out |
Frequently asked questions
Why can’t I see the Start Program Increment button?
Either your role does not have Save rights for Program Increments, or the PI is not in Planning status. Atlassian’s knowledge base article on starting and closing a PI walks through the role setting.
How early should we start preparing?
Three weeks is a practical minimum for a train of five to ten teams. Larger trains or a first PI on Jira Align usually need four to six weeks.
Do we need Jira Align to run PI Planning?
No, but at enterprise scale it gives leadership one view of objectives, dependencies, and risks across trains, which is hard to keep accurate in spreadsheets.
How VTPMO can help
We have configured Jira Align and coached Release Train Engineers through PI Planning for organizations such as Visa and the Federal Reserve Banks. See our Scaled Agile and Jira Align services, or talk with us about a readiness review before your next PI.