SAFe PI Planning and Events

Question 1

What is the primary purpose of PI Planning in SAFe?

Accepted Answer

To align all ART teams to a shared mission, identify dependencies, and commit to PI Objectives

Answer

To assign tasks to individual developers

Answer

To review the previous PI performance

Answer

To update the enterprise project portfolio

Question 2

How long does a typical PI Planning event last?

Accepted Answer

Two days

Answer

Half a day

Answer

One day

Answer

One week

Question 3

What inputs are required BEFORE PI Planning begins?

Accepted Answer

Product/Solution Vision, Architecture Vision, and top Features in the Program Backlog

Answer

Sprint backlogs and user stories only

Answer

Annual budget approvals and headcount plans

Answer

Completed System Demo and retrospective notes

Question 4

During PI Planning, what is the purpose of 'draft plan review'?

Accepted Answer

Teams present draft PI plans including risks and impediments to the ART for feedback

Answer

Executives review and approve team plans

Answer

The RTE finalizes the PI schedule

Answer

Product Owners assign stories to developers

Question 5

What is a 'Management Review and Problem Solving' session during PI Planning?

Accepted Answer

A working session where management adjusts scope, resources, or constraints in response to team concerns

Answer

A session where managers assign work to teams

Answer

A financial audit of the previous PI

Answer

An architecture review board meeting

Question 6

At the end of PI Planning, teams vote on confidence in the PI plan using a 'Fist of Five.' What does a vote of 3 mean?

Accepted Answer

I have some concerns but will support the plan

Answer

Complete confidence — I'll champion this plan

Answer

I don't support the plan at all

Answer

I need more information before committing