- 1 Who does PI planning in Agile?
- 2 How do you facilitate a PI planning session?
- 3 What is the scrum masters role in PI planning?
- 4 What is a PI plan?
- 5 What happens in a PI planning session?
- 6 What are the 2 inputs to PI planning?
- 7 How long is a PI?
- 8 How long is pi planning?
- 9 What should I bring to PI planning?
- 10 How many sprints are in a pi?
- 11 What are the three pillars of Scrum?
- 12 Why does a scrum master use the powerful questioning technique?
- 13 What should PI objectives be based on?
- 14 What is the goal of a PI planning event?
- 15 What is the difference between Pi roadmaps and solution roadmaps?
Who does PI planning in Agile?
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.
How do you facilitate a PI planning session?
- Establish (and stick to!)
- Align all Participants with Clear Objectives and a Clear Vision.
- Empower your people to make decisions throughout the Planning event.
- Gain Consensus with the Business BEFORE you start planning.
What is the scrum masters role in PI planning?
Responsibilities. An effective Scrum Master is a team-based servant leader who: They help the team focus on creating increments of value each iteration and achieving daily and Iteration Goals in the context of the current Program Increment (PI) Objectives.
What is a PI plan?
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. PI planning is essential to SAFe: If you are not doing it, you are not doing SAFe.
What happens in a PI planning session?
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. The goal is to align the teams to the mission and each other.
What are the 2 inputs to 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.
How long is a PI?
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. A PI is to an Agile Release Train (ART) (or Solution Train), as an Iteration is to the Agile Team.
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 should I bring to PI planning?
Set Planning Context in Pre-PI Planning
- PI summary reports – Each ART and supplier presents a brief report of the accomplishments of the previous PI.
- Business context and solution vision – A senior executive presents a briefing about the current state of the solution and portfolio.
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 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.
Why does a scrum master use the powerful questioning technique?
Sprint Retrospective is the last Scrum event within a Sprint. During this event entire Scrum Team- Scrum Master, Product Owner & Development Team inspects the Sprint and decides how to improve the next Sprint. Powerful questions help the team to identify solutions and explore other various possibilities.
What should PI objectives be based on?
The PI objectives should draw focus towards helping the user or the business owner implement a feature. It should be planned in such a way that you get feedback as early as possible so changes can be made in time so that it reduces costs and risks in the future.
What is the goal of a PI planning event?
In addition to opening lines of communication, the goal of a PI planning event is to: Create an Agile Release Train (ART). The ART aligns vision, planning, risks, and dependencies among the various teams to focus on fast, flexible development and release.
What is the difference between Pi roadmaps and solution roadmaps?
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.