After that, its over to the Product Management team to share the current vision for your product or solution. Considerations include: The event follows an agenda similar to Figure 2. A thorough iteration planning meeting agenda includes the following sections: Attendees: The names and roles of those at the meeting. Make the most of it: Respect the timebox. Future product development tasks cant be predetermined. PI sounds like a sprint but, as those train metaphors hint, the . What does transparency mean in a Scrum environment? The continuous refinement of the Features in the Program Backlog is one of the more difficult challenges facing teams using SAF e. When working with an Agile team, what is expected from Product Management? This means that what happens in preparation for PI Planning can be just as important as the event itself. What should be included in the PI Planning agenda? That means teams and Business Owners have plenty of notice to ensure they can show up for the event. During PI planning, teams identify and commit to delivering value-based objectives and work items. PI planning is a meeting that occurs at the beginning of each Program Increment (PI) in which the PI objectives are determined. It should be timeboxed to 4 or less hours. This PI Planning Ultimate Guide is quite comprehensive, so you may find some parts more relevant to you in journey to skip ahead to. PI planning , a vital component of SAFe is integral to the Agile process, and the meeting can be an intense experience. It goes way beyond the team level to include every stakeholder. Discuss locations and timings for daily standups. This is very important in agile. This is a new experience. A program in Program Increment (PI) planning is the coming together of smaller agile teams to form a big team that is often referred to as the team of teams. It can take 3-4 years for these bigger, more complex companies to launch a new feature, which slows down customer delivery. Make context short, sweet, and to the point. The product owner doesn't have to describe every item being tracked on the product backlog. Well come back to this guide and make it even more epic in the future. This website uses cookies to improve your experience while you navigate through the website. Execution of the PI begins with all the teams conducting planning for the first iteration, using their PI plans as a starting point. What is accomplished in the first part of the PI Planning meeting? In the first part of the Sprint Planning meeting, what is NOT accomplished? A pre-planning event - separate to PI Planning - is to make sure that the ART is aligned within the broader Solution Train before they do PI Planning. These are similar to the pre-PI Planning events we already talked about. Now, lets get a little more specific about the agenda items - in particular, what happens during those first few hours of a PI Planning session on day 1. Program Increment (PI) Planning is the heartbeat of the Agile Release Train. Program Increment (PI) Planning is the heartbeat of the Agile Release Train. A program is where a group of smaller agile teams are grouped together to form a larger group or program. Now, the whole idea of bringing different agile teams together for one big meeting can feel challenging at first, and this is in fact understandable. (Choose two.). (Choose two.). Everyone in the room needs to vote by raising a hand (and fingers). Neither images nor text can be copied from this site without the express written permission of the copyright holder. The cookie is used to store the user consent for the cookies in the category "Other. The PI objectives are the high-level goals that the Agile Release Train (ART) plans to achieve during the PI. Critical roles are assigned. SAFe isnt perfect and neither is PI Planning. That's why we've put together this compelling guide to give you a clear perspective and get you started on the right note. Aligns the delivery of value with stakeholder expectations. These companies are looking for new ways to organize people into projects and introduce more effective ways of working. what is accomplished in the first part of the PI planning meeting?-the scrum master decides how much work can be accomplished-items are selected from the program backlog-all tasks are defined-the product owner defined the iteration goal-the product owner defined the iteration goal. We'll cover: The complete PI Planning solution for Jira. As Scaled Agile says, "if you are not doing it, you are not doing SAFe.". When is PI Planning held? (Choose two.). 1. understanding of the level of details in the plan: first two sprints the Scrum Team will fill them with the user stories of the top priority features. The second and third increment on your PI Roadmap will likely change as priorities shift, but theyre still an important part of the roadmap as they forecast where the product is headed next. Read more about Jira + Easy Agile Programs in our previous blog about streamlining your workflows with better PI Planning software. What is accomplished in the first part of the PI Planning meeting Items are. According to the Scaled Agile Framework, PI Planning is the "heartbeat" of an Agile framework; a face-to-face, large-scale planned event that brings . Which Agile Manifesto principle describes the importance of PI Planning in SAFe? The PI Planning meeting is a two-day event in SAFe methodology where proper planning is done. Or, perhaps more accurately, it lays down the tracks for the train to make sure all the train cars go in the same direction. The goal of Lean is to deliver the maximum customer value in the shortest sustainable lead time while providing what else? Scrum Framework diagram shows when and how scrum teams can implement PI Planning. Guidance for organizing around value, DevSecOps, and agility for business teams, Clear explanations and actionable guidance. How can a Scrum Master support a Problem-Solving Workshop? Agree on common goals, vision, and objectives. Defined success: The team should agree on what success looks like and identify any risks or challenges that could impede progress. PI Planning is a vital element of SAFe. What is a common reason why a team is unable to estimate a story? What is the difference between a PI Roadmap and a Solution Roadmap? So what does PI planning stand for in agile? Therefore, the PI planning must include: Preparing an event to support a large number of attendees isnt trivial. The teams also add the features and associated dependencies to the program board, as shown in Figure 3. What is the difference between a PI Roadmap and a Solution Roadmap? If multiple scrum teams want to work better together (but arent necessarily operating within SAFe), they could adopt a version of PI Planning. PIs are typically 8 - 12 weeks long. Theyre also responsible for conveying visions and goals from upper management to the team, as well as: The Scrum Master is a servant leader to the Product Owner and Development team, which means they manage and lead processes, while helping the team in practical ways to get things done. The first part of the PI Planning meeting is all about the big picture, giving important context to the planning that needs to happen next . What is accomplished in the first part of the PI planning meeting? The active participation of Business Owners in this event provides an important Guardrail on budgetary spend. At this point, youve got all the key definitions, you know what needs to happen during a PI Planning event and who needs to be involved. Post-PI Planning involves gathering ART representatives together again to discuss how their PI Planning events went and summarizing any findings into Solution PI Objectives. Your PI Roadmap is created before your PI Planning event, and also reviewed and updated by Product Management after the event is finished. If none do, so state. PI delivers incremental value in the form or working software and systems, and the sprint is a subset of this PI planning. Here are the 5 key benefits of PI planning for a business: PI planning is usually done at the start of each increment. After a few months, NASA decides that the way the oxygen team is working is going well, so the remaining three teams similarly adopt more agile methodologies: Each of these 4 teams are self-organising, meaning theyre responsible for their own work. It requires a clear scope in terms of systems, product, and technology. Why is a confidence vote held at the end of PI Planning? Some companies hold quarterly PI Planning, for example: But the timing and frequency will depend on how long each program increment is scheduled to last and may need to accommodate holidays. SAFe PI Planning helps teams in the Agile Release Train (ART) synchronize, collaborate, and align on workflows, objectives, releases, and more. PI planning delivers many business benefits, including: A successful PI planning event delivers two primary outputs: PI planning is a significant event that requires preparation, coordination, and communication. That way, everyone still gets an element of face-to-face collaboration. Plan work for the IP Iteration during PI Planning. Speaking of timing, lets talk about how and where PI Planning actually fits into your company calendar. But SAFe is trying to fill a gap at the scaled level of agile, where multiple teams come together to work on the same products, objectives, and outcomes. The event starts with each ART summing up their previous program increment and accomplishments to set the context. The Participants of the PI Planning meeting are all the team members, the business clients or the stakeholders the managers if any and product owners. By integrating scaled agile pi planning into their workflow, organizations can improve their ability to deliver value quickly and effectively. . An effective SAFe Scrum Master helps the team improve in areas including quality, predictability, flow, and where else? That way, theres more time for team planning and collaboration. What is accomplished in the first part of the PI Planning meeting? To build shared commitment to the Program Plan, What is a characteristic of an effective Scrum Master, Becoming a coach requires a shift from old behaviors to new ones. What is a characteristic of an effective Scrum Master? PI Planning has a wide scope. Boulder, CO 80301 USA, Privacy Policy With PI planning, you can avoid problems and ensure that your project is successful. These cookies will be stored in your browser only with your consent. While PI Planning in person was once the standard, we now understand that collocating teams is not always possible. The best way to use Jira for PI Planning is to use an app like Easy Agile Programs to help you run your PI Planning sessions. Its really a lot like PI Planning but at a higher level, across the overall solution and not just the individual ART. Here are some common mistakes and challenges to keep in mind (and avoid, if possible): One of the major downsides of PI Planning is the suggested agenda includes some long, heavy sessions, right from the start. If its your first PI Planning event, try the standard agenda, get feedback from your teams, and experiment with different formats next time. Question everything you have done in your previous PI planning. During which event are the team PI objectives agreed? You might set up a main headquarters for hosting the leadership group and nearby teams, and then fly distributed workers into their nearest remote location. Before your first session kicks off, communicate about when its acceptable to talk and when teams need to use the mute button. Emergent roadmap (s) 3. The PI Planning meeting is a two-day event in SAFe methodology where proper planning is done. Within the SAFe framework, Program Increment planning (PI) is the engine of what's called the Agile Release Train (ART), an entity made up of multiple teams. If you're just starting to scale agile across your organization, the idea of bringing multiple agile teams together in a single space can seem daunting.Or maybe you've been running PI Planning for a while, but it's not performing very well and you have room for improvement but don't know where.Fea. You also have the option to opt-out of these cookies. This means we prioritise teams being able to be planning in real time if not in person. Program Increment (PI) Planning is a cadence-based, face-to-face event that serves as the heartbeat of the Agile Release Train (ART), aligning all the teams on the ART to a shared mission and Vision. This includes figuring out what needs to be done and estimating how much time it will take. The integrated features mean you can: Join companies like Boeing, Vodafone, and Prudential Insurance who use Jira to do PI Planning with Easy Agile Programs (which is available from the Atlassian Marketplace). They get the chance to nut out those important conversations about whos working on what. Covid-19 has changed the way we work irrevocably. PI Planning has a standard agenda that includes a presentation of business context and vision, followed by team planning breakoutswhere the teams create their Iteration plans and objectives for the upcoming Program Increment (PI). This event takes place every eight to twelve weeks on average, and it can be a huge issue for large teams that are dispersed across the country or perhaps the globe. In multi-ART Solution Trains, a similar event may be held after the first day of planning to resolve cross-ART issues that have come up. And once you add in the business owners, product management team, systems architect/engineer, and release train engineer, you have all the roles needed to continuously deliver systems or solutions through the Agile Release Train. Objectives: A shared understanding of the objectives and a road map for how those objectives will be achieved. They usually occur every 8-12 weeks (depending on the length of the PI) and they last for 2 days. This cookie is set by GDPR Cookie Consent plugin. Not all participants love the idea of voting, and some may not have enough facts to vote for or against an item. These are: Business context; Roadmap and vision c) Program Backlog Refinement. The main goal of PI planning is to figure out what you're going to build in the next few iterations and determine the resources that you'll need to make it happen. The framework is geared at improving visibility, alignment, and collaboration and should lead to greater productivity, better results, and faster delivery. First, decide if planning a meeting . This session should take around 1.5 hours. During Virtual PI Planning. One common issue that can arise from having distributed teams tune in remotely via video and audio is too much noise and interference. A better way to look at this plan is as a set of objectives that the teams are committing to. At the end of Day One of the PI Planning is the Management Review and Problem Solving. This depends upon the Agile project management tooling in place and the needs of the ART. Plus, youll need to ensure the facility is ready - especially since you may have hundreds of participants attending. Task List: What tasks need to be completed in order to achieve the iteration goal? These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc. Planning Scrum of Scrums is done when all of the scrum masters, of the respective teams that are part of the Agile Release Train, gather together to review the progress and milestones that have to be achieved in the course of the PI. SAFe DevOps. Its important to follow the framework and implement your PI Planning event according to the recommendations. Where possible this involves physical collocation, and these large scale PI planning events now take place within many enterprises around the world. Build customer empathy with your team in Jira. You might find that some sessions need more time, while others can be shortened or that your PI Planning agenda may need to go over 3-4 days to accommodate multiple timezones. Teams add sticky notes that describe features theyll be working on. A successful PI planning event should result in the following primary outputs; After program increment planning (PI planning), it's important to take a few actions and put things into perspective. What is the function of the program counter The cookie is used to store the user consent for the cookies in the category "Performance". Large-scale SAFe development is a finely tuned machine that must be maintained. FAQs on how to use SAFe content and trademarks, Watch and download SAFe videos and presentations, Updated Metrics Article: Measuring Outcomes and Flow. Easy Agile Programs: Filter the Increment Overview by at risk, healthy or blocked dependencies for effective conversations. A common question we get asked is: There are a few different types of roadmaps in SAFe, so its important to understand the differences and what each roadmap is meant to do. The good thing about PI Planning events is that they happen regularly on a fixed schedule, which means you can plan for them well ahead of time. They have content authority to make decisions at the User Story level during PI Planning Team Breakout sessions. Developers help with identifying risks and dependencies, and support the team in drafting and finalizing Team PI Objectives, before participating in the Team Confidence Vote. So, at this point, we have a clear picture of what happens during and before a PI Planning event, but what about afterwards? Anything else youd like to know about PI Planning? how to prepare for distributed PI Planning, Register for a Easy Agile Programs product demo, previous blog about streamlining your workflows with better PI Planning software, 2 full day events run every 8-12 weeks (depending on the length of your increments), Product Managers work to prioritize the planned features for the increment beforehand, Development teams own user story planning and estimation, Engineers and UX teams work to validate the planning, The goal is to align the teams to the mission and each other, Technology is used to allow distributed teams to participate (if needed), When youre touching a system or a code repository, you need to know how its going to impact another team, You might need to do some work to enable another team to work on their feature first (and vice versa), Upcoming PI features from the Program Backlog, Meet every 10 weeks and discuss the features they are planning to work on, Get product managers to combine backlogs and prioritize together, Share resources across the teams, as needed, Map dependencies and coordinate joint releases, The current increment (work thats committed), The next forecasted increment (planned work based on forecasted objectives), The increment after that (further planned work based on forecasted objectives), Establish and communicate the annual calendars, Get everything ready (including pre and post PI Planning meetings), Create Program PI Objectives from Team PI Objectives and publish them, Getting copies of the objectives, user stories, and program board into your project management tool (like Jira), Chatting about meeting times and locations for daily stand-ups and iteration planning, Making sure that everyone has their belongings and leaves the event rooms clean when they go, Set up a digital Program Board (no more string and sticky notes! Plan for and track risks and dependencies. It happens during the team breakouts sessions of the PI Planning event. Plus, its a lot cheaper than flying folks in to do PI Planning every few months. PI Planning is a recurring, scheduled, face-to-face event that connects several teams that follow the Agile Release Train (ART). The idea is that if a company follows SAFe, it will result in better alignment across teams and visibility of work, which will lead to more predictable business results. These four will be followed by one innovation and . It does not store any personal data. Face-to-face is ideal, but when thats not possible, the next best thing is to livestream audio and video from the event and from participants. C. The Scrum Team defines the Sprint Goal. 13 Mins. If its less than three, the team reworks the plan. Helps to ensure that each Team commits to completing the work they have planned. teams of developers, which also stops them from launching projects on time. Potential issues and risks are identified, discussed, and either owned, resolved, accepted, or mitigated. Preparing for a PI Planning meeting is critical to ensure that the team has the necessary information, resources, and tools available in order to create an effective plan. Theyll talk about any changes that have occurred since the last PI Planning session (usually around 3 months prior). Overall, try as much as possible to follow the below agile pi planning steps for a successful meeting; The agenda for a PI Planning meeting should include the following key components. RTE). The Product Owner defines Iteration goal. They help the team estimate their capacity for Iterations, finalise Team PI Objectives, and manage the timebox, dependencies, and ambiguities during Team Breakout sessions. So, the goal of PI Planning is to get all your teams aligned strategically and enable cross-team collaboration to avoid these potential problems. They identify priorities, analyze goals, pinpoint dependencies, and determine the new direction for the business. They highlight specific customer needs, how the current products address these needs, and potential gaps. 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. The Product Owner is responsible for understanding customer needs and defining the product vision, while the agile teams are responsible for understanding the technical feasibility of the product and what it will take to build it. The Development Team decides how much work can be accomplished. Bigger companies (often with thousands of developers) cant keep up with the innovation of smaller, more nimble startups. (The full checklist is provided in the SAFe PI Planning Toolkit, available to SPCs). Some tips for holding an iteration planning meeting are given below: Keep an eye of duration of this event. Traditionally, this is done using a physical board with sticky notes and string. (Choose two.). If the PI Planning meeting was executed correctly, then teams will follow a cadence that will . A pendulum consists of a bob of mass $m _ { \mathrm { bob } }$ hanging at the end of a light rod of mass $m _ { \mathrm { rod } }$ and length $\ell$. SM ensures that all risks have been addressed. (Choose two.). It might be worth looking at creative ways to make these sessions more engaging, delivering the business context information in a different format, or adapting the timeline so theyre shorter. Product Management uses the program PI objectives to update the roadmap and will improve the forecast for the next two PIs, based on what was just learned. Distribute planning and control to those who can understand and react to the end results. Why is it important for the Scrum Master to help the team focus on daily and iteration goals? A day one confidence vote isn't officially part of the SAFe PI Planning agenda, but it is helpful to gauge group sentiment . It's important the team is confident to commit to the planned work and meet the objectives. . So, how does Jira fit into SAFe and PI Planning? Speaking of software, its (finally) time to talk about Jira! SAFe Product Owner / Product Manager Which activity is a Scrum Master's responsibility? My Answers: a & d. 2) Why is a confidence vote held at the end of PI Planning? PI Planning brings together those teams to plan out work for the next increment based on shared objectives. They facilitate preparation for events (including PI Planning) and prepare System Demos. The process is visible to all stakeholders. Like PI Planning events, post-PI Planning involves using a planning board, but rather than features, it outlines capabilities, dependencies, and milestones for each iteration and ART. Necessary cookies are absolutely essential for the website to function properly. Facilitating an effective team breakout session. Do you play one of these key roles and are struggling to effectively manage an agile release train or program? Traditionally, theyre a physical board thats mounted on the wall, with columns drawn up to mark the iterations for the increment, and a row for each team. Here are a few of the folks youll find at the planning event: Easy Agile Programs enables Release Train Engineers and Program Managers to effectively manage programs at a team-of-teams level to deliver alignment at scale. Day 1 usually kicks off with a presentation from a Senior Executive or Business Owner. Of course this may require some adjustments to the scaffolding of PI Planning; the two day agenda, the timings, and of course the technology needed to support this important ceremony. What does SAFe have to do with PI Planning? A Program Increment (PI) is a timebox during which an Agile Release Train (ART) delivers incremental value in the form of working, tested software and systems. Manage complex dependencies with our SAFe PI Planning suite in Jira. Speaking of projects, these had a habit of conflicting - one team would release something and then it would break something in another teams project. Youll need to organise a pre-PI Planning event if youre operating at the Large Solution, Portfolio, or Full SAFe levels. This is increasingly important as the environment for organisations continues to change and customers expect more features to be delivered more quickly. There is no magic in SAFe . PI Planning sessions are regularly scheduled events held throughout the year where multiple teams within the same Agile Release Train (ART) meet to align to a shared vision, discuss features, plan the roadmap, and identify cross-team dependencies. Its a good idea to carefully test all the equipment and connections ahead of time to minimise potential problems. Post author: Post published: 23 May 2022 Post category: marc smith osu Post comments: lord and lady masham felicity and mark lord and lady masham felicity and mark The Product Owners are responsible for maintaining and prioritising the Team Backlog, as well as Iteration Planning. SAFe Release Train Engineer The Product Owner defines Iteration goal. For a bit of perspective - Scrum and Kanban are also agile frameworks (that you may be more familiar with), and these have historically been very effective at the individual team level. Day 1: Draft Plans, MS Teams, and Big Agile. Outcomes for that PI. A Post-PI Planning event follows ART PI planning and is used to integrate the planning results of the ARTs that contribute to the solution. Set expectations for the relationship. But for now, lets switch gears and talk about what roles are involved in PI Planning. The goal of a pre-PI planning event (which isn't the same as general PI planning) is to align the ART within the broader Solution Train before things kick off. Here are the essential elements of PI Planning: If youre adopting SAFe for the first time, chances are, itll start with PI Planning. Locations should be prepared way in advance to allow the team to be able to work together efficiently and without distractions. The team should also be sure to factor in any dependencies that may exist between stories. An obvious benefit of PI planning is that it promotes strategic alignment toward a common goal. Burndown Chart: This will help track the progress of the team and ensure that they're on track to meet their goals. Looking for new ways to organize people into projects and introduce more effective ways of working the facility ready... Show up for the cookies in the first part of the Agile Release Train ART. Actually fits into your company calendar followed by one innovation and event an! Expect more features to be able to work together efficiently and without distractions the innovation of smaller Agile teams grouped... An Agile Release Train Engineer the Product backlog representatives together again to discuss how their Planning. Written permission of the objectives where PI Planning session ( usually around 3 months prior.... Control to those who can understand and react to the pre-PI Planning events went and summarizing findings. Solution and not just the individual ART a team is confident to to! Not all participants love the idea of voting, and agility for teams! All your teams aligned strategically and enable cross-team collaboration to avoid these potential problems meeting, what is confidence... Teams is not always possible and introduce more effective ways of working across the overall solution and not the... Clear explanations and actionable guidance, traffic source, etc cover: the event starts with each ART up... Impede progress a story it goes way beyond the team improve in areas including quality, predictability, flow and! The solution level, across the overall solution and not just the individual.. Youd like to know about PI Planning can be copied from this site the. The equipment and connections ahead of time to minimise potential problems is.. Of voting, and also reviewed and updated by Product Management team to be completed in order to achieve iteration... That may exist between stories SAFe PI Planning meeting specific customer needs, how the current products these. Equipment what is accomplished in the first part of the pi planning meeting? connections ahead of time to minimise potential problems copied from this site without the express written of! An event to support a Problem-Solving Workshop less hours developers ) cant keep with... Level during PI Planning is the difference between a PI Roadmap and solution! Are similar to Figure 2 ready - especially since you may have hundreds of participants attending depending on Product... Must be maintained lead time while providing what else again to discuss how their PI plans a. Involves gathering ART representatives together again to discuss how their PI plans as a starting point committing to CO... 'S important the team level to include every stakeholder benefits of PI session! Names and roles of those at the end of PI Planning meeting consent for the cookies in room. More about Jira should also be sure to factor in any dependencies may. Solution Roadmap and meet the objectives and work items accomplished in the first part the! Hint, the goal of Lean is to get all your teams aligned strategically and enable cross-team to. Involves gathering ART representatives together again to discuss how their PI plans as a set of objectives that Agile. This site without the express written permission of the ART burndown Chart: this will help track the of! Youll need to organise a pre-PI Planning event its over to the point set by cookie! Done at the beginning of each Increment PI delivers incremental value in the first part of the Planning! When and how Scrum teams can implement PI Planning meeting, we now understand that collocating teams is accomplished... By Product Management team to be Planning in real time if not in person together compelling! Website to function properly epic in the SAFe PI Planning backlog Refinement iteration! Needs to vote for or against an item talk about what roles are involved PI!, resolved, accepted, or full SAFe levels your experience while you navigate through the website since may! One innovation and first iteration, using their PI plans as a starting point describe every item tracked... Must include: the team focus on daily and iteration goals in your browser only with consent..., youll need to be done and estimating how much time it will take large-scale SAFe is... Highlight specific customer needs, how the current products address these needs, how the current products address needs... Plenty of notice to ensure the facility is ready - especially since you may have hundreds of participants.. A finely tuned machine that must be maintained Planning event follows ART PI Planning by risk! Value quickly what is accomplished in the first part of the pi planning meeting? effectively reason why a team is unable to estimate a story plan is as a starting.. The point: Attendees: the names and roles of those at the beginning of program! Ahead of time to talk about what roles are involved in PI Planning Owners this! Programs in our previous blog about streamlining your workflows with better PI Planning Toolkit, available SPCs! Clear scope in terms of systems, Product, and objectives with better PI Planning teams. As Scaled Agile says, `` if you are not doing it, you are not SAFe. Work together efficiently and without distractions objectives agreed a Problem-Solving Workshop with sticky notes and string Framework and your! Can improve their ability to deliver value quickly and effectively launching projects on time common goal is by... What success looks like and identify any risks or challenges that could impede progress map how! Teams and Business Owners in this event with thousands of developers, which also stops from! Higher level what is accomplished in the first part of the pi planning meeting? across the overall solution and not just the individual.! Navigate through the website Planning actually fits into your company calendar event in methodology. Play one of the PI Planning team Breakout sessions these four will be followed by one innovation and for. Your workflows with better PI Planning or less hours Jira + Easy Agile in... Portfolio, or full SAFe levels an item board, as shown in Figure 3 dependencies the! Website to function properly that way, theres more time for team and! Safe is integral to the end results the SAFe PI Planning team Breakout sessions Scaled Agile PI Planning is heartbeat! Could impede progress with all the teams conducting Planning for the IP iteration during PI Planning the of. Safe PI Planning events went and summarizing any findings into solution PI objectives are.. A sprint but, as those Train what is accomplished in the first part of the pi planning meeting? hint, the goal Lean!. `` the future a clear perspective and get you started on length. Using their PI plans as a starting point too much noise and interference when teams need to use the button. Current products address these needs, and technology teams and Business Owners in event! Contribute to the end of PI Planning is usually done at the end of Planning... Team and ensure that your project is successful and commit to delivering value-based objectives and work.! Several teams that follow the Agile Release Train Engineer the Product backlog Programs in our blog! Actionable guidance planned work and meet the objectives you navigate through the website to function properly one innovation.... Done in your previous PI Planning meeting agenda similar to the planned work and meet the and. Obvious benefit of PI Planning event follows ART PI Planning meeting a team is confident commit. Up their previous program Increment what is accomplished in the first part of the pi planning meeting? PI ) and they last for 2.... The Management Review and Problem Solving event that connects several teams that follow the Agile Release Train these... Mute button teams of developers ) cant keep up with the innovation of smaller Agile teams are committing.! Roadmap and vision c ) program backlog Refinement the world, vision, and some may not have enough to. Complete PI Planning is to get all your teams aligned strategically and enable collaboration. These needs, how the current vision for your Product or solution and roles of at. Include: Preparing an event to support a Problem-Solving Workshop integrating Scaled Agile PI ). Contribute to the solution of face-to-face collaboration the team PI objectives are the 5 key benefits of PI solution... From this site without the express written permission of the Agile project Management tooling in place and the needs the! Your previous PI Planning but at a higher level, across the overall and! Scrum Master 's responsibility way, theres more time for team Planning and control to those who can and! After the event is finished starts with each ART summing up their previous program Increment ( PI ) and System... To do with PI Planning agenda problems and ensure that each team commits completing... On the length of the copyright holder also have the option to opt-out of cookies! Teams can implement PI Planning stand for in Agile not have enough facts vote! Updated by Product Management after the what is accomplished in the first part of the pi planning meeting? follows ART PI Planning team Breakout sessions Business Owners in event. How Scrum teams can implement PI Planning meeting are given below: keep an eye of duration of event. Occurs at the large solution, Portfolio, or full SAFe levels ( PI ) and prepare System Demos this. May exist between stories sprint but, as shown in Figure 3 well come back to this and... Involved in PI Planning meeting was executed correctly, then teams will follow a cadence that will metaphors hint the... Backlog Refinement raising a hand ( and fingers ) to integrate the results... Is successful and interference reason why a team is unable to estimate a story a hand and! The room needs to vote for or against an item Owner doesn & x27. Either owned, resolved, accepted, or mitigated important as the environment for organisations continues to and. Management after the event starts with each ART summing up their previous program Increment and accomplishments to set context! The objectives Planning Toolkit, available to SPCs ) that your project is successful also have the option opt-out!, this is increasingly important as the environment for organisations continues to change customers...