Inputs to PI planning include:
- Business context (see ‘content readiness’ below)
- Roadmap and vision
- Top 10 Features of the Program Backlog
What are the outputs of Pi planning?
The issues are placed in one of these categories:
- Resolved – After discussion, the teams agree that the issue is no longer a concern.
- Owned – Someone on the train takes ownership of the item to work on solving the issue at a later time.
- Accepted – Some risks are just facts or potential problems that must be understood and accepted.
What is the purpose of Pi planning?
- Planning Locations: Minimize the number of dispersed locations by determining the number of locations needed.
- PI Planning Agenda: Creating an inclusive PI planning agenda to accommodate multiple time zones for the participating teams.
- Facilities: Setting up the appropriate physical space to conduct the planning.
What is the goal of the Pi planning event?
Solution Train PI Execution
- Pre- and Post-PI Planning. Pre- and Post-PI Planning events are used for preparation and coordination of PI planning across multiple ARTs and Suppliers in a Solution Train.
- Solution Increment and Solution Demo. During the PI timebox, the ARTs build multiple increments of value, which grow into solution capabilities.
- Solution Train Inspect and Adapt. ...
How to plan second PI planning?
Pre- and post-PI planning events allow Agile Release Trains and Suppliers in large Development Value Streams to build a unified plan for the next PI. The pre- and post-PI planning events serve as a wrapper for the PI planning at the Essential Level , where the actual detailed planning takes place and is incorporated into the Innovation and ...
What are two outputs PI planning?
A successful PI planning event delivers two primary outputs: Committed PI objectives – A set of SMART objectives that are created by each team with the business value assigned by the Business Owners. Program board – Highlighting the new feature delivery dates, feature dependencies among teams and relevant Milestones.
What are the 2 strategies for effective distributed PI planning events?
What are 2 strategies for effective distributed PI planning events? Extend PI planning to 2.5 or 3 days. Extend PI planning to 2.5 or 3 days.
What are the 2 benefits of PI objectives?
These provide several benefits: Provide a common language for communicating with business and technology stakeholders. Creates the near-term focus and vision. Enables the ART to assess its performance and the business value achieved via the Program Predictability Measure.
What is PI in project planning?
Program Increment (PI) Planning is the heartbeat of the Agile Release Train. Or, perhaps more accurately, it lays down the tracks for the train to make sure all the train cars go in the same direction. Large-scale SAFe development is a finely tuned machine that must be maintained.
What two actions are part of the scrum masters role in PI planning?
During PI planning, which two tasks are part of the scrum master's role in the first team breakout?Provide clarifications necessary to assist the team with their story estimating and sequencing.facilitate the coordination with other teams for dependencies.More items...
What are two strategies a product owner can use during program increment planning?
Answers of Question What are two strategies a Product Owner can use during Program Increment Planning to minimize dependencies? is Move Stories on their team's backlog to another team, Split Stories to eliminate dependencies, asked in PO PM Certification Exam.
What are two purposes of the system demo?
The goal of the system demo is to learn from the most recent development experience and adjust the course of action. However, some components don't lend themselves to continuous integration – hardware, mechanical systems, and supplier-provided components, and scarce components due to costs or availability.
Which two responsibilities belong to the product owner?
What Are a Product Owner's Major Responsibilities?Managing and prioritizing the product backlog. ... Translating product managers' strategies to tasks for development. ... Learning the market and customers' needs. ... Serving as a liaison between product and development. ... Staying accessible to development to answer questions.
Which two options are part of the SAFe core values?
The four Core Values of alignment, built-in quality, transparency, and program execution represent the fundamental beliefs that are key to SAFe's effectiveness. These guiding principles help dictate behavior and action for everyone who participates in a SAFe portfolio.
What are the PI planning stages include?
Here are the essential elements of PI Planning: 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.
What are two good scrum master facilitation practices choose two?
Answers of Question What are two good scrum master facilitation practices? is create an environment of safety so that everyone feels comfortable contributing to the discussion, ensure all voices are heard, asked in Scrum Master Certification Exam.
Which two actions enhance an agile release train's performance?
What improves collaboration between Scrum Masters and System Architects, System Teams, and Operations? Which two actions enhance an Agile Release Train's performance? (Choose two.) Collaboration;Team alignment; What are three distinct traits a group must have to be considered a Community of Practice? (Choose three.)
What are some improvements you could make as to how you engage during PI planning?
Five powerful tips for virtual PI planning eventsExtend PI planning timelines. ... Move to the cloud. ... Groom and manage program backlog. ... Livestream and record the entire event. ... Conduct pre and post-PI planning events.
How do you prepare for PI planning?
Prepare for Pre- and Post-PI PlanningThe executive briefing – Defines current business, solution, and customer context.Solution vision briefing(s) – Briefings prepared by Solution Management, including the top capabilities in the solution backlog.Define milestones – Clearly explain upcoming events and key dates.
What are the inputs for pre- and post-PI planning?
Inputs to pre- and post-PI planning include the Solution Roadmap, vision, Solution Intent, and the top Capabilities from the Solution Backlog. Attendees include:
What is PI planning?
Program Increment (PI) planning is the critical, cadence-based synchronization point for every ART. For Solution Trains, however, there are two additional activities: pre- and post-PI planning. They support and coordinate the various ARTs involved in the Solution Train.
What are the key stakeholders in ART PI?
However, it’s critical that key stakeholders—particularly Solution Management, the Solution Train Engineer, and Solution Architect/Engineering —participate in as many of the ART PI planning sessions as possible. In many cases, ART planning sessions are concurrent, and these solution stakeholders may attend by circulating among the ART PI planning sessions. Suppliers and customers play a critical role as well, and they should be represented in ART PI planning.
What is a smart solution PI?
A set of ‘ SMART’ solution PI objectives for the Solution Train, with the business value set by Solution Management, Solution Architect/Engineering, and customers. This may include uncommitted objectives, which are goals built into the plan but not committed to by the solution. Uncommitted objectives provide the flexible capacity and scope management options needed to increase predictability and quality of PI execution.
What is solution planning board?
A solution planning board, which highlights the objectives, anticipated delivery dates, and any other relevant milestones, aggregated from the program boards, as Figure 3 illustrates.
What is a pre- and post-PI?
The pre- and post-PI planning events serve as a wrapper for the PI planning at the Essential Level, where the actual detailed planning takes place and is incorporated into the Innovation and Planning (IP) Iteration calendar.
What is a pre-PI planning event?
The pre-PI planning event is used to develop the context for the ARTs and suppliers to create their individual plans. A suggested agenda is shown in Figure 1 and each item is described next.
What is PI in Agile?
A Program Increment ( PI) starts with a time-boxed PI Planning event in which Agile Release Train responsible for planning & delivering incremental value in the form of working, tested software and systems . This is a two-day event where all stakeholders (including Agile/Scrum Teams) on the Agile Release Train (ART) participate in a collocated event. All teams have their own areas setup for their planning together with a Program Area with a Program Board to map Feature delivery and dependencies across teams. PI are usually 8 – 12 weeks long.
What is a PI roadmap?
Answer: PI Roadmap is created before your PI Planning event, and also reviewed and updated by Product Management after the event is finished. It will usually cover three Program Increments:
What is a draft plan review?
Draft Plan Review: This is a time-boxed meeting where the teams present their draft plans so that business owners, product owners, stakeholders and other teams can give feedback.
What is the purpose of release planning?
Goals: The primary purpose of release (PI) planning is to gain alignment between business owners and program teams on a common, committed set of Program Objectives and Team Objectives for the next release (PI) time-box.
How long is a PI?
PI are usually 8 – 12 weeks long. Purpose: The purpose of PI Planning is to create an emergent roadmap to deliver a prioritized and agreed set of outcomes as well as identify both known and potential impediments to progress.
What is RTE in planning?
Planning Context & Lunch: The Release Train Engineer (RTE) outlines how the PI planning process will work and what is expected from the teams and the overall meeting.
How many votes are needed for a Fist of Five?
It is a Fist-of-Five vote from all team members. Any vote less than 3 should be explored and commitments potentially re-worked until all team members vote at least a 3.
What are the inputs and outputs of PI planning?
Following are the inputs to the PI Planning: 1. Customer should be ready with what he needs from the Program. The context needs to be set and ready. Basically, the in-scope items, its priorities. 2. Product Owner or Client should be ready with Roadmap and goal. 3.
What is PI planning?
PI Planning full form is Program Increment Planning. PI Planning is one of the most important ceremonies of SAFe implementation. Program Increment (PI) Planning is the core of the Agile Release Train.
What is a PI planning meeting?
The PI Planning meeting is a two-day event in SAFe methodology where proper planning is done. 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. The PI Planning is done with everyone assembled at the same place to assess the program backlog and based on which prioritize the items for upcoming sprints. If everyone is not located at the same location then probably, everyone can get into either audio/ video call to conduct the Program Increment Planning. Basically, this planning is done to understand what the client expects in next couple of sprints and what all are the value adds to the customer. This meeting characteristically occurs once in every eight to 12 weeks.
How many sprints are in PI planning?
Sprint Planning is done for the single Sprint whereas PI planning is done for four sprints together to get a vision of business value. Sprint planning is done once in either 2, 3 or 4 weeks at the beginning of the Sprint depending upon the sprint length.
How often should I have a PI meeting in Agile?
It is mandatory to have a face-to-face PI planning in agile meeting every 8 to 12 weeks which will certainly pave way for team communication. When the entire team meets they will understand things better and can brainstorm challenges.
How long does PI planning take?
PI Planning is done to help the developers and every team member to stay connected with the other team members, and stay updated about the processes once in 8 to 12 weeks. Therefore, it offers major benefits as listed below.
Why is PI planning important?
Overall, we can understand that PI planning enhances communication, provides clarity, and thus helps in strategizing the share vision to all the team members.
Who is responsible for ensuring that the people responsible for owning or mitigating a risk have captured the information?
Program risks remain with the RTE , who ensures that the people responsible for owning or mitigating a risk have captured the information and are actively managing the risk.
What is a team planning based on?
Teams continue planning based on their agenda from the previous day, making the appropriate adjustments. They finalize their objectives for the PI, to which the Business Owners assign business value
What is the role of RTE in a problem solving meeting?
The RTE facilitates and keeps the primary stakeholders together for as long as necessary to make the decisions needed to reach achievable objectives.
How many fingers are needed for a fist of five?
Each team conducts a 'fist of five' vote. If the average is three fingers or above, then management should accept the commitment. If it's less than three, the team reworks the plan. Any person voting two fingers or fewer should be given an opportunity to voice their concerns. This might add to the list of risks, require some re-planning, or simply be informative. Once each team has voted the process is repeated for the entire ART with everyone expressing their confidence in the collective plan, as illustrated in Figure 5.
What is Continuous Delivery Pipeline?
a method to visualize and manage the flow of Features and Capabilities from ideation to analysis, implementation, and release through the Continuous Delivery Pipeline.
When is PI planning scheduled?
PI Planning is scheduled at the beginning of each Program Increment and after the Inspect & Adapt Iteration. Although some companies may start the PI Planning event with the Inspect & Adapt meeting, that is not the focus of this article. The outcomes of the Inspect & Adapt event should be a part of the content of the PI Planning going forward. These items become action items for the next Program Iteration.
How often is PI planning?
The PI Planning event is two days of focused planning with all the teams, stakeholders, and product owners/managers in one place to review the program backlog and determine the direction of the business. This event typically happens every eight to 12 weeks and can be a significant challenge for large teams that are spread out across the country or even the world.
How to vote on confidence in PI?
Confidence Vote – Once all the risks and objectives have been outlined and discussed, the teams will vote on their confidence that the objective can be accomplished in the coming PI. This is a five-finger vote. The team members will hold up their hands with one to five fingers. Anything less than a three-finger vote will need to be addressed. The team member that has a problem with an objective will need to explain the issue so that it can be addressed by the teams. If the problem is satisfied, the objective is voted on again to reach a confidence vote for the coming PI.
What is PI in Agile?
Program Increment (PI) Planning is the heartbeat of the Agile Release Train. Or, perhaps more accurately, it lays down the tracks for the train to make sure all the train cars go in the same direction. Large-scale SAFe development is a finely tuned machine that must be maintained.
What is RTE in PI planning?
Planning Context & Lunch – The Release Train Engineer (RTE) outlines how the PI planning process will work and what is expected from the teams and the overall meeting. They will often outline what the expected outcomes are for the meeting and answer any questions that the teams may have about the process.
Can a team attend a PI planning meeting?
While many of the team members may be onsite and can attend the PI Planning meeting, there may be entire teams that cannot . For SAFe to evolve, consideration and thought will need to be given to how best to include the valuable input of these remote teams.
Is PI planning important?
With the addition of business agility to the framework, PI Planning (and the pre- and post-PI Planning ceremonies) becomes even more valuable to the business. As a business expands Agile, expanding PI Planning to multiple events to include all parts of the organization, connecting the ARTs, and the work to the overall business goals, is tricky. This is where leadership comes in. There must be buy-in from the leadership at the top and implementing a PI Planning-like event for leadership (think Quarterly Steering) to inform the business may be necessary.
What are the outputs of PI planning?
Outputs from a PI Planning 1 We also gain an insight into each team’s velocity for Iteration 1 and Iteration 2 at the minimum, along with the User stories with Size identified for these iterations that the teams will work on. 2 An important output of the PI Planning is the Program Dependency board which depicts the Features/ Stories, any Dependencies, and the Milestones. Architects and UX team members play a key role to help identify these dependencies. 3 PI Planning also gives us a list of Risks identified and how they have been addressed through ROAM (Resolved, Owned, Accepted, Mitigated) mechanism.
What is PI planning?
The PI Planning is meant for the entire team allocated to the Agile Release Train and everyone is expected to attend it. If some of the team members are at other locations, they need to join in remotely. The PI Planning meeting is divided into different sessions held over the 2 day period.
What does PI mean in a plan?
And what does the ‘PI’ in PI Planning mean? Well – PI stands for Program Increment. A Program Increment is a fixed timebox of 8 to 12 weeks (default being 10 weeks as recommended by Scaled Agile Inc.). The 10 weeks’ time-box encapsulates 5 Agile Sprints or Iterations with each spanning 2 weeks.
How long is a PI meeting?
This meeting is referred to as PI Planning. It is an elaborate and detailed meeting and has a duration of 2 days for a 10 week PI .
What is program vision?
The Program Vision and Program Backlog are two key inputs that are essential for conducting a PI Planning meeting. The Vision provides the context to the entire team on why and how the work being done in the PI will help in the delivery of the overall Solution. The Program Backlog comprises of the top 10 Features ranked by Priority and accompanied with a short description of the Business Benefit that the Feature would beget.
Why is PI planning important?
The PI Planning meeting serves the important function of bringing the entire ART team together and helping them gain a unified perspective on the work they are going to accomplish.
Who organizes the PI planning meeting?
The PI Planning meeting is organized by the Release Train Engineer (RTE, also called the Scrum Master of the Agile Release Train). The RTE presents the Vision and the top 10 Features in the inaugural session of the PI Planning.
What is PI in a program?
Program Increment ( PI) is one of the most critical part for successful PI delivery. If PI planning is not done properly due to any reason like insufficient backlog, or improper grooming, the whole PI will be chaotic and full of challenges.
When is PI planning scheduled?
PI Planning is scheduled at the beginning of each Program Increment and after the Inspect & Adapt Iteration. Although some companies may start the PI Planning event with the Inspect & Adapt meeting, that is not the focus of this article. The outcomes of the Inspect & Adapt event should be a part of the content of the PI Planning going forward. These items become action items for the next Program Iteration.
What is PI in Agile?
Program Increment (PI) Planning is the heartbeat of the Agile Release Train. Or, perhaps more accurately, it lays down the tracks for the train to make sure all the train cars go in the same direction. Large-scale SAFe development is a finely tuned machine that must be maintained.
How long does PI planning last?
PI Planning normally lasts for two days which involves many ceremonies. Complete two-day agenda is defined to include the following
What is a big room planning?
It is a whole team event where the whole program – the set of smaller agile teams working closely together as a single team-of-teams – come together in a big room (hence it is often referred to as Big Room Planning) to agree a plan for the next 8 – 12 weeks. The goal of the event is to create alignment, encourage collaboration, enable self-organization, eliminate waste and exploit the synergy between the teams.
Inputs and Outputs
Gain Context in The Solution Demo
- The solution demo is to the Solution Train, what the System Demois to the ART. It is a regular opportunity to evaluate a fully integrated solution. Usually hosted by Solution Management, solution stakeholders typically attend. The insights from the demo will inform these stakeholders of the current objective assessment of solution progress, performance, and potential fitness for …
Prepare For Pre- and Post-PI Planning
- The pre- and post-PI planning events bring together stakeholders from all parts of the Solution Train. They require advance content preparation, coordination, and communication. The actual agendas and timelines listed below are a suggested way to run these events, but various value streams may adapt these to their capabilities and locations. Regardless of how the timing and p…
Create The Right Outcomes
- A successful event delivers three primary artifacts: 1. A set of ‘SMART’ solution PI objectivesfor the Solution Train, with the business value set by Solution Management, Solution Architect/Engineering, and customers. This may include uncommitted objectives, which are goals built into the plan but not committed to by the solution. Uncommitted objectives provide the flexi…
Coordinating Solution Train and Art Planning Events in The IP Iteration
- Completing all the necessary refinement, pre- and post-planning, PI planning, and Inspect and Adapt (I&A)workshops for a Solution Train and its ARTs can represent a logistical challenge. STE and all RTEs sequence the events to ensure the correct stakeholders are present during planning. Figure 4 shows a sample schedule of a two-week IP iteration with all the solution and ART event…