{"id":208481,"date":"2024-12-09T09:10:51","date_gmt":"2024-12-09T09:10:51","guid":{"rendered":"https:\/\/monday.com\/blog\/?p=208481"},"modified":"2026-03-10T05:14:56","modified_gmt":"2026-03-10T10:14:56","slug":"pi-planning","status":"publish","type":"post","link":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/","title":{"rendered":"PI planning: The ultimate guide for 2026"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":213,"featured_media":210254,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"pages\/cornerstone-primary.php","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_title":"PI Planning: The Ultimate Guide","_yoast_wpseo_metadesc":"Master PI planning with monday dev. Learn steps, best practices, and AI tools to run smarter, more successful planning events.","monday_item_id":18008518846,"monday_board_id":0,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[13911],"tags":[],"class_list":["post-208481","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-rnd"],"acf":{"sections":[{"acf_fc_layout":"content_1","blocks":[{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">Program Increment (PI) Planning is a cadence-based event that aligns all Agile Release Train (ART) teams to the same mission and vision. It&#8217;s a crucial element of the Scaled Agile Framework (SAFe) that organizations need to master if they want to develop and manage successful products.<\/p>\n<p class=\"p1\">Increasingly, AI-powered tools \u2014 like those found in monday dev \u2014 support this alignment by forecasting capacity, optimizing work allocation, and flagging risks automatically \u2014 helping teams plan smarter, faster.<\/p>\n<p class=\"p1\">In this guide, you&#8217;ll learn why organizations use PI planning, who&#8217;s involved, what the agenda covers, and how to run successful PI planning events. We&#8217;ll also show you how to bring multiple teams together and streamline the PI planning process with monday dev.<\/p>\n<a class=\"cta-button blue-button\" aria-label=\"Try monday dev\" href=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_self\">Try monday dev<\/a>\n"},{"acf_fc_layout":"testimonials_carousel","testimonial_collection_select":14085,"tc_slide_to_show":"2"}]},{"main_heading":"Key takeaways","content_block":[{"acf_fc_layout":"text","content":"<ul class=\"ul1\">\n<li class=\"li1\">PI planning is a cadence-based, strategic event that aligns all ART teams to a shared mission and vision for the next program increment.<\/li>\n<li class=\"li1\">Successful PI planning requires collaboration, early risk management, and strong stakeholder alignment to ensure predictable delivery and business value.<\/li>\n<li class=\"li1\">The process involves structured steps \u2014 from presenting business context and product vision, to breakout planning and retrospective \u2014 helping teams commit to collective outcomes.<\/li>\n<li class=\"li1\">Leveraging software like monday dev, teams can visualize dependencies, automate reporting, and use AI for smarter, faster planning \u2014 even with distributed teams.<\/li>\n<li class=\"li1\">Best practices include regular scheduling, clear <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-principles\/\"><span class=\"s2\">Agile<\/span><\/a>\u00a0roles, active retrospectives, and adapting PI planning for both in-person and remote collaboration to maximize success.<\/li>\n<\/ul>\n"}]},{"main_heading":"What is PI planning?","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">Program increment (PI) planning is a key event in the <a href=\"https:\/\/monday.com\/blog\/rnd\/scaled-agile-framework\/\"><span class=\"s1\">Scaled Agile Framework (SAFe)<\/span><\/a>, where multiple teams within the same <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-release-train\/\">Agile Release Train<\/a> (meet to align on goals and plan work for the upcoming program increment.<\/p>\n<h3>How long does PI planning take?<\/h3>\n<p class=\"p1\">PI planning typically occurs every 8 to 12 weeks, but organizations can adjust the timing to their needs. For instance, some organizations prefer 8-week intervals for more agility, while others choose 12-week intervals to align with financial quarters. If <a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-planning\/\"><span class=\"s1\">sprints<\/span><\/a> are 2 weeks long, one PI consists of 4 to 6 sprints, providing a consistent rhythm for planning and alignment.<\/p>\n<p class=\"p1\">Whatever cadence organizations choose, PI planning has a regular, predictable schedule. It&#8217;s a fixed time-boxed event that usually lasts for two days. The consistent cadence ensures teams have regular opportunities to synchronize, plan, and adapt their work across the Agile Release Train.<\/p>\n<h3 class=\"p1\">PI planning vs. sprint planning<\/h3>\n<p class=\"p1\">PI planning and sprint planning are closely linked, yet address different needs at varying levels of scale and detail. Here\u2019s a comparison table highlighting the key differences:<\/p>\n\n<table id=\"tablepress-770\" class=\"tablepress tablepress-id-770 bold-left-column\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Feature<\/th><th class=\"column-2\">PI planning<\/th><th class=\"column-3\">Sprint planning<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Scope<\/td><td class=\"column-2\">Strategic objectives and roadmap \u2014 program level<\/td><td class=\"column-3\">Detailed user stories and tasks \u2014 team level<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Timeframe<\/td><td class=\"column-2\">8\u201312 weeks<\/td><td class=\"column-3\">1\u20132 weeks<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Participants<\/td><td class=\"column-2\">Multiple teams<\/td><td class=\"column-3\">Single team<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Duration<\/td><td class=\"column-2\">2+ days<\/td><td class=\"column-3\">2\u20134 hours<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Outputs<\/td><td class=\"column-2\">PI objectives, program board, risks, roadmap<\/td><td class=\"column-3\">Sprint goal, sprint backlog<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-770 from cache -->\n<p class=\"p1\">Sprint planning builds directly from PI objectives by translating broad, strategic goals into actionable tasks for the team\u2019s next sprint. Each sprint is designed to make steady progress toward the program\u2019s key outcomes, ensuring that day-to-day work remains aligned with organizational priorities and that teams deliver value consistently throughout the PI window.<\/p>\n<h3>Who participates in PI planning?<\/h3>\n<p class=\"p1\">Because of its collaborative nature, PI planning involves multiple perspectives. Here are the key roles and responsibilities:<\/p>\n<p><span style=\"font-weight: 400;\">\n<table id=\"tablepress-307\" class=\"tablepress tablepress-id-307\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Role<\/th><th class=\"column-2\">Responsibilities<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Release Train Engineer (RTE)<\/td><td class=\"column-2\">Facilitates the event, manages risks\/dependencies, aligns teams, tracks objectives<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Product Manager<\/td><td class=\"column-2\">Presents program vision, prioritizes workflows, updates roadmap post-planning<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Product Owner<\/td><td class=\"column-2\">Maintains backlog, defines user stories, ensures team priorities align with program goals<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Scrum Master<\/td><td class=\"column-2\">Coaches teams, removes impediments, enforces Agile principles, manages timebox<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Developers &amp; Testers<\/td><td class=\"column-2\">Participate in breakouts, refine user stories, identify dependencies, draft PI objectives<\/td>\n<\/tr>\n<tr class=\"row-7\">\n\t<td class=\"column-1\">Other stakeholders (business owners, architects, executives, customers)<\/td><td class=\"column-2\">Provide context, feedback, and approvals<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-307 from cache --><\/span><\/p>\n"}]},{"main_heading":"Why do PI planning?","content_block":[{"acf_fc_layout":"text","content":"<p data-start=\"1444\" data-end=\"1804\">The goal of PI planning is to align <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-release-planning\/\">releases<\/a>, foster collaboration, manage risks, improve predictability, and ensure teams work efficiently toward shared business goals. While it requires significant time and effort, the benefits almost always outweigh the costs in large-scale <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-planning\/\"><span class=\"s1\">Agile<\/span><\/a> development.<\/p>\n<p data-start=\"1444\" data-end=\"1804\">Here are the key reasons organizations invest in PI planning:<\/p>\n<ul>\n<li data-start=\"1812\" data-end=\"1987\"><strong data-start=\"1812\" data-end=\"1840\">Alignment and visibility: <\/strong>All teams within the ART connect to the business context and vision, ensuring clarity on priorities and upcoming work.<\/li>\n<li data-start=\"1812\" data-end=\"1987\"><strong data-start=\"1995\" data-end=\"2029\">Collaboration and coordination: <\/strong>The event brings teams together to discuss dependencies, foster cross-team collaboration, and make real-time decisions.<\/li>\n<li data-start=\"2163\" data-end=\"2295\"><strong data-start=\"2163\" data-end=\"2182\">Risk management: <\/strong>Potential issues are surfaced early, giving teams the chance to develop mitigation plans before execution.<\/li>\n<li data-start=\"2303\" data-end=\"2471\"><strong data-start=\"2303\" data-end=\"2334\">Planning and predictability: <\/strong>With AI-powered predictive analytics, teams achieve more accurate forecasts and build stakeholder confidence in their commitments.<\/li>\n<li data-start=\"2479\" data-end=\"2603\"><strong data-start=\"2479\" data-end=\"2503\">Resource utilization: <\/strong>Capacity and demand can be balanced more effectively, preventing teams from being overloaded.<\/li>\n<li data-start=\"2611\" data-end=\"2756\"><strong data-start=\"2611\" data-end=\"2637\">Motivation and clarity: <\/strong>By seeing the bigger picture, teams understand their role in the program and stay motivated around shared goals.<\/li>\n<li data-start=\"2764\" data-end=\"2897\"><strong data-start=\"2764\" data-end=\"2785\">Stronger networks: <\/strong>Whether in person or remote, the event strengthens trust and relationships across teams and stakeholders.<\/li>\n<\/ul>\n"}]},{"main_heading":"What are the steps involved in PI planning? ","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">PI planning follows a structured agenda that guides Agile teams through strategic alignment, planning, review, and commitment for the next program increment. Here are the 9 steps involved:<\/p>\n<ol class=\"ol1\">\n<li class=\"li1\"><strong>Business context presentation:<\/strong> Senior leadership shares the current business environment, market outlook, and high-level goals to set the strategic context for teams.<\/li>\n<li class=\"li1\"><strong>Product vision presentation:<\/strong> Product managers outline the program vision, key priorities, and the main features slated for development.<\/li>\n<li class=\"li1\"><strong>Planning context and expectations:<\/strong> The Release Train Engineer explains the PI planning process, clarifies objectives, and sets expectations for outcomes.<\/li>\n<li class=\"li1\"><strong>Team breakouts:<\/strong> Individual teams review capacity, break down features into user stories, and draft initial plans, identifying dependencies and risks.<\/li>\n<li class=\"li1\"><strong>Draft plan review:<\/strong> Teams present their first draft plans, including PI objectives, risks, and dependencies, for feedback from other teams.<\/li>\n<li class=\"li1\"><strong>Management review and problem-solving:<\/strong> Management facilitates the resolution of cross-team dependencies and roadblocks, ensuring alignment and feasibility.<\/li>\n<li class=\"li1\"><strong>Risk identification and resolution:<\/strong> Teams collectively assess and categorize risks as resolved, owned, accepted, or mitigated, then vote on confidence in meeting objectives.<\/li>\n<li class=\"li1\"><strong>Rework and confidence vote:<\/strong> Teams adjust plans based on feedback and risk assessment, reworking drafts for a higher confidence score in their deliverables.<\/li>\n<li class=\"li1\"><strong>Retrospective and next steps:<\/strong> The Release Train Engineer leads a closing retrospective to capture what worked, what could improve, and actionable lessons for future PI events.<\/li>\n<\/ol>\n<p class=\"p1\">This step-by-step structure keeps the PI planning process organized, ensures stakeholder alignment, and drives collective commitment to shared objectives for the increment.<\/p>\n"}]},{"main_heading":"What are some best practices for PI planning?","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">Some of the best practices for effective PI planning focus on preparation, stakeholder alignment, clear communication, risk management, and leveraging technology for remote teams.<\/p>\n<ul class=\"ul1\">\n<li class=\"li1\"><strong>Ensure organizational readiness:<\/strong> Schedule PI planning events regularly and communicate them well in advance so all stakeholders can participate; this sets expectations and supports full-team engagement.<\/li>\n<li class=\"li1\"><strong>Prepare program vision and content:<\/strong> Share the business mission, current <a href=\"https:\/\/monday.com\/blog\/rnd\/product-plan\/\"><span class=\"s2\">roadmap<\/span><\/a>, and product vision with all team members before the event, so everyone is aligned on priorities and the \u201cwhy\u201d behind key features.<\/li>\n<li class=\"li1\"><strong>Organize logistics for collaboration:<\/strong> Set up physical or virtual meeting spaces to support large group discussions and team breakouts, and make sure everyone has the right tools for clear participation \u2014 including video conferencing for remote\/hybrid teams.<\/li>\n<li class=\"li1\"><strong>Manage scope and participation:<\/strong> Clarify the scope of planning, identify essential team members, and confirm roles like Scrum master, Product owner, and Release Train Engineer. Encourage a shared understanding of responsibilities and priorities.<\/li>\n<li class=\"li1\"><strong>Promote open communication:<\/strong> Facilitate regular check-ins and feedback sessions to surface dependencies and risks early; foster honest, respectful dialogue to solve problems and improve plans.<\/li>\n<li class=\"li1\"><strong>Proactively identify and address risks:<\/strong> Early risk identification and categorization (resolved, owned, accepted, mitigated) improves transparency and confidence in the final plan. Document and track risks as the increment progresses.<\/li>\n<li class=\"li1\"><strong>Run engaging retrospectives:<\/strong> End each PI planning event with a retrospective, so teams can reflect on what worked well, what needs improvement, and actionable ideas for next time \u2014 helping drive continuous improvement.<\/li>\n<li class=\"li1\"><strong>Leverage digital tools:<\/strong> Use AI-powered planning software like <a href=\"https:\/\/monday.com\/w\/dev\"><span class=\"s2\">monday dev<\/span><\/a> to visualize dependencies, track objectives, and facilitate collaboration, especially for distributed teams.<\/li>\n<\/ul>\n<p class=\"p1\">By following these best practices, organizations can increase engagement, alignment, and the likelihood of achieving program goals throughout each increment.<\/p>\n"}]},{"main_heading":"How to prepare for a PI planning event","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">Here are ten essential steps to ensure your organization is well-prepared for a successful PI planning event.<\/p>\n<ol class=\"ol1\">\n<li class=\"li1\"><strong>Understand and communicate the purpose:<\/strong> Ensure all participants, especially executives and management, clearly understand the goals of PI planning. Communicate that the aim is to create an emergent roadmap and identify potential obstacles.<\/li>\n<li class=\"li1\"><strong>Schedule well in advance:<\/strong> Plan the event for the next quarter at the end of the current quarter. Ensure the availability of all key stakeholders and leaders.<\/li>\n<li class=\"li1\"><strong>Prepare the program vision and context:<\/strong> Determine the program vision and purpose in advance. Ensure program leaders and business stakeholders know how to convey this information.<\/li>\n<li class=\"li1\"><strong>Arrange appropriate facilities:<\/strong> Book a large room that can accommodate about double the number of expected attendees. Ensure proper setup for remote participants, such as video conferencing equipment.<\/li>\n<li class=\"li1\"><strong>Refine the backlog:<\/strong> Review and refine the <a href=\"https:\/\/monday.com\/blog\/rnd\/product-backlog\/\">product backlog<\/a>. Ensure <a href=\"https:\/\/monday.com\/blog\/rnd\/user-story-template\/\">user stories<\/a> and features are well-defined and prioritized.<\/li>\n<li class=\"li1\"><strong>Align stakeholders:<\/strong> Engage with business owners and stakeholders to understand the priorities and expectations.<\/li>\n<li class=\"li1\"><strong>Plan logistics:<\/strong> Arrange the necessary tools, resources, and materials. Set up digital collaboration tools if needed.<\/li>\n<li class=\"li1\"><strong>Prepare an agenda:<\/strong> Create a detailed agenda for the two-day event. Include time for business context, vision presentations, team breakouts, plan reviews, etc.<\/li>\n<li class=\"li1\"><strong>Pre-PI planning:<\/strong> Each team should conduct its own pre-PI planning session to prepare initial plans and identify potential risks and dependencies.<\/li>\n<li class=\"li1\"><strong>Set up a program board:<\/strong> Prepare a physical or digital program board to visualize features, dependencies, and milestones.<\/li>\n<\/ol>\n<p class=\"p1\">Modern platforms like monday dev now use AI to transform backlog items, requirements, and meeting notes into actionable user stories and tasks \u2014 reducing manual prep and improving quality.<\/p>\n<p><iframe loading=\"lazy\" title=\"How to summarize developer docs with AI in monday dev\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube.com\/embed\/hoNBi4G_fCA?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/p>\n<a class=\"cta-button blue-button\" aria-label=\"Try monday dev\" href=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_self\">Try monday dev<\/a>\n"}]},{"main_heading":"How to run a PI planning event\u00a0","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">Here\u2019s how a typical PI planning agenda plays out over 2 days:<\/p>\n<h3 class=\"p2\">Day 1 agenda<\/h3>\n<p class=\"p1\">The first-day agenda includes an overview of the business context, <a href=\"https:\/\/monday.com\/blog\/rnd\/product-vision\/\">product vision<\/a>, and architecture, followed by detailed team planning and initial reviews of those plans.<\/p>\n\n<table id=\"tablepress-843\" class=\"tablepress tablepress-id-843\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Session<\/th><th class=\"column-2\">Purpose<\/th><th class=\"column-3\">Details<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Business context<\/td><td class=\"column-2\">Senior leader presents the state of the business, portfolio vision, and customer needs<\/td><td class=\"column-3\">\u2013<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Product\/solution vision<\/td><td class=\"column-2\">Product manager shares the current product vision and top ~10 features<\/td><td class=\"column-3\">\u2013<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Architecture vision &amp; practices<\/td><td class=\"column-2\">System architect presents the architecture vision; dev managers outline best Agile practices<\/td><td class=\"column-3\">\u2013<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Planning context<\/td><td class=\"column-2\">RTE explains the planning process and expected outcomes<\/td><td class=\"column-3\">\u2013<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Team breakouts #1<\/td><td class=\"column-2\">Teams estimate capacity, identify backlog items, and refine features into stories<\/td><td class=\"column-3\">AI-powered scenario simulation lets teams test allocations and schedules instantly<\/td>\n<\/tr>\n<tr class=\"row-7\">\n\t<td class=\"column-1\">Draft plan review<\/td><td class=\"column-2\">Teams present draft PI objectives, risks, and dependencies<\/td><td class=\"column-3\">Stakeholders (Business Owners, PMs, etc.) provide feedback<\/td>\n<\/tr>\n<tr class=\"row-8\">\n\t<td class=\"column-1\">Management review\/problem-solving<\/td><td class=\"column-2\">Leadership and RTE resolve dependencies, negotiate scope, and ensure feasibility<\/td><td class=\"column-3\">\u2013<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-843 from cache -->\n<h3 class=\"p2\">Day 2 agenda<\/h3>\n<p class=\"p1\">The second-day agenda lets teams finalize their plans, address risks, and align on objectives for the upcoming PI. It concludes with a confidence vote to ensure everyone is committed to the plan and a retrospective to improve future PI planning events.<\/p>\n\n<table id=\"tablepress-844\" class=\"tablepress tablepress-id-844\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Session<\/th><th class=\"column-2\">Purpose<\/th><th class=\"column-3\">Details<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Planning adjustments<\/td><td class=\"column-2\">Management presents results from Day 1 and any scope changes<\/td><td class=\"column-3\">\u2013<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Team breakouts #2<\/td><td class=\"column-2\">Teams refine plans, finalize objectives, and adjust based on feedback<\/td><td class=\"column-3\">Business owners assign business values and rank objectives<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Final plan review<\/td><td class=\"column-2\">Teams present finalized PI objectives, risks, impediments, and dependencies<\/td><td class=\"column-3\">Business owners must approve plans, even if adjusted<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">ART risks<\/td><td class=\"column-2\">Teams categorize risks from final plan review<\/td><td class=\"column-3\"><strong>Resolved:<\/strong> no longer a risk<br \/>\n<strong>Owned:<\/strong> assigned to a person\/team<br \/>\n<strong>Accepted:<\/strong> acknowledged, unavoidable<br \/>\n<strong>Mitigated:<\/strong> strategies in place to reduce impact<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Confidence vote<\/td><td class=\"column-2\">Teams vote using \u201cfist of five\u201d<\/td><td class=\"column-3\"><strong>3+ avg:<\/strong> plan accepted<br \/>\n<strong>Below 3:<\/strong> rework required<br \/>\n<strong>2 or lower:<\/strong> concerns added to risk list or require re-planning<\/td>\n<\/tr>\n<tr class=\"row-7\">\n\t<td class=\"column-1\">Plan rework (optional)<\/td><td class=\"column-2\">Teams adjust plans if confidence is too low<\/td><td class=\"column-3\">\u2013<\/td>\n<\/tr>\n<tr class=\"row-8\">\n\t<td class=\"column-1\">Retrospective &amp; next steps<\/td><td class=\"column-2\">RTE facilitates lessons learned<\/td><td class=\"column-3\">Captures improvements for future PI planning events<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-844 from cache -->\n"}]},{"main_heading":"monday dev Testimonials","content_block":[{"acf_fc_layout":"testimonials_carousel","testimonial_collection_select":14085,"tc_slide_to_show":"2"}]},{"main_heading":"What happens after a PI planning event?\u00a0","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">By following these post-PI planning activities, organizations can ensure that plans are effectively implemented and continuously improved throughout the program increment.<\/p>\n<ul class=\"ul1\">\n<li class=\"li1\"><strong>Next steps:<\/strong> To move objectives forward, teams coordinate calendars to arrange daily standups and iteration meetings.<\/li>\n<li class=\"li1\"><strong>Documentation:<\/strong> Teams transcribe objectives, user stories, and the program board into tools like monday dev and update roadmaps based on program objectives.<\/li>\n<li class=\"li1\"><strong>Execution:<\/strong> ARTs begin implementing the plans outlined during PI planning and delivering value according to the commitments.<\/li>\n<li class=\"li1\"><strong>Post-PI planning events:<\/strong> Further planning sessions involving stakeholders from all Agile Release Trains (ARTs) within the Solution Train take place to ensure synchronization and alignment. Teams present plans, explain objectives, and share milestones and timelines for each iteration and ART.<\/li>\n<li class=\"li1\"><strong>Continuous improvement:<\/strong> Teams hold regular Inspect and Adapt (I&amp;A) sessions throughout the increment, reflecting on progress, identifying areas for improvement, and adapting plans as needed to optimize performance.<\/li>\n<li class=\"li1\"><strong>Customer feedback:<\/strong> Product owners actively seek and incorporate feedback from customers and end-users so future plans align with customer expectations.<\/li>\n<\/ul>\n"}]},{"main_heading":"Common PI planning pitfalls to avoid","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">Here are ten common pitfalls to avoid in your PI planning.<\/p>\n<ol class=\"ol1\">\n<li class=\"li1\"><strong>Insufficient preparation:<\/strong> Not providing enough context or vision before the event and failing to have a clear backlog or prioritized features ready.<\/li>\n<li class=\"li1\"><strong>Poor time management:<\/strong> Allowing discussions to run over and disrupt the agenda and not allocating enough time for team breakouts or plan reviews.<\/li>\n<li class=\"li1\"><strong>Lack of stakeholder engagement:<\/strong> Not involving key business stakeholders throughout the process and failing to get proper buy-in from leadership.<\/li>\n<li class=\"li1\"><strong>Ignoring dependencies:<\/strong> Failing to identify and manage cross-team dependencies and not visualizing dependencies on the program board.<\/li>\n<li class=\"li1\"><strong>Overemphasis on estimation:<\/strong> Spending too much time on granular details at the expense of other activities and losing sight of the big picture.<\/li>\n<li class=\"li1\"><strong>Neglecting team dynamics:<\/strong> Not promoting a positive and inclusive environment for collaboration. Failing to address conflicts or issues promptly.<\/li>\n<li class=\"li1\"><strong>Skipping the confidence vote:<\/strong> Not conducting or taking the team confidence vote on the plan seriously.<\/li>\n<li class=\"li1\"><strong>Forgetting to review past PIs:<\/strong> Not looking back at previous PI performance to inform current planning.<\/li>\n<li class=\"li1\"><strong>Neglecting retrospectives:<\/strong> Skipping or rushing through the planning retrospective and not implementing improvements based on feedback from previous sessions.<\/li>\n<li class=\"li1\"><strong>Challenges with virtual planning:<\/strong> Failing to adapt the planning process effectively for distributed teams and using inadequate remote collaboration tools.<\/li>\n<\/ol>\n"}]},{"main_heading":"Using monday dev for PI planning","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">Built on <a href=\"https:\/\/monday.com\/\" target=\"_blank\" rel=\"noopener\"><span class=\"s1\">monday.com<\/span><\/a> Work OS and packed with versatile features, <a href=\"https:\/\/monday.com\/dev\" target=\"_blank\" rel=\"noopener\"><span class=\"s1\">monday dev<\/span><\/a> enables teams and stakeholders to connect and collaborate at every step of the PI planning process. Its built-in AI actions help automate reporting, track team progress, and generate dashboards with predictive analytics, making it easier to monitor PI health and proactively manage objectives.<\/p>\n<h3 data-start=\"296\" data-end=\"361\">AI-powered PI planning<\/h3>\n<p data-start=\"296\" data-end=\"361\">Traditional PI planning relies heavily on manual tracking, spreadsheets, and static boards. monday dev brings AI into the process \u2014 automatically surfacing dependencies, forecasting team capacity, and turning backlogs into actionable plans. This makes PI planning faster, more accurate, and far more scalable for distributed teams.<\/p>\n<h3 class=\"p2\">Plan with customizable boards<\/h3>\n<p class=\"p2\"><span style=\"font-size: 16px;\">You can adapt customizable boards in monday dev to support every aspect of PI planning. For instance, a <\/span>program board<span style=\"font-size: 16px;\"> gives a high-level view of features, dependencies, and milestones across teams, while <\/span>team boards<span style=\"font-size: 16px;\"> let individual groups track their PI objectives and break them down into actionable items.<\/span><\/p>\n"},{"acf_fc_layout":"image","image_type":"normal","image":208471,"image_link":""},{"acf_fc_layout":"text","content":"<h3 class=\"p1\">Collaborate in real time<\/h3>\n<p data-start=\"81\" data-end=\"320\">Collaboration is seamless, with real-time updates that allow teams to work on plans simultaneously and instantly see changes, plus built-in comments and discussions to address dependencies, risks, and adjustments as they come up.<\/p>\n"},{"acf_fc_layout":"image","image_type":"normal","image":208443,"image_link":""},{"acf_fc_layout":"text","content":"<h3 class=\"p1\">Visualize work with multiple views<\/h3>\n<p>Visualization features make PI planning easier, whether through Gantt charts that map out timelines, features, and dependencies across the program increment, or Kanban boards that help teams manage their <a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-backlog\/\"><span class=\"s2\">backlog<\/span><\/a> and organize work for the upcoming PI.<\/p>\n"},{"acf_fc_layout":"image","image_type":"normal","image":208450,"image_link":""},{"acf_fc_layout":"text","content":"<h3 class=\"p1\">Connect tools and automate workflows<\/h3>\n<p data-start=\"50\" data-end=\"258\">Integration features let teams connect monday dev with existing <a href=\"https:\/\/monday.com\/blog\/rnd\/software-development-tools\/\">development tools<\/a> to pull in relevant planning data, while automations can notify team members of updates or changes to keep everyone aligned.<\/p>\n"},{"acf_fc_layout":"image","image_type":"normal","image":208457,"image_link":""},{"acf_fc_layout":"text","content":"<h3 class=\"p1\">Track progress with AI-driven reporting<\/h3>\n<p class=\"p2\">Use the reporting features to monitor the advancement of PI objectives throughout the increment. Create dashboards to visualize team capacity, risks, and other key metrics for PI planning. Use built-in AI actions to automate reporting and predictive analytics, giving teams and stakeholders live, actionable insights into planning health.<\/p>\n<p><iframe loading=\"lazy\" title=\"monday dev: Enterprise - Part 5 - &#039;Epics and user stories&#039; | monday.com webinars\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube.com\/embed\/12aLQJs8eDI?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/p>\n<a class=\"cta-button blue-button\" aria-label=\"Try monday dev\" href=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_self\">Try monday dev<\/a>\n"}]},{"main_heading":"Streamline your PI planning","content_block":[{"acf_fc_layout":"text","content":"<p class=\"p1\">Successful PI planning relies on the active participation and alignment of all team members and stakeholders. With monday dev, you have a flexible platform to provide the technical infrastructure, but the event&#8217;s success ultimately depends on effective facilitation and team engagement.<\/p>\n<p class=\"p1\">Try <a href=\"https:\/\/monday.com\/dev\" target=\"_blank\" rel=\"noopener\"><span class=\"s1\">monday dev<\/span><\/a> to see how you can streamline your PI planning process and get everyone on the same page.<\/p>\n<a class=\"cta-button blue-button\" aria-label=\"Try monday dev\" href=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_self\">Try monday dev<\/a>\n<div class=\"accordion faq\" id=\"faq-pi-planning\">\n  <h2 class=\"accordion__heading section-title text-left\">FAQs <\/h2>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-pi-planning\" href=\"#q-pi-planning-1\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What is PI planning in SAFe?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-pi-planning-1\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-pi-planning\">\n      <p>PI planning in SAFe is a structured, two-day event that occurs every 8-12 weeks, where multiple Agile teams, stakeholders, and leaders align on shared objectives for the upcoming program increment. It drives team collaboration, dependency mapping, and a unified delivery roadmap, ensuring alignment with the organization's vision and strategy over the next 8-12 weeks.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-pi-planning\" href=\"#q-pi-planning-2\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What is PI planning in Scrum?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-pi-planning-2\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-pi-planning\">\n      <p>In Scrum, PI planning is adapted for coordinating across several Scrum teams. These teams meet at regular intervals to prioritize features, align backlogs, and sync on dependencies \u2014 especially useful if multiple teams need to coordinate releases or collaborate on shared goals outside the single-team sprint focus. This adapted version of PI planning allows Scrum teams to maintain their sprint-based approach while benefiting from the alignment and coordination that PI planning provides.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-pi-planning\" href=\"#q-pi-planning-3\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What's the difference between PI planning and sprint planning?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-pi-planning-3\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-pi-planning\">\n      <p>PI planning is a strategic event that occurs every 8-12 weeks and aligns multiple teams on goals and plans for an entire program increment. In contrast, sprint planning is a tactical event that happens at the start of each 1-2 week sprint, focusing on a single team's detailed work plan for that sprint. While PI planning sets the broader vision and objectives for the PI, sprint planning breaks down those objectives into specific tasks and user stories for immediate execution.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-pi-planning\" href=\"#q-pi-planning-4\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What's the difference between PI planning and Big Room planning?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-pi-planning-4\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-pi-planning\">\n      <p>PI Planning and Big Room Planning are essentially the same event, with \"Big Room Planning\" being an alternative name for PI Planning. Both refer to a large-scale planning event involving multiple teams that typically occurs every 8-12 weeks. The terms are often used interchangeably, with \"Big Room Planning\" emphasizing the physical aspect of having many people in one large room, while \"PI Planning\" focuses on its role in the Scaled Agile Framework (SAFe).<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-pi-planning\" href=\"#q-pi-planning-5\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What are the key outputs of PI planning?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-pi-planning-5\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-pi-planning\">\n      <p>The key outputs of PI planning are committed PI objectives, a program board with feature delivery dates and dependencies, and a prioritized backlog for upcoming iterations. Teams also identify risks, assign business values to objectives, and agree on milestones for the increment.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-pi-planning\" href=\"#q-pi-planning-6\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What tools are best for remote PI planning?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-pi-planning-6\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-pi-planning\">\n      <p>For remote PI planning, tools like monday dev support real-time collaboration, objective tracking, and visual management of dependencies. Other effective platforms include Miro, Mural, Piplanning.io, and Kendis, which provide digital workspaces, planning boards, and seamless communication for distributed teams.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-pi-planning\" href=\"#q-pi-planning-7\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">How do you measure the success of a PI planning event?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-pi-planning-7\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-pi-planning\">\n      <p>Success in PI planning is measured by team alignment on objectives, backlog completion rates, delivery against milestones, and business value achieved. Metrics include velocity, user story completion, and customer satisfaction. Post-event retrospectives help assess gaps and drive ongoing improvement for future PIs.<\/p>\n    <\/div>\n  <\/div>\n  <script type='application\/ld+json'>{\n    \"@context\": \"https:\\\/\\\/schema.org\",\n    \"@type\": \"FAQPage\",\n    \"mainEntity\": [\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What is PI planning in SAFe?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>PI planning in SAFe is a structured, two-day event that occurs every 8-12 weeks, where multiple Agile teams, stakeholders, and leaders align on shared objectives for the upcoming program increment. It drives team collaboration, dependency mapping, and a unified delivery roadmap, ensuring alignment with the organization's vision and strategy over the next 8-12 weeks.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What is PI planning in Scrum?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>In Scrum, PI planning is adapted for coordinating across several Scrum teams. These teams meet at regular intervals to prioritize features, align backlogs, and sync on dependencies \\u2014 especially useful if multiple teams need to coordinate releases or collaborate on shared goals outside the single-team sprint focus. This adapted version of PI planning allows Scrum teams to maintain their sprint-based approach while benefiting from the alignment and coordination that PI planning provides.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What's the difference between PI planning and sprint planning?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>PI planning is a strategic event that occurs every 8-12 weeks and aligns multiple teams on goals and plans for an entire program increment. In contrast, sprint planning is a tactical event that happens at the start of each 1-2 week sprint, focusing on a single team's detailed work plan for that sprint. While PI planning sets the broader vision and objectives for the PI, sprint planning breaks down those objectives into specific tasks and user stories for immediate execution.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What's the difference between PI planning and Big Room planning?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>PI Planning and Big Room Planning are essentially the same event, with \\\"Big Room Planning\\\" being an alternative name for PI Planning. Both refer to a large-scale planning event involving multiple teams that typically occurs every 8-12 weeks. The terms are often used interchangeably, with \\\"Big Room Planning\\\" emphasizing the physical aspect of having many people in one large room, while \\\"PI Planning\\\" focuses on its role in the Scaled Agile Framework (SAFe).<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What are the key outputs of PI planning?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The key outputs of PI planning are committed PI objectives, a program board with feature delivery dates and dependencies, and a prioritized backlog for upcoming iterations. Teams also identify risks, assign business values to objectives, and agree on milestones for the increment.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What tools are best for remote PI planning?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>For remote PI planning, tools like monday dev support real-time collaboration, objective tracking, and visual management of dependencies. Other effective platforms include Miro, Mural, Piplanning.io, and Kendis, which provide digital workspaces, planning boards, and seamless communication for distributed teams.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"How do you measure the success of a PI planning event?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Success in PI planning is measured by team alignment on objectives, backlog completion rates, delivery against milestones, and business value achieved. Metrics include velocity, user story completion, and customer satisfaction. Post-event retrospectives help assess gaps and drive ongoing improvement for future PIs.<\\\/p>\\n\"\n            }\n        }\n    ]\n}<\/script><\/div>\n\n"}]}]}],"lobby_image":false,"post_thumbnail_title":"","hide_post_info":false,"hide_bottom_cta":false,"hide_from_blog":false,"landing_page_layout":false,"hide_time_to_read":false,"sidebar_color_banner":"","custom_tags":false,"disclaimer":"","cornerstone_hero_cta_override":{"label":"","url":""},"cluster":"","display_dates":"updated","featured_image_link":"","faqs":[{"faq_title":"FAQs ","faq_shortcode":"pi-planning","faq":[{"question":"What is PI planning in SAFe?","answer":"<p>PI planning in SAFe is a structured, two-day event that occurs every 8-12 weeks, where multiple Agile teams, stakeholders, and leaders align on shared objectives for the upcoming program increment. It drives team collaboration, dependency mapping, and a unified delivery roadmap, ensuring alignment with the organization's vision and strategy over the next 8-12 weeks.<\/p>\n"},{"question":"What is PI planning in Scrum?","answer":"<p>In Scrum, PI planning is adapted for coordinating across several Scrum teams. These teams meet at regular intervals to prioritize features, align backlogs, and sync on dependencies \u2014 especially useful if multiple teams need to coordinate releases or collaborate on shared goals outside the single-team sprint focus. This adapted version of PI planning allows Scrum teams to maintain their sprint-based approach while benefiting from the alignment and coordination that PI planning provides.<\/p>\n"},{"question":"What's the difference between PI planning and sprint planning?","answer":"<p>PI planning is a strategic event that occurs every 8-12 weeks and aligns multiple teams on goals and plans for an entire program increment. In contrast, sprint planning is a tactical event that happens at the start of each 1-2 week sprint, focusing on a single team's detailed work plan for that sprint. While PI planning sets the broader vision and objectives for the PI, sprint planning breaks down those objectives into specific tasks and user stories for immediate execution.<\/p>\n"},{"question":"What's the difference between PI planning and Big Room planning?","answer":"<p>PI Planning and Big Room Planning are essentially the same event, with \"Big Room Planning\" being an alternative name for PI Planning. Both refer to a large-scale planning event involving multiple teams that typically occurs every 8-12 weeks. The terms are often used interchangeably, with \"Big Room Planning\" emphasizing the physical aspect of having many people in one large room, while \"PI Planning\" focuses on its role in the Scaled Agile Framework (SAFe).<\/p>\n"},{"question":"What are the key outputs of PI planning?","answer":"<p>The key outputs of PI planning are committed PI objectives, a program board with feature delivery dates and dependencies, and a prioritized backlog for upcoming iterations. Teams also identify risks, assign business values to objectives, and agree on milestones for the increment.<\/p>\n"},{"question":"What tools are best for remote PI planning?","answer":"<p>For remote PI planning, tools like monday dev support real-time collaboration, objective tracking, and visual management of dependencies. Other effective platforms include Miro, Mural, Piplanning.io, and Kendis, which provide digital workspaces, planning boards, and seamless communication for distributed teams.<\/p>\n"},{"question":"How do you measure the success of a PI planning event?","answer":"<p>Success in PI planning is measured by team alignment on objectives, backlog completion rates, delivery against milestones, and business value achieved. Metrics include velocity, user story completion, and customer satisfaction. Post-event retrospectives help assess gaps and drive ongoing improvement for future PIs.<\/p>\n"}]}],"activate_cta_banner":false,"banner_url":"","main_text_banner":"","sub_title_banner":"","sub_title_banner_second":"","banner_button_text":"","below_banner_line":"","use_customized_cta":false,"custom_schema_code":"","parse_from_google_doc":false,"show_contact_sales_button":"default","post_date":"20250909","custom_header_banner":false,"show_sidebar_sticky_banner":false,"override_contact_sales_label":"","override_contact_sales_url":"","menu_cta_override":{"label":"","url":""}},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.6 (Yoast SEO v26.6) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>PI Planning: The Ultimate Guide<\/title>\n<meta name=\"description\" content=\"Master PI planning with monday dev. Learn steps, best practices, and AI tools to run smarter, more successful planning events.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PI planning: The ultimate guide for 2026\" \/>\n<meta property=\"og:description\" content=\"Master PI planning with monday dev. Learn steps, best practices, and AI tools to run smarter, more successful planning events.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/\" \/>\n<meta property=\"og:site_name\" content=\"monday.com Blog\" \/>\n<meta property=\"article:published_time\" content=\"2024-12-09T09:10:51+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-10T10:14:56+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png\" \/>\n\t<meta property=\"og:image:width\" content=\"4800\" \/>\n\t<meta property=\"og:image:height\" content=\"2400\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"David Hartshorne\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"David Hartshorne\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"1 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/\"},\"author\":{\"name\":\"David Hartshorne\",\"@id\":\"https:\/\/monday.com\/blog\/#\/schema\/person\/4cf4e679301900c5395f6f33cbc6d7c9\"},\"headline\":\"PI planning: The ultimate guide for 2026\",\"datePublished\":\"2024-12-09T09:10:51+00:00\",\"dateModified\":\"2026-03-10T10:14:56+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/\"},\"wordCount\":6,\"publisher\":{\"@id\":\"https:\/\/monday.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png\",\"articleSection\":[\"Product development life cycle\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/\",\"url\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/\",\"name\":\"PI Planning: The Ultimate Guide\",\"isPartOf\":{\"@id\":\"https:\/\/monday.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png\",\"datePublished\":\"2024-12-09T09:10:51+00:00\",\"dateModified\":\"2026-03-10T10:14:56+00:00\",\"description\":\"Master PI planning with monday dev. Learn steps, best practices, and AI tools to run smarter, more successful planning events.\",\"breadcrumb\":{\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#primaryimage\",\"url\":\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png\",\"contentUrl\":\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png\",\"width\":4800,\"height\":2400,\"caption\":\"PI planning The ultimate guide for 2026\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/monday.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Product development life cycle\",\"item\":\"https:\/\/monday.com\/blog\/rnd\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"PI planning: The ultimate guide for 2026\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/monday.com\/blog\/#website\",\"url\":\"https:\/\/monday.com\/blog\/\",\"name\":\"monday.com Blog\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/monday.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/monday.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/monday.com\/blog\/#organization\",\"name\":\"monday.com Blog\",\"url\":\"https:\/\/monday.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/monday.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/res.cloudinary.com\/monday-blogs\/fl_lossy,f_auto,q_auto\/wp-blog\/2020\/12\/monday.com-logo-1.png\",\"contentUrl\":\"https:\/\/res.cloudinary.com\/monday-blogs\/fl_lossy,f_auto,q_auto\/wp-blog\/2020\/12\/monday.com-logo-1.png\",\"width\":200,\"height\":200,\"caption\":\"monday.com Blog\"},\"image\":{\"@id\":\"https:\/\/monday.com\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/monday.com\/blog\/#\/schema\/person\/4cf4e679301900c5395f6f33cbc6d7c9\",\"name\":\"David Hartshorne\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/monday.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/ed456025e4e33ef078189c6c433af6cdb6ebb40d534d44f96d8393ab15fe0f34?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/ed456025e4e33ef078189c6c433af6cdb6ebb40d534d44f96d8393ab15fe0f34?s=96&d=mm&r=g\",\"caption\":\"David Hartshorne\"},\"description\":\"David Hartshorne is an experienced writer and the owner of Azahar Media. A former global support and service delivery manager for enterprise software, he uses his subject-matter expertise to create authoritative, detailed, and actionable content for leading brands like Zapier and monday.com.\",\"sameAs\":[\"https:\/\/azaharmedia.co.uk\",\"https:\/\/www.linkedin.com\/in\/dhartshorne\/\"],\"jobTitle\":\"B2B SaaS content marketing writer\",\"url\":\"https:\/\/monday.com\/blog\/author\/davidhartshorne\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PI Planning: The Ultimate Guide","description":"Master PI planning with monday dev. Learn steps, best practices, and AI tools to run smarter, more successful planning events.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/","og_locale":"en_US","og_type":"article","og_title":"PI planning: The ultimate guide for 2026","og_description":"Master PI planning with monday dev. Learn steps, best practices, and AI tools to run smarter, more successful planning events.","og_url":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/","og_site_name":"monday.com Blog","article_published_time":"2024-12-09T09:10:51+00:00","article_modified_time":"2026-03-10T10:14:56+00:00","og_image":[{"width":4800,"height":2400,"url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png","type":"image\/png"}],"author":"David Hartshorne","twitter_card":"summary_large_image","twitter_misc":{"Written by":"David Hartshorne","Est. reading time":"1 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#article","isPartOf":{"@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/"},"author":{"name":"David Hartshorne","@id":"https:\/\/monday.com\/blog\/#\/schema\/person\/4cf4e679301900c5395f6f33cbc6d7c9"},"headline":"PI planning: The ultimate guide for 2026","datePublished":"2024-12-09T09:10:51+00:00","dateModified":"2026-03-10T10:14:56+00:00","mainEntityOfPage":{"@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/"},"wordCount":6,"publisher":{"@id":"https:\/\/monday.com\/blog\/#organization"},"image":{"@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png","articleSection":["Product development life cycle"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/","url":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/","name":"PI Planning: The Ultimate Guide","isPartOf":{"@id":"https:\/\/monday.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#primaryimage"},"image":{"@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png","datePublished":"2024-12-09T09:10:51+00:00","dateModified":"2026-03-10T10:14:56+00:00","description":"Master PI planning with monday dev. Learn steps, best practices, and AI tools to run smarter, more successful planning events.","breadcrumb":{"@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/monday.com\/blog\/rnd\/pi-planning\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#primaryimage","url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png","contentUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/11\/PI-planning.png","width":4800,"height":2400,"caption":"PI planning The ultimate guide for 2026"},{"@type":"BreadcrumbList","@id":"https:\/\/monday.com\/blog\/rnd\/pi-planning\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/monday.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Product development life cycle","item":"https:\/\/monday.com\/blog\/rnd\/"},{"@type":"ListItem","position":3,"name":"PI planning: The ultimate guide for 2026"}]},{"@type":"WebSite","@id":"https:\/\/monday.com\/blog\/#website","url":"https:\/\/monday.com\/blog\/","name":"monday.com Blog","description":"","publisher":{"@id":"https:\/\/monday.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/monday.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/monday.com\/blog\/#organization","name":"monday.com Blog","url":"https:\/\/monday.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/res.cloudinary.com\/monday-blogs\/fl_lossy,f_auto,q_auto\/wp-blog\/2020\/12\/monday.com-logo-1.png","contentUrl":"https:\/\/res.cloudinary.com\/monday-blogs\/fl_lossy,f_auto,q_auto\/wp-blog\/2020\/12\/monday.com-logo-1.png","width":200,"height":200,"caption":"monday.com Blog"},"image":{"@id":"https:\/\/monday.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/monday.com\/blog\/#\/schema\/person\/4cf4e679301900c5395f6f33cbc6d7c9","name":"David Hartshorne","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/ed456025e4e33ef078189c6c433af6cdb6ebb40d534d44f96d8393ab15fe0f34?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ed456025e4e33ef078189c6c433af6cdb6ebb40d534d44f96d8393ab15fe0f34?s=96&d=mm&r=g","caption":"David Hartshorne"},"description":"David Hartshorne is an experienced writer and the owner of Azahar Media. A former global support and service delivery manager for enterprise software, he uses his subject-matter expertise to create authoritative, detailed, and actionable content for leading brands like Zapier and monday.com.","sameAs":["https:\/\/azaharmedia.co.uk","https:\/\/www.linkedin.com\/in\/dhartshorne\/"],"jobTitle":"B2B SaaS content marketing writer","url":"https:\/\/monday.com\/blog\/author\/davidhartshorne\/"}]}},"auth_debug":{"user_exists":false,"user_id":0,"user_login":null,"roles":[],"authenticated":false,"get_current_user_id":0},"_links":{"self":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/208481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/users\/213"}],"replies":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/comments?post=208481"}],"version-history":[{"count":28,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/208481\/revisions"}],"predecessor-version":[{"id":309923,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/208481\/revisions\/309923"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media\/210254"}],"wp:attachment":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media?parent=208481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/categories?post=208481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/tags?post=208481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}