Release Train: Program Increment (PI) Planning
Activity: Identify Product Backlog Items to deliver; allow teams to select PBIs (preferably grouped by high-level feature or capability) and plan the stories into the non-IP sprints; identify dependencies between teams; identify risks and impediments.
Attendees: Release Train Engineer (facilitator), Product Manager, all product owners, all scrum masters, and every member of every team in the release train.
Cadence: At the start of every program increment.
Approximate time: 2 days for a 5-sprint program increment with up to 12 teams.
Inputs
Refined program backlog. (See backlog refinement.)
Roadmap.
Outputs
PI objectives.
PI board.
Risks and impediments.
Next up:
Team activities (planning, stand-ups, demo, retrospective) for each team for each sprint.
Regular Scrums of Scrums for product management and scrum masters.
Then, PI Demo.