PI Planning Template
Bring your team toward one vision and decide what stories to develop with the PI Planning Template. Manage your team's backlog, increase productivity, and build the foundation for a successful PI Planning event.
About the PI Planning Template
Many product teams and agile facilitators use PI Planning to align and bring teams towards one shared vision. PI Planning is supposed to happen in person, but since the rise of hybrid work, many teams run it remotely. Miro’s PI Planning Template helps you get an excellent overview of your PI Planning event, with step-by-step frames that will guide you through the whole process.
Keep reading to know more about how to use the PI Planning Template.
What is PI planning?
PI planning or “program increment planning” is a method for strategizing toward a shared vision among teams. In a PI planning event, teams, stakeholders, and project owners are assembled to review a program backlog and determine what direction the business will take next. Typically, organizations carry out PI planning every 8 to 12 weeks.
Benefits of PI planning
PI planning can be useful in a number of ways, and teams in various industries apply the PI methods to boost efficiency and productivity.
Establish face-to-face communication
One advantage of PI planning is that it enables all the various stakeholders and teams on a project to meet face-to-face and talk about the overall mission and goals. This is the crucial first step towards aligning all the different parties towards the same mission and goals.
Boost productivity
PI planning fosters cross-team and cross-Agile Release Team (ART) collaboration and establishes a clear backlog and schedule for when tasks should be completed. With teams syncing and communicating in the right way and focused on their own goals, overall team productivity improves.
Align team goals
One of the main goals of the PI planning process is to set clear goals and ensure that all stakeholders and team members are working towards that goal. Making sure that everyone understands and shares the same goal is the foundation of a unified team effort.
When to use PI planning
PI planning is part of the Scaled Agile Framework (SAFe), which is designed to help developers overcome the challenge of coordinating across teams, processes, and programs. In the SAFe model, teams are assembled into Agile Release Trains (ARTs), each of which works on a specific part of a broader goal.
To engage in PI planning, the Agile Release trains are brought together every 8 to 12 weeks. A PI planning event is an opportunity to step back and ensure everyone is still working toward the same business goals and is satisfied with the overall vision.
Create your PI Planning board
You can easily organize a PI Planning event remotely or in-person with Miro. Our PI Planning Template is divided into four parts:
Agenda
Program Board
ROAM Board
Teams Board
Read below to see how to use each part of the PI Planning Template:
PI Planning Agenda
Have a dedicated space to share the PI Planning schedule, where every participant will know what to expect and when. This will include all the PI Planning stages. Add a Program Backlog so you and your team know what still needs to be worked on.
Program Board (SAFe)
Here is where you and your team add milestones and iterations and how they correlate. Color-code tasks and connect them with lines and arrows to indicate flows and interdependencies. On the Program Board, you will overview features, dependencies, and milestones.
ROAM Board
A ROAM Board is where you and your team can see the program’s risks. That’s the moment to identify obstacles to achieving goals and decide how to proceed. Use the voting feature to perform the confidence vote.
Teams Board
Each team will have precise future iterations, tasks, and objectives moving forward. What’s on this frame needs to be included in the roadmap.
General considerations when running a PI Planning session:
Bring everyone together
Make sure all stakeholders, teammates, and project owners are present for the first all-hands planning session. For remote PI planning, you might choose to use video conferencing tools, which are widely used now.
Clarify team goals
Now, the team comes together to articulate the vision for the product or solution. Answer these questions: How are you filling customer needs? How have market changes impacted your ability to do so?
Draft a plan
Bring all these components together in a project management document for management and teams to review.
Tip: you can easily add Jira cards to your PI planning board to organize Jira issues and mark dependencies.
How do you do PI Planning?
A PI Planning event has a duration of 2 days, and it can be done remotely or in person. To run a successful PI Planning session, make sure that at the end of it you and your team come out with two things: committed PI Objectives and a Program Board where you will see the next milestones and delivery dates.
What are the PI planning stages?
The PI Planning event is divided into two days. On the first day, present your business context, draft a plan and manage and review blockers or constraints. The second day is meant to review your plan, evaluate program risks, perform the confidence vote and plan the rework and next steps.
Get started with this template right now.
One Page Product Strategy
Works best for:
Product Management, Planning
The One Page Product Strategy template condenses complex product strategies into concise, actionable plans. By providing a structured framework for outlining goals, target markets, and key initiatives, this template enables product teams to align on strategic objectives efficiently. With sections for defining value propositions, competitive differentiators, and success metrics, it facilitates strategic decision-making and execution. This template serves as a roadmap for driving product development efforts and achieving business objectives effectively.
Check-In Icebreaker Template
Works best for:
Icebreakers, Meetings
Run a dynamic online session with the Check-in Icebreaker Template. Use this icebreaker before your meeting to boost energy levels, connect people, and warm up the room.
4 L's Retrospective Template
Works best for:
Retrospectives, Decision Making
So you just completed a sprint. Teams busted their humps and emotions ran high. Now take a clear-eyed look back and grade the sprint honestly—what worked, what didn’t, and what can be improved. This approach (4Ls stand for liked, learned, lacked, and longed for) is an invaluable way to remove the emotion and look at the process critically. That’s how you can build trust, improve morale, and increase engagement—as well as make adjustments to be more productive and successful in the future.
Event Storming
Works best for:
Agile
Event Storming is a collaborative workshop technique for exploring complex business problems and modeling solutions. It fosters communication, uncovers dependencies, and aligns stakeholders by visualizing the flow of events in a system. This template empowers teams to map out processes, identify bottlenecks, and iterate towards more efficient solutions, driving continuous improvement and innovation.
AI Product Canvas
Works best for:
Product Management, Planning
The AI Product Canvas template facilitates the development of AI-powered products with a comprehensive framework. By defining AI capabilities, data requirements, and ethical considerations, this template guides teams through the AI product development process. With sections for identifying use cases, defining algorithms, and assessing model performance, it ensures that AI solutions meet user needs and ethical standards. This template serves as a strategic guide for developing innovative AI products that deliver value and drive business success.
Service Blueprint by Hyperact
Works best for:
Research & Design
The Service Blueprint template is perfect for visualizing the orchestration of service components. It maps out frontstage and backstage elements, helping you analyze and enhance customer experiences. Use this template to align teams, identify pain points, and streamline processes, ensuring a seamless service delivery. It's ideal for creating a shared understanding of service dynamics among stakeholders and collaborators.