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 3 primary outputs of PI planning?
Outputs include three primary artifacts: A set of aggregated specific, measurable, achievable, realistic, time-bound (SMART) PI objectives for the solution. A solution planning board (shown below), which highlights the capabilities, anticipated delivery dates, and any other relevant milestones for the solution.
What is the objective of PI planning?
Importance of PI Objectives: PI Planning aims at generating alignment and permits teams to plan, estimate and innovate their own work. It is a part of the SAFe approach to mission planning. The business owners present the overall goals of the list of the features and PI to the teams to come up with the objectives.
What are the two inputs of PI planning?
So what goes into a PI Planning? 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.
What are two outputs of Iteration planning?
The output of iteration planning is: The iteration backlog, consisting of the stories committed to for the iteration, with clearly defined acceptance criteria. A statement of Iteration goals, typically a sentence or two for each one, stating the business objectives of the iteration.
What is one output of enterprise strategy formulation?
One of the outputs of strategy formulation is Strategic Themes, which are differentiating business objectives and typically captured using Objectives and Key Results (OKR).
Which role is part of PI planning?
Role of a Scrum Master & Product Owner in Program Increment (PI) Planning Meeting. The Scaled Agile Framework (SAFe) helps achieve business agility by bringing alignment in strategy and execution. The Agile Release Train (ART) serves as a hub for all people and groups working toward one objective.
How many sprints are in a PI?
Teams apply common iteration lengths – within a PI there are 5 Sprints of 2 weeks each and each team adheres to the iteration length.
What is release and iteration planning?
Release and iteration planning broadly helps the team to prepare test planning checklist related to the following items: The team members responsible for testing. The scope of testing and testing goals to be carried out. The test environment that needs to be setup. The test data to be collected that helps the testing ...
Why is confidence vote held at the end of PI planning?
Confidence Vote is an activity done in the Program Increment Planning session after the risk assessment has been done. It is when all the team members sit together and raise their hand and with their fingers, vote their level of confidence on the PI Objectives being completed.
Is iteration planning and sprint planning same?
Sprint and iteration are essentially the same things. The standard duration for each is two weeks. However, on rare occasions, the work context may make a one, two, three, or four-week iteration a better choice.
What is PI in project planning?
PI planning is an opportunity to build trust in Agile teams, which is essential in an Agile release train. ARTs are designed to move as one towards a shared vision, and PI planning enables seamless cross-functional collaboration.
What is the ultimate goal of the PI planning event quizlet?
4.2) What is the goal of the PI Planning event? The PI planning events aligns all to a common mission and commitment around a clear set of prioritized objectives.
Who is responsible for PI objectives?
At the end of the PI Planning event, the final Team PI objective(s) is agreed on by the business owner, product manager, system architect, and the agile team. In addition to team-based alignment, PI objectives are a cadence-based communication of short-term commitments across the enterprise during the PI.
What is PI and why is it important?
The number π is defined to equal the ratio of the circumference of any circle to its diameter across. This ratio is constant. No matter what size of the circle we try this with, that number will be always the same. It begins 3.141592653589, and it keeps going.
What is PI planning?
PI Planning is a vital element of SAFe. It’s a ceremony that brings together representatives from every team to help them work together, decide on top features to work on next, identify dependencies, and make a plan for the next Program Increment.
How many key roles are there in a PI planning event?
There are 5 key roles in a PI Planning event:
What are the downsides of PI planning?
One of the major downsides of PI Planning is the suggested agenda includes some long, heavy sessions, right from the start. 😴 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 they’re shorter. That way, there’s more time for team planning and collaboration.
What is the role of product owner in PI planning?
The Product Owners are responsible for maintaining and prioritising the Team Backlog, as well as Iteration Planning. They have content authority to make decisions at the User Story level during PI Planning Team Breakout sessions.
Should everyone participate in PI planning?
Ideally, everyone will participate in the PI Planning live. But whether your team is distributed across multiple timezones or a couple of team members can’t make it on the day due to sickness or something else, it’s a good idea to record the event, too. 📹🎤 Plus, having a recording to refer back to could be useful for attendees who want a refresher on anything that’s been discussed.
Does PI planning always go well?
PI Planning doesn’t always go… well, to plan. And the framework itself may present a challenge to some organizations. Here are some common mistakes and challenges to keep in mind (and avoid, if possible):
Can PI planning be changed to fit multiple timezones?
Some teams will change the standard PI Planning agenda to fit multiple timezones, which could mean starting the event earlier or later for some, or even running it across 3 days instead of 2.
What are the inputs and outputs of PI planning?
The inputs for the PI Planning process are well defined business context, roadmap, vision and top 10 Features of the Program Backlog. The outputs, on the other hand, are two. The first one is a set of Team and Program Committed PI Objectives. These are a set of SMART objectives that are created by each team with the business value assigned by the Business
What is PI planning?
The idea of PI Planning is, that everyone plans together; teams estimate what will be delivered and highlight their dependencies with other Agile teams and trains, various requirements and designs emerge, important decisions are accelerated, and teams take responsibility for their own plans. It also provides the time and space to align all stakeholders around the next set of deliverables.
What is a pre-PI meeting?
Pre-PI Planning meeting is held before PI Planning and its purpose is to coordinate input objectives, Milestones and business and solution context for the PI Planning session. Post-PI Planning happens after PI Panning event and its purpose is to assess and remove Work in Process (WIP) and integrate the results of PI Planning into Vision and Roadmap for the larger value stream. At the end of post PI Planning there should be an agreement on a set of PI Objectives at solution level that need to be implemented by the end of Program Increment and demoed at the next Solution Demo (Source: Scaled Agile, Inc.).
What is the second output of a project?
The second output is the Program Board which helps visualize and highlight the new feature delivery dates, feature dependencies among teams and all the important Milestones.
What is a solution planning board?
A solution planning board, which highlights the capabilities, anticipated delivery dates, and any other relevant milestones for the solution
What is a PI objective?
PI Objectives are business summaries of what each team intends to deliver in the upcoming PI. They usually relate to Features in the backlog, but can also include important Milestones, Enable Feature that supports the implementation or major refactoring.
How long is a PI planning event?
PI Planning event takes place over two days, although it could be extended to accommodate planning across multiple time zones in case of distributed/remote teams. PI Planning agenda is standard for all PI Planning events. Event includes all members on ART and it occurs within the Innovation and Planning (IP) Iteration. Holding the event during the IP iteration avoids affecting the scheduling, or capacity of other iterations in the PI. Examples of agenda for Day 1 and Day 2 can be seen on below graphics.
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.
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.
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.
Why is PI planning important?
Okay, so PI planning helps empower your Agile project teams. But, why exactly is program increment planning important?
What does SAFe have to do with PI planning?
Performing PI planning in ART (Agile Release Train) becomes critical for SAFe ( Scaled Agile Framework ). No PI planning means that your team is not doing SAFe.
What are the challenges of virtual PI planning?
Do you know that the Agile manifesto expressly states that a face-to-face conversation is the most vital communication step within product development teams ?
