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.
.
Also to know is, what is pi Planning in Agile?
PI Planning stands for Program Increment Planning. 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.
Additionally, what happens after PI planning? The post-PI planning event occurs after the ARTs have run their respective planning sessions and are used to synchronize the ARTs and create the overall solution plan and roadmap. Plan review, risk analysis, and confidence vote – All the participants review the complete solution-level plan.
Also to know is, what is the goal of Pi planning?
It is the beating heart of the agile release train and any SAFe® implementation. PI planning is intended to be a highly collaborative event where teams take ownership of the suggested Features and work with their Product Owners to identify, estimate and elaborate the Features and their Stories.
Why is a confidence vote held at the end of pi planning?
A vote of confidence is held near the end of PI planning, where the teams commit to the PI objectives. Teams agree to do everything reasonably in their power to meet the committed objectives.
Related Question AnswersWhat are the three pillars of Scrum?
Empirical Process Control But in order to make good observations, there are three things necessary: transparency, inspection, and adaptation. We call these the three Pillars of Scrum. Let's dig a little bit deeper into each one.How many sprints are in a pi?
5 SprintsWho attends scrum of scrums?
Each team would then designate one person to also attend a scrum of scrums meeting. The decision of who to send should belong to the team. Usually the person chosen should be a technical contributor on the team—a programmer, tester, database administrator, designer, and so on—rather than a product owner or ScrumMaster.Who is responsible for PI planning?
Product Manager So, what is the product manager's role in PI Planning? They present the Program vision (aka top 10 Features that are coming up) plus any upcoming Milestones. They review the Draft plan and describe any changes to the planning and scope based on the Management Review & Problem Solving session.What are the two inputs to PI planning?
Inputs to PI planning include: Business context (see 'content readiness' below) Roadmap and vision. Top 10 Features of the Program Backlog.How long is 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. PIs are typically 8 – 12 weeks long. The most common pattern for a PI is four development Iterations, followed by one Innovation and Planning (IP) Iteration.What are the 4 core values of SAFe?
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.How do you conduct PI planning?
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 the last three steps of the SAFe implementation roadmap?
Figure 1. SAFe Implementation Roadmap- Reaching the Tipping Point.
- Train Lean-Agile Change Agents.
- Train Executives, Managers, and Leaders.
- Create a Lean-Agile Center of Excellence.
- Identify Value Streams and ARTs.
- Create the Implementation Plan.
- Prepare for ART Launch.
- Train Teams and Launch the ART.
Why do business owners assign value to PI objectives?
Communicate Business Value with PI Objectives As objectives are finalized during PI planning, Business Owners collaboratively assign business value to each of the team's individual objectives in a face-to-face conversation. Business value is assigned, not calculated, and serves as an input to execution considerations.What are two types of enabler stories?
There are many other types of Enabler stories including: Refactoring and Spikes (as traditionally defined in XP) Building or improving development/deployment infrastructure.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 pi objectives?
Program Increment (PI) Objectives are a summary of the business and technical goals that an Agile Team or train intends to achieve in the upcoming Program Increment (PI). During PI Planning, teams create PI objectives, which are the things they intend to accomplish in the upcoming PI.What is Pi in Scrum?
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. PIs are typically 8 – 12 weeks long. A Program Increment is to an ART (or Solution Train), as an Iteration is to the Agile Team.What are the two primary responsibilities of business owners in PI planning?
Among other duties, they have specific responsibilities during PI Planning, where they participate in mission setting, planning, draft plan reviews, conducting management reviews, and problem-solving. They also assign business value to Team PI Objectives and approve the PI plan.How often is 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. PIs are typically 8 – 12 weeks long. The most common pattern for a PI is four development Iterations, followed by one Innovation and Planning (IP) Iteration.How do you write a good PI objective?
Write SMART PI Objectives- Specific – States the intended outcome concisely and explicitly as possible.
- Measurable – It should be clear what a team needs to do to achieve the objective.
- Achievable – Achieving the objective should be within the team's control and influence.
