SAFe - How to lead a successful PI Planning

1. 05 - After the PI Planning event

1.1. RTE and stakeholders summarize individual team PI objectives

1.1.1. Real

1.2. Product Management updates roadmap and improves

1.3. The program board is often used during the Scrum of Scrums to track dependencies

1.4. the ART proceeds to execute the PI, tracking progress and adjusting as necessary to the changes that occur as new knowledge emerges

1.5. Next Lesson - Develop on Cadence ; Release on demand

2. 04 - Day 2 - Activities

2.1. Team Breakouts Outcomes

2.2. Program risks management

2.2.1. ROAMing risks

2.3. Confidence Vote

2.3.1. Low level Confidence

2.3.2. High level confidence

2.4. Retrospective

2.4.1. Questions to ask

3. 01 - Preparation

3.1. Description

3.2. What event !

3.3. Requirements

4. 02 - Inputs and Outcomes

4.1. The objectives

4.1.1. Final Objectives

4.2. the program Board

4.3. Inputs

5. 03 - Day 1 - Activities

5.1. Program Board draft 1

5.1.1. Estimate Story Points

5.1.2. Estimate velocity

5.2. Draft Plan Review looks like a SoS

5.3. Management review and problem solving

5.3.1. Questions to ask

5.3.2. To be continued next day