Simplifying Collaboration: The Power of Program Increment Planning

What is Program Increment Planning?

Program increment planning (PI planning) is a strategic event that brings multiple teams together to align on a shared direction. It’s a moment to agree on what to focus on, what to drop, and how to minimize dependencies. While PI planning is often used with SAFe, its principles can be applied to any framework.

The Benefits of PI Planning

• Output: Clearly defined goals, actions to deal with dependencies, and a set team roadmap
• Outcome: Clarity on direction and empowerment to say no to distractions

PI Planning vs. Sprint Planning

PI planning and sprint planning serve distinct purposes and operate on different timelines. PI planning is a high-level, strategic event that sets the stage for cross-team alignment and long-term focus. Sprint planning, on the other hand, is a more granular, tactical activity that ensures teams are well-coordinated and making progress towards overarching goals.

Modern PI Planning

Forget the bureaucratic name – let’s call it product goal alignment. The focus is on outputs and outcomes, not names. Here’s how it works:

• Why: Clear alignment for the next quarter(s)
• What: Define goals, name dependencies, define responsibilities, and roadmap
• When: 2-3 weeks before the end of the quarter
• Who: Product trio of each team (PM, UX, and dev), and company leadership
• How long: 4-6 hours
• How often: Once a quarter

Preparing for PI Planning

Proper preparation is key. Before the session, ensure:

1. Product vision: Clearly defined and communicated to all
2. Strategy: Defined and aligned with product vision
3. Status quo: Current product state and gaps to product vision
4. Prioritization: Clear prioritization of what to focus on and what to say no to

Running the PI Planning Session

Share the summary of vision, strategy, status quo, and prioritization with everyone before the session. Prepare a physical or virtual space, and follow a structured agenda.

# Example PI Planning Agenda

## Introduction (15 minutes)

* Review purpose and objectives
* Introduce facilitator and participants

## Review of Current State (30 minutes)

* Review current product state and gaps to product vision
* Discuss current challenges and pain points

## Goal Setting (60 minutes)

* Define goals and objectives for the next quarter
* Identify dependencies and potential roadblocks

## Prioritization (60 minutes)

* Prioritize goals and objectives based on business value and complexity
* Discuss trade-offs and compromises

## Roadmap and Responsibilities (60 minutes)

* Create a roadmap for the next quarter
* Assign responsibilities and tasks to team members

## Conclusion (15 minutes)

* Review outcomes and action items
* Set next steps and follow-up meetings

By following this structured approach to PI planning, teams can achieve clear alignment on goals and objectives, prioritize effectively, and create a roadmap for success.