Program Increment (PI) Planning is the heartbeat of the Agile Release Train.
What is Pi in Agile methodology?
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 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 pi planning in Scrum?
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.
What is pi session?
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.
Who attends Pi planning?
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.
Who reviews the top capabilities for the upcoming pi?
Solution backlog – Solution Management will review the top capabilities for the upcoming PI. Solution Architect/Engineering will discuss upcoming Enabler capabilities and Epics.
How long 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.
What is IP Sprint?
The Innovation and Planning (IP) Iteration occurs every Program Increment (PI) and serves multiple purposes. It acts as an estimating buffer for meeting PI Objectives and provides dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt (I&A) events.
What should PI objectives be based on?
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 Program Increment (PI).
How do you make pi planning fun?
Treasure hunts and scavenger hunts are another fun way to get people working together. Give each team member a list of things to find or do, like visit another team to find program risks and dependencies and determine whether or not they impact the plan being created.
What is the goal of Pi planning?
The goal of PI Planning is to ensure that the Agile Release Train has clear goals and a high-level emergent plan for the upcoming Program Increment (PI).
Who facilitates 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.
What is the difference between a PI roadmap and a solution roadmap?
PI roadmap: The PI roadmap consists of a committed plan for the current PI and a small number of future PIs. … Solution roadmap: The solution roadmap provides a longer-term—often multiyear—view, showing the key milestones and deliverables needed to achieve the solution vision over time.
What are two primary responsibilities of business owners increment PI planning?
The importance of the Business Owner’s role during PI planning cannot be overstated. They: … Are ready and available to participate in key activities, including the presentation of vision, draft plan review, assigning business value to team PI objectives, and approving final plans.
What is the first step in the problem solving workshop?
Steps Step 1: Identify Possible Causal Factors. During the situation analysis, the project team set the vision, identified the problem and collected data needed to better understand the current situation. Step 2: Identify the Root Cause. Step 3: Identify Communication Challenges.