Leading PI Planning (20%) Flashcards
What is the typical Day 1 standard agenda for PI Planning?
- Business Context
- Product/Solution Vision
- Communicate the vision
- Top 10 Features
- Architecture Vision
- Planning Context
- Team Breakouts
- Decompose Features into Stories
- Negotiate scope
- Review the draft PI plan
- Management review and problem-solving of plan
What is the recommended way to Communicate the Product Vision?
- Present how the Vision aligns to the Strategic Themes
- Illustrate how the Vision improves customers’ experiences using Personas
- Explain the need for NFR
What is the typical Day 2 standard agenda for PI Planning?
- Review plan adjustments from Day 1 –> Presented by Business Owners
- Team breakouts
- PI Objectives
- Business owners assign value to PI Objectives
- Final Plan Review
- Go over Program Risks
- Confidence Vote
- Rework plan, if needed
- PI Meeting retrospective
During PI Planning, what should be communicated about the Program Roadmap?
- Show how the PI Roadmap and this PI are aligned with the Vision
- Go over the PI Roadmap for the next 2 Program Increments (PI)
- Highlight Program epics and milestones
How many Features are targeted for PI Planning?
10
The practice is called the Top 10 Features but in reality the PI can do more or less than 10 Features
When reviewing the Top 10 Features during PI Planning, what should the PM strive to accomplish?
- No surprises, the team should already be aware of the Features because of successive refinement sessions
- Be able to explain how the Features were chosen for the Roadmap and this PI
What should Product Managers be socializing before PI Planning?
Features so that teams are aware and knowledgeable and thus better able to right-size a Feature
Explaining why a Feature was chosen for a PI supports what SAFe Core Value?
Transparency
What do Agile Teams do during the PI Planning Team Breakout time?
Work on planning how they will deliver Features in upcoming iterations
Who leads Agile Team in decomposing Features during PI Planning?
Product Owners
What do Product Managers do during Agile Team Breakout sessions during PI Planning?
Support the team in understanding Features by providing additional insight and guidance
What are PI Objectives?
A summary of the business and technical goals that each team intends to achieve during the PI
What are 5 benefits PI Objectives provide for a PI?
- Provide a common language for communicating with business and technology stakeholders
- Creates the near-term focus and vision
- Provide a means to assess the performance and business value achieved via the Program Predictability Measure
- Communicates and highlights each team’s contribution to the business value of the PI
- Exposes dependencies that require coordination
How is flow predictability measured for an ART?
SAFe Program Predictability Measure
What does the Program Predictability Measure (PPM) provide for an ART?
Measures the flow predictability of the teams and ART to plan and meet their PI Objectives.
How is PPM measured?
It’s the ratio of the PI Objectives Business Value subjective ranking by the business owners (1 to 10) to the “actual” Business Value ranking by the business owners after the PI is delivered
What does the acronym PPM stand for?
SAFe Program Predicitibility Measure (PPM)
Why is the PPM important?
Low or erratic predictability makes delivery commitments unrealistic and often highlights underlying problems in technology, planning, or organization performance that need addressing.
Reliable ARTs should operate in the 80 – 100 percent range; this allows the business and its stakeholders to plan effectively.
Who commits to the PI Objectives?
Agile Teams
Why are PI Objectives important for Agile Teams?
- Provides immediate feedback to the business owners that the Agile Teams understand the desired outcomes for the PI
- The business value provided by the business owners promotes decentralized decision-making should the Team need to adjust the planning work of the PI
- Committing to Objectives instead of a specific Feature or Story enhances agility.
How are Features different than PI Objectives?
PI Objectives focus on OUTCOMES
while
Features focus on OUTPUT