Skip to main content
Enterprise Agile Planning icon with arrows
Last Updated May 07, 2020 — Enterprise Agile Planning expert

Remote PI Planning: Day One and Two

Enterprise Agile Planning

Last week, we published the first installment of our Remote PI Planning blog series in which we discussed virtual environment, organizational, and information collection readiness for Pre-PI planning. In this week’s blog, we continue the conversation by explaining day one and two of Remote PI Planning. We have also put together a step-by-step checklist that shows how easy and intuitive it is to create a draft PI plan in VersionOne. If you would like to learn about the entire PI Planning process, please download the Enterprise Guide to Remote PI Planning for a comprehensive overview.

Remote PI Planning Agenda

Scaled Agile, Inc. recommends extending the PI Planning agenda from two to three days for virtual events to maintain team focus.

Day One of PI Planning

A significant portion of the first day is spent providing the right context and explaining the big picture to teams. Make sure you schedule the executive briefing meetings at a time when teams across time zones can attend. It is also recommended to shorten these meetings to 15-20 minutes with a TED-talk style format. Alternatively, you can record and send videos to teams before the event to maximize team breakout time. Also, before diving into executive briefings, dedicate some time for ice-breaker activities to help kickstart participation. Read on to learn about the different PI Planning activities on day one:

Business Context: Executives share the current state of the business, portfolio vision, and how well existing solutions are meeting customer needs. This is valuable context for teams to understand how development activities contribute to the overall strategic direction of the company. It is important to leverage chat tools or conversations in VersionOne to gather and respond to questions from the ART during context briefings.

Product/Solutions Vision: Program Management presents the vision for the business for the upcoming PI and the top ten features that will help meet these goals.

Architecture Vision & Development Practices: The Systems Architect or IT department communicates the technology strategy and roadmap that enable the portfolio to support current and future business capabilities. They may also introduce improvements to development practices such as DevOps, test automation, and CI/CD for the upcoming PI.

Planning Context and Lunch: The Release Train Engineer (RTE) explains how the PI Planning process will work, key deliverables, and expected outcomes for the meeting.

Team Breakout: During this time, teams will create a draft plan in VersionOne Team Planning Rooms. Apply filters to the Portfolio Tree, Team PI Planning, and other areas to show assigned features for your specific team.

Day Two of PI Planning

Team Breakouts: If you have teams across time zones, they can use this time on the second day of PI Planning to work on user stories and dependencies.

Draft Plan View: This is a time-boxed meeting where teams present their draft plans to business owners, product management, and other teams in the ART to get feedback. The draft plan includes their capacity and load, draft PI objectives, potential risks, dependencies, and reveal any unplanned stories that might prevent features from being fully planned in the PI.

Management Review and Problem Solving: This meeting is scheduled by the RTE with business owners and key stakeholders to discuss draft plans and address any issues that come up with architecture, dependencies, scope, and resource constraints. The main goal of this meeting is to determine the adjustments necessary to ensure a successful PI. This can sometimes result in a new set of priorities or features for teams to work on. VersionOne provides leadership with all the insights they need to understand the impact of the change they are considering, enabling them to make better decisions faster.

Planning Adjustments: During this meeting, business owners and key stakeholders share any decisions that were made in the management review meeting. If there is a new set of top ten features, they will be shared through VersionOne in the portfolio backlog tree, feature kanban board, and ART planning room.

Team Breakouts: Teams continue the planning process, making the appropriate adjustments. They will update their PI objectives so business owners can assign values to each objective and rank them for implementation.

Check out the step-by-step checklist that shows how you can use VersionOne to create a draft PI Plan. If you would like to learn more about PI Planning, we are holding a live webinar on May 19th where you ask your most pressing questions and learn best practices and recommendation for Remote PI Planning success from expert practitioners. We will share our experiences from helping companies across industries strategize and execute PI Planning in today’s work-from-home era. Register Now.

More from the Blog

View more Government Cloud
Apr 12, 2022 Government Cloud receives FedRAMP Authorization through sponsorship from the United States Department of Veterans Affairs

Enterprise Agile Planning
Flagship Agility solutions can effectively scale agile deve ...
Read More
Nov 22, 2021

What are the qualities of highly effective agile teams?

Enterprise Agile Planning
A team is the core unit of productivity in an agile organization. Wher ...
Read More
Nov 15, 2021

How an open-first attitude revolutionized government tech development

Enterprise Agile Planning
Public perception of government is often that it is slow-moving, reluc ...
Read More
cross functional
Nov 08, 2021

6 best practices for building resilient cross-functional teams

Enterprise Agile Planning
Agile frameworks prize the quality of resilience within every facet of ...
Read More
Contact Us