RTE PI Planning

Question 1

What is the primary goal of PI Planning in SAFe?

Accepted Answer

Align all Agile Release Train teams to a shared mission and vision

Answer

Review individual team backlogs for completeness

Answer

Assign story points to all planned features

Answer

Approve the portfolio budget for the next quarter

Question 2

How often does PI Planning typically occur in SAFe?

Accepted Answer

Every 8–12 weeks

Answer

Every 2 weeks

Answer

Every sprint

Answer

Once per year

Question 3

Who is responsible for presenting the Vision during PI Planning?

Accepted Answer

Business Owners and Product Management

Answer

Scrum Masters

Answer

Release Train Engineer

Answer

System Architect

Question 4

What is a Team PI Objective?

Accepted Answer

A summary of what a team plans to accomplish during the PI, tied to business value

Answer

A backlog item assigned to one developer

Answer

A sprint goal for a single iteration

Answer

A compliance requirement for the program

Question 5

What artifact is produced at the end of PI Planning?

Accepted Answer

A Program Board showing features, dependencies, and milestones

Answer

A release plan and deployment checklist

Answer

A risk register for the portfolio

Answer

An updated product roadmap for two years

Question 6

What does the RTE do during PI Planning breakout sessions?

Accepted Answer

Facilitates team breakouts and resolves cross-team impediments

Answer

Assigns user stories to developers

Answer

Approves all team PI objectives

Answer

Writes acceptance criteria for features