## Overview A Program Increment (PI) is a fundamental timebox in the Scaled Agile Framework ([[SAFe]]). It is a set period during which multiple Agile teams work together toward a common goal and deliver continuous value. ### Purpose of a PI - Enable scalable Agile development - Align and coordinate multiple teams - Deliver business value continuously ### Basic Information About PI - Duration: 8 to 12 weeks (typically 10 weeks) - Structure: 4 to 5 iterations (sprints) - Main objective: Coordination and alignment across teams ### Components of a PI #### 1. PI Planning - Conducted during the first two days - All teams and stakeholders participate - Define goals, identify risks, and align dependencies #### 2. Iteration - Each sprint delivers and validates working functionality - Typically 2 weeks per iteration, repeated 4–5 times #### 3. System Demo - Teams present completed work - Stakeholders provide feedback #### 4. Inspect & Adapt - Review results and processes - Identify improvement actions for the next PI ### Visual Representation of a PI #### Structure of a 10-Week Program Increment | Phase | Duration | Description | | -------------------------- | ------------- | ----------------------------------------------- | | PI Planning | 2 days | Planning, alignment, and goal setting | | Iteration 1 | 2 weeks | Sprint execution | | Iteration 2 | 2 weeks | Sprint execution | | Iteration 3 | 2 weeks | Sprint execution | | Iteration 4 | 2 weeks | Sprint execution | | IP (Innovation & Planning) | About 1 week | Technical debt reduction, learning, improvement | | Inspect & Adapt | Half to 1 day | Review and define improvement actions |