Leadership for PI Planning
Leadership is a behaviour, not a title
PI Planning is where leadership is most visible. The RTE facilitates the event; Business Owners are accountable for business outcomes, assign business value to team PI Objectives, and take part in the management review; executives set context and stay out of the room's problem-solving. Product Management and Product Owners lead through content and clarity:
- PM delivers the vision briefing and presents the top Features; POs are present and available in every team breakout.
- Leaders answer questions, negotiate scope, and resolve priority conflicts in real time - a question deferred until after the PI becomes a dependency and a delay.
- In the management review and problem-solving session, leaders address draft plans, unresolved dependencies, and scope or skill gaps.
Leaders also protect the PI after planning: no mid-PI priority churn, and impediments removed quickly.
Rule of thumb
Ask, don't tell. During breakouts a leader's job is to ask “what would you need to make this fit?” rather than issue a new commitment.
Traps
Believing PI Planning belongs to the RTE alone (PO/PM absence in breakouts is a top failure mode); pushing teams to “commit” instead of plan, with a confidence vote and honest risks; Business Owners assigning business value by gut feel without reading the objectives; executives leaving before the management review so decisions stall; ignoring a confidence vote below 3, which signals replanning.
Worked example
Two teams claim the same shared service. Instead of escalating, the PM and PO sit with both teams after breakout one, re-split the Feature, record one dependency, and the teams replan before the management review - fixed inside the event, not three weeks later.