Project Management Process
PI: Program Increment
Embedded Files
PI Planning & Concept
PI Planning & Concept
Program Increment (PI):
A fixed timebox (usually 8–12 weeks) in SAFe during which an Agile Release Train (ART) delivers incremental value via multiple team sprints.
How it's formulated:
How it's formulated:
Input: Vision, roadmap, backlog, business priorities.
Planning: Teams plan together in PI Planning event to commit on objectives.
Execution: Teams build and integrate features across iterations/sprints within the PI.
Inspect & Adapt: At PI end, hold a review and problem-solving workshop to improve.
PI Phases:
PI Phases:
Preparation: Business context, vision, backlog readiness.
PI Planning: Two-day event to align teams, plan work, identify risks.
Execution: Series of sprints (usually 4-5) delivering features.
System Demo: Regular demos to show progress at ART level.
Inspect & Adapt: Final event with retrospective, metrics review, and improvement plans.
Similar to retrospective, but across all teams
Includes all team members, even business teams and POs
Lean Portfolio Management
Lean Portfolio Management
1. Strategy & Investment Funding
1. Strategy & Investment Funding
Align portfolio vision with enterprise strategy
Define value streams
Allocate budgets to value streams (not projects)
Use Lean Budgets and Guardrails
Fund long-lived teams instead of temporary projects
🔷 2. Lean Governance
🔷 2. Lean Governance
Enable decentralized, yet controlled execution
Track portfolio metrics (e.g. epic progress, budget burn)
Apply Agile forecasting and rolling-wave planning
Use participatory budgeting
Support audit/compliance without waterfall artifacts
🔷 3. Agile Portfolio Operations
🔷 3. Agile Portfolio Operations
Coordinate value delivery across value streams
Use Portfolio Kanban to manage Epics
Drive LPM syncs and collaboration across ARTs
Empower Epic Owners to lead epics through the lifecycle
Connect LACE (Lean-Agile Center of Excellence) for enablement
🔷 4. Portfolio Vision
🔷 4. Portfolio Vision
Define a compelling future state for the portfolio
Developed by LPM stakeholders
Communicated through portfolio canvas, roadmap, solution intent
🔷 5. Enterprise Architecture Alignment
🔷 5. Enterprise Architecture Alignment
Guide architectural evolution and technology strategy
Enterprise Architects collaborate with System/Solution Architects
Ensure solutions align with strategic intent and NFRs
🔷 6. Epic Lifecycle Management
🔷 6. Epic Lifecycle Management
Manage large initiatives (business or enabler epics)
Use Lean Business Cases
Go through funnel → review → analysis → approval → implementation
Track via Portfolio Kanban system
Dr. Ghoniem Lawaty
Tech Evangelist
Page updated
Google Sites
Report abuse