Align on goals, workflows, and releases for the next program increment
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.
Achieve a higher level of agile team alignment to the larger business context
Collaboratively create a clear roadmap and prioritize work items
Increase transparency and build trust between teams and stakeholders
Create a forum to come together and work towards common goals
Before the teams come together for the PI planning iteration, be sure to have a few things prepared:
Create a program board: from this template and create a dedicated room in Mural to hold all the resources from the upcoming sessions.
Create one team board per team: In the dedicated room, add one team board per team that'll participate in the PI planning process.
Edit the template: Delete any elements from the template that don’t suit your team’s needs and adapt the remaining elements to a format that best suits your team. This template should serve as a jumping-off point.
Lock content to the background: Before sharing your mural, right click to lock all content to the background to avoid elements being moved during the session.
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 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.
PI Planning Program Board: Create a visual summary of the goals, features, risks, dependencies, and timelines defined in the program increment plan.
PI Planning Team Board: 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.
After the session, clean up the board and record action items, following up from any unanswered questions that remain after the session.
Be sure to add any resources needed for the PI planning event to the Mural beforehand. This can be links, screenshots, PDFs, and more!
For recommendations on how to make the PI planning sessions run smoothly, check out Mural’s guide to PI planning for hybrid and remote teams.
Once the session is over, transfer learnings and action items quickly and efficiently into Jira.
When it comes to Agile software development, PI planning is an essential component. But what exactly is PI planning? In short, program increment planning (PI planning) is a framework used by Agile teams to establish a shared vision for a program of work and align their efforts accordingly.
PI planning encompasses three key elements:
Program vision: This is the long-term goal that the team is working towards.
Program backlog: This details the specific features and functionality that need to be delivered in order to achieve the program vision.
Iteration planning: This involves breaking down the program backlog into smaller pieces that can be completed within a set timeframe (usually 2-4 weeks).
By following this framework, teams can ensure that everyone is aware of the program's goals and objectives and knows what needs to be done in order to achieve them. Additionally, PI planning can help to prevent scope creep by keeping teams focused on delivering value within each iteration. Ultimately, PI planning is an essential part of any Agile software development initiative.
The program increment (PI) planning board is an important tool for organizations that use the Agile framework. PI planning is a process that helps teams to establish a common understanding of their goals and objectives, and to identify the necessary steps to achieve them.
PI planning boards provide a visual representation of this information, allowing team members to track progress and make adjustments as needed. In addition, the PI planning board can help to identify dependencies between different parts of the project, and ensure that all team members are working towards the same goal.
Typically, PI Planning sessions are conducted over a period of 2 to 5 days. However, it's important to note that the length can be adjusted based on the specific requirements and constraints of your team and organization. The goal is to allocate enough time for meaningful discussions, collaboration, and decision-making to effectively plan the program increment.
Program vision and objectives: The program vision and objectives provide the overarching direction and purpose for the program increment. They define what the team aims to achieve and serve as a guiding principle throughout the planning process.
Program backlog: The program backlog consists of the features, user stories, or work items that need to be addressed during the program increment. It includes the prioritized list of tasks or deliverables that the team will work on to achieve the program objectives.
Team and resource capacity: Understanding the team's capabilities and available resources is crucial for effective planning. This input includes information on the team members' skills, expertise, and availability, as well as any external dependencies or constraints that might impact the capacity to deliver the planned work.
The goal of a PI Planning session is to align teams, stakeholders, and leadership on a shared vision, known as the PI. During this session, teams come together to discuss and plan their work for the upcoming PI, with the ultimate goal of delivering valuable and high-quality products or services to customers. The session involves a series of structured activities, such as reviewing the current state of the business, identifying dependencies and risks, and collaboratively defining and prioritizing the objectives and features to be delivered in the PI.
The end result is a comprehensive and coordinated plan that drives the team towards achieving the common goal, fosters transparency and collaboration, and ensures everyone is on the same page. Ultimately, the goal of a PI Planning session is to enable teams to deliver value to customers efficiently and effectively, while continuously adapting and improving their processes.
PI (Program Increment) Planning is a crucial component of Agile project management. It's a collaborative and time-boxed event that brings together all members of an Agile team, including Product Owners, Scrum Masters, and development teams.
The main function of PI Planning is to align all team members on the same goals and priorities for the upcoming Program Increment. This is achieved through a series of discussions and activities, such as reviewing the overall vision and objectives, identifying and prioritizing features and user stories, estimating effort and dependencies, and creating a high-level plan for the next iteration. PI Planning helps teams to plan and coordinate their work more effectively, making sure that everyone is working towards the same objectives and delivering value to the customer. It also promotes transparency and collaboration, allowing team members to share ideas and make decisions together, ultimately leading to a successful and cohesive delivery of the project.
Mural is the only platform that offers both a shared workspace and training on the LUMA System™, a practical way to collaborate that anyone can learn and apply.