Align your product development team strategically
Use this template to create a visual summary of the goals, features, risks, dependencies, and timelines defined in the program increment plan.
Program increment planning — or PI planning — is an iterative exercise part of the SAFe (Scaled Agile Framework) that allows all Agile Release Train (ART) collaborators to align on goals, workflows, and releases included in the next PI.
Before the teams come together for the PI planning iteration, be sure to have a few things prepared:
Define the objectives of the program increment by creating a high-level summary of the business and technical goals that an agile team or train intends to achieve in the upcoming session.
Be sure to list out objectives, not features. Draft objectives by thinking about the problems that are being solved for the user (better, faster, cheaper). Think of features as being the solutions to those problems.
The program board highlights the new feature delivery updates, feature dependencies between teams, and milestones.
Once teams have completed their planning in the team boards, the whole group comes together to conclude their dependencies and delivery dates in the program board.
Create a visual summary of the goals, features, risks, dependencies, and timelines defined in the program increment plan.
Estimate the capacity of each team to accomplish the tasks in each iteration. You'll need one per team who participate in the planning.
Identify program risks and impediments that could impact your ability to meet your objectives. These need to be discussed and addressed with honesty and transparency, then categorized into one of the following categories: resolved, owned, accepted, and mitigated.
Rate your confidence in being able to deliver on your PI plan by using the voting function in Mural. Each participant gets one vote to cast.
5. Export your PI planning board
After the session, clean up the board and record action items, following up from any unanswered questions that remain after the session.