A PI planning session is a collaborative SAFe event for organizing work across an upcoming program increment. A program increment lasts 8–12 weeks and usually contains four iterations, or sprints. section 1.3
A practical planning flow connects business commitments to manageable development work:
- Review the product roadmap, including business commitments, expected regulatory changes, and company initiatives. section 1.3
- Break larger initiatives into epics, then decompose projects or releases into user stories and smaller tasks. section 1.3
- Plan the resulting work across short development cycles, keeping terminology consistent enough to support communication. section 1.3
ACH project planning
An ACH project can use PI planning to translate a roadmap commitment or regulatory change into epics, user stories, and work planned for the coming sprints. section 1.3
