How to do PI Planning in real life

Clarify prerequisites for effective Pi planning, define Pi, agile team, and agile release train, outline trainings, features, stories, Jira whiteboard, and stakeholder engagement.

Pi, previously known as program increment, is a planning interval of 8–12 weeks. Create a pi calendar, plan the year, and establish a collaboration channel to align stakeholders.

Describe agile teams as cross-functional units of developers and testers with a product owner and a Scrum Master, empowered to decide within a 12-or-fewer member limit, using short sprints.

Explore how an agile release train coordinates multiple teams to deliver value, guided by roles like the release train engineer, product management, system architect, and business owners during PI planning.

Learn essential trainings for agile roles in Scaled Agile Framework, from scrum masters and teams to product owners, architects, and business agility leaders, with recommended Scrum Guide.

Define a feature as an independent delivery component aligned to business objectives, tracked in Jira through funnel, analysis, ready for PI planning, in dev and test, deploy, and release.

A story is a small piece of functionality deliverable within a week that fits in a sprint and is managed in the product backlog, moving through todo and in-progress stages.

Explore the basics of agile planning tools—zero for issue tracking, Jira for backlog and sprint planning, and Miro for collaborative whiteboarding—with practical references and upcoming Jira configuration content.

Identify and invite key stakeholders for PI planning, and confirm 1-to-1 participation with executives, architects, and security teams. Use risk rolling and confidence voting to address blockers and guide planning.

Clarify prerequisites for effective Pi planning, define Pi, explain agile teams and art and their sizes, outline trainings for participants, and identify and engage stakeholders through features and stories.

Prepare for PI planning by identifying a suitable venue, planning capacity, assembling required content, assigning responsibilities, socializing materials at the right time, and crafting a practical PI planning agenda.

Structure Pi planning across single to multiple time zones with one to four days, covering vision, team breakout, dependency planning, plan review, risk roaming, confidence voting, and retrospective.

Learn to calculate team capacity in agile projects by counting working days, adjusting for leaves and holidays, allocating 70–80% for delivery and 20–30% for admin, and excluding IP iteration.

Identify participants and locations for PI planning and determine remote or in-person attendance. Prepare the venue with Wi‑Fi, screens, seating, and refreshments, and set up video conferencing for hybrid planning.

Content readiness aligns features and stories with acceptance criteria and stakeholder input before pi planning, while two parallel streams, execution and preparation, guide teams and clear impediments.

Content socialization guides agile teams through features and stories before Pi planning, enabling sizing, dependency identification, backlog alignment, and prioritization.

Prepare for PI planning by identifying venue needs and gaps, mastering capacity planning, and ensuring content readiness; socialize content with participants to shape an agenda aligned with team distribution.

Prepare pi planning content and select tools to ensure board readiness; explore Jira Kanban stages, compare agile tools like Azure DevOps, and outline whiteboard components and available resources.

Explore Jira readiness for pi planning by configuring art, establishing aligned art and team backlogs with features and stories, and prioritizing with product managers and product owners aligned with stakeholders.

Prepare the PI planning board ahead of day one by aligning iterations, dependencies, risks, and objectives, and ensure capacity and backlog for the three-day agenda.

Learn to set up your Pi planning board using JIRA or agile project management tools, from event calendar and agenda to team level boards and the Pi planning retrospective.

Explore the key parts of Pi planning day, from the vision section to team breakout and confidence voting, and learn a simple way to run your Pi planning retrospective.

Kick off pi planning with a three-day example across time zones, using the pi planning board's sections—vision, guidance, team planning, art objectives, confidence voting, and retrospective.

Day one outlines the two-hour vision day of PI planning, delivered online or remote, with time-boxed sessions covering introduction to PI planning, exec vision, product vision, and architecture vision.

Explore day two of pi planning as teams map roles, plan iterations, manage dependencies and risks, and define pi objectives on team and art boards.

This lecture covers the final pi planning retrospective, using start-stop-continue with color coded sticky notes and three votes per participant to build a next-step action plan.

Learn how to run a Pi planning day and tailor it to your needs, organization dynamics, and the product or services you deliver. Gain in-depth knowledge of breakout guidance, dependency planning, risk roaming, exercises, confidence voting, executive support, objective building, and engaging retrospectives that contribute to your organization's strategic objectives.

Learn the key roles and responsibilities in Pi planning, including agile teams, Scrum Master, Release Train Engineer, product owners and managers, business owners, exec support, and stakeholders.

The release train engineer leads and facilitates the pr planning as a servant leader, coordinating venue, content, tool readiness, and coaching product managers, owners, and scrum masters to align stories.

Scrum masters serve as team level coaches, ensuring story readiness and a PI planning board, planning capacity including leave, managing dependencies and roaming exercises, and escalating items to ART level.

Product managers align art vision with business objectives, prepare the art backlog on time, prioritize features, and coordinate with business owners, executives, architects, and security teams to manage dependencies.

Drive readiness of the team backlog, prioritize stories with product managers and business owners, manage dependencies, and collaborate with architects to align architecture and clear impediments.

Architects define the architecture and technical roadmap to enable business and product vision, guide teams, support planning and estimation, resolve impediments, and manage technical risk at team and art level.

Define and align agile team objectives within art, estimate and plan features and stories, manage capacity and dependencies, raise risks and training needs, and participate in pi planning confidence voting.

Business owners articulate the business context and goals, align product management with priorities, review features and stories, and support risk management and confidence voting during PI planning.

Executives participate in PI planning to ensure strategic alignment, empower teams, product management, and the Scrum Master, review team plans and ART objectives, and support ART risk and confidence voting.

Engage stakeholders in PI planning, including security analysts, to ensure alignment with security guidelines, review plans, manage dependencies, address deviations, and participate in risk roaming exercise and confidence voting exercise.

Identify the roles and responsibilities of every participant in PI planning and show how each contributes from preparation through team breakout, dependency planning, risk roaming, exercises, and objective building.