RTE PI Planning 1 — Questions and Answers
Question 1: What is the primary goal of PI Planning in SAFe?
- Align all Agile Release Train teams to a shared mission and vision (Correct answer)
- Review individual team backlogs for completeness
- Assign story points to all planned features
- Approve the portfolio budget for the next quarter
Correct answer: Align all Agile Release Train teams to a shared mission and vision
PI Planning aligns all ART teams to a shared mission, vision, and objectives for the next Program Increment.
Question 2: How often does PI Planning typically occur in SAFe?
- Every 2 weeks
- Every sprint
- Every 8–12 weeks (Correct answer)
- Once per year
Correct answer: Every 8–12 weeks
PI Planning occurs every 8–12 weeks, aligning with the length of a Program Increment.
Question 3: Who is responsible for presenting the Vision during PI Planning?
- Scrum Masters
- Business Owners and Product Management (Correct answer)
- Release Train Engineer
- System Architect
Correct answer: Business Owners and Product Management
Business Owners and Product Management present the Vision to the ART teams during PI Planning.
Question 4: What is a Team PI Objective?
- A backlog item assigned to one developer
- A summary of what a team plans to accomplish during the PI, tied to business value (Correct answer)
- A sprint goal for a single iteration
- A compliance requirement for the program
Correct answer: A summary of what a team plans to accomplish during the PI, tied to business value
Team PI Objectives summarize what each team intends to accomplish during the PI and are assigned business value by Business Owners.
Question 5: What artifact is produced at the end of PI Planning?
- A release plan and deployment checklist
- A Program Board showing features, dependencies, and milestones (Correct answer)
- A risk register for the portfolio
- An updated product roadmap for two years
Correct answer: A Program Board showing features, dependencies, and milestones
The Program Board is the key artifact produced during PI Planning, showing features, team commitments, dependencies, and milestones.
Question 6: What does the RTE do during PI Planning breakout sessions?
- Assigns user stories to developers
- Facilitates team breakouts and resolves cross-team impediments (Correct answer)
- Approves all team PI objectives
- Writes acceptance criteria for features
Correct answer: Facilitates team breakouts and resolves cross-team impediments
During breakout sessions the RTE facilitates collaboration, helps remove impediments, and ensures cross-team dependencies are identified and resolved.
RTE PI Planning 1
What is the primary goal of PI Planning in SAFe?