PI Planning is a meeting of multiple teams working in an Agile Release Train (ART) where they meet to plan the roadmap, deliberate on features, and identify cross-team dependencies.

What do we do in pi 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. … The goal is to align the teams to the mission and each other.

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.

How do you prepare for PI planning?

1. The executive briefing – Defines current business, solution, and customer context.
2. Solution vision briefing(s) – Briefings prepared by Solution Management, including the top capabilities in the solution backlog.
3. Define milestones – Clearly explain upcoming events and key dates.

How often is pi planning done?

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 a PI objective?

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). … Provide a common language for communicating with business and technology stakeholders. Creates the near-term focus and vision.

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 in SAFe?

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.

Is Pi planning waterfall?

The PI Planning “Waterfall“), it is to create common understanding. PI Planning does not separate “planners” and “doers”: Given a prioritized list of abstract, high-level stories (“features”), they decide autonomously what to do while exploring the “Why” together with others.

What is pi backlog?

Refining the Backlog Agile Release Trains and Solution Trains run a steady 8-12 week Program Increment (PI) cadence of planning, execution, demo, and Inspect and Adapt (I&A). This regular rhythm is the heartbeat that drives backlog readiness as well.

Article first time published on

What is P1 planning?

A part of Scale Agile, P1 planning is done on the product-level before every release to bring teams together for discussions on the features. During this stage, all the team members scheduled to work together on the product devote initial two-three days in planning without getting involved in any sprint work.

What is the importance of the definition of done?

The Definition of Done ensures everyone on the Team knows exactly what is expected of everything the Team delivers. It ensures transparency and quality fit for the purpose of the product and organization.

What is team's commitment during Pi planning?

A vote of confidence is held near the end of PI planning, where the teams commit to the PI objectives. However, it must be a reasonable ask of the people who do the work. Therefore, the SAFe commitment has two parts: Teams agree to do everything in their power to meet the committed objectives.

What are two common PI planning anti patterns?

• Too much time spent analyzing each story.
• Part-time scrum masters do not have time to plan as part of the team.
• Too much time spent analyzing each story.

What is Agile Release Train?

The Agile Release Train (ART) is a long-lived team of Agile teams, which, along with other stakeholders, incrementally develops, delivers, and where applicable operates, one or more solutions in a value stream.

What do Agile release trains realize?

When organized into Agile Release Trains, or teams of teams, high-performing Agile teams can realize their full potential: consistently, sustainably delivering value to the end users of their respective value streams.

What is the purpose of iterations?

Iterations provide a regular, predictable cadence for teams to produce an increment of value, as well as to refine those previously developed.

What are 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.

What is the purpose of a program epic?

Answers of Question What is the purpose of a Program Epic? is To capture Agile Release Train initiatives that cannot be completed in a single Program Increment, asked in SAFe PO Certification Exam.

What is true scrum?

Scrum is a process framework used to manage product development and other knowledge work. Scrum is empirical in that it provides a means for teams to establish a hypothesis of how they think something works, try it out, reflect on the experience, and make the appropriate adjustments.

What is the main concern of having too much preparation for PI planning?

Over-preparation will leave the teams wondering why they have had two days of their lives stolen to listen to other people present their work and their plans, and to tell them what they have already committed the ’empowered’ teams to deliver.

What is the role of the release train engineer?

The Release Train Engineer (RTE) is a servant leader and coach for the Agile Release Train (ART). The RTE’s major responsibilities are to facilitate the ART events and processes and assist the teams in delivering value. … That responsibility falls to the RTE, who operate most effectively as servant leaders.

What is the basis for most team conflicts?

• Conflict often arises when team members focus on personal (emotional) issues rather than work (substantive) issues. …
• Competition over resources, such as information, money, supplies or access to technology, can also cause conflict.

What is Agile system?

Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. Instead of betting everything on a “big bang” launch, an agile team delivers work in small, but consumable, increments.

What is the key purpose of DevOps?

DevOps is a mindset, a culture, and a set of technical practices. It provides communication, integration, automation, and close cooperation among all the people needed to plan, develop, test, deploy, release, and maintain a Solution.

What is Pi in Devops?

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.

Who defines Definition of done?

The Scrum Team owns the Definition of Done, and it is shared between the Development Team and the Product Owner. Only the Development Team are in a position to define it, because it asserts the quality of the work that *they* must perform.

Who create Definition of done?

In the 2020 Scrum Guide, the Definition of Done is created by the Scrum Team. In previous versions of the Scrum Guide, this responsibility was explicitly owned by the Development Team.

What is done done in agile?

A term often used by teams to mean the work performed during the sprint is “really” done. Teams that use “done-done” often use the term done to mean “we did as much work as we were prepared to do!” Well-functioning agile teams don’t need two concepts (done and done-done). …

Who should write pi objectives?

As the business owners assign business value to the Team PI objective(s), the business owner and product manager describe the strategy and context of the business intent. The team uses this crucial information as they work toward delivering the PI objective.

What are two purposes of the system demo?

A system demo is a critical event. It’s the method for assessing the Solution’s current state and gathering immediate, Agile Release Train-level feedback from the people doing the work, as well as critical feedback from Business Owners, sponsors, stakeholders, and customers.