Table of Contents
When should PI planning occur?
every eight to 12 weeks
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. We are here to explore PI Planning, its importance to SAFe development, and some of the challenges of PI planning with multi-locational teams.
What is pi planning event?
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.
How often is pi planning done?
every 8-12 weeks
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.
During which event are the team pi objectives agreed?
PI Planning event
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.
When should a complicated subsystem team be used?
A complicated subsystem team could build things such as: Highly specialized system components, often used across multiple systems. Safety-critical systems elements, which have a high cost of failure. Specialty algorithms or business rules that are critical for fitness of use in the domain.
What’s the importance of a program board and how would you characterize the PI planning event?
The Program Board is a critical artifact to successful PI planning. It helps teams within the Agile Release Train (ART) visualize and track dependencies across their PIs. With the board, they have a clear idea of what’s done, what’s being worked on, and what might keep them from getting their work completed on time.
What do you need to prepare before planning pi?
Prepare for Pre- and Post-PI Planning
- The 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 two strategies for effective 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. A team is running out of time to draft their PI objectives for the draft plan review because they are creating very detailed plans.
During which event are the team pi?
PI Planning
During PI Planning, teams create PI objectives, which are the things they intend to accomplish in the upcoming Program Increment (PI).
What is one of the key outcomes from solution pre PI planning?
As with PI planning, the pre- and post-PI planning events deliver several business benefits: Provide open and productive communication through face-to-face alignment. Synchronize ARTs with Solution Train vision via the ART and solution PI objectives. Identify dependencies and foster cross-ART coordination.