PI Planning overview
What this page is — The map of PI Planning: several teams plan one programme increment (a phase of a project and the sprints under it) together, each on its own board, against one shared clock, and the result is merged and committed to the tasks once.
Planning teams
What this page is — The standing teams your organisation plans with: who is in each team, in which role and at what share of their time, who leads it, and which projects it plans in. Teams live in Organization Settings; each project picks the teams that plan in it.
Session set-up, brief and team boards
What this page is — Everything that happens before and around the planning itself: creating a PI session, the Brief tab where the facilitator decides which team plans which category, publishing, and the Team boards tab where each team plans its own work.
Running the live session
What this page is — The controls that run a PI session while it happens: the session bar with the shared clock, the facilitator's buttons, the Broadcast to everyone, who is online, and the Discussion tab where teams ask, answer and share.
Program board, dependencies and risks
What this page is — The two whole-programme views of a PI session: the Program board (every team's plan side by side, with the cross-team dependencies between them) and the Risks tab (the ROAM board of team and programme risks).
Objectives, review, merge and commit
What this page is — The end of a PI session: the Objectives each team commits to (with business value), the Review tab with team demos and the confidence vote, the adjustment round, and Merge & commit, which turns every team's board into one plan written to the tasks.
PI Planning for integrators and assistants
What this page is — Every way software, rather than a person in the session, reaches PI Planning: the read-only Orbit Public API and the matching MCP tools, the questions the Orbit Assistant answers, the two e-mails and the webhook a session sends, and the live connection the page itself uses.