Virtual PI Planning
Amidst the increasing number of confirmed Coronavirus cases, several organizations are mandating their colleagues to work from home. In such times, Release Train Engineers (RTEs) and Scrum Masters (SM) are searching for creative ways to execute virtual PI planning. This article provides valuable insights into conducting the event effectively. With this post, you will also understand different options available readily to you for creating an online Program Board. Below is the list of activities that an RTE must consider when conducting a virtual PI planning.
First, communicate the tool that everyone must use to attend the virtual event - WebEx, Skype, etc. My organization uses WebEx, thus I have consolidated some WebEx guidelines/resources that are useful.
Primary WebEx details should be shared with everyone prior to the event. This WebEx room must be open during the entire event and will act as the common forum to ask questions and collaborate across teams as needed.
WebEx details for additional/secondary rooms should also be published prior to the event. These WebEx rooms are required to facilitate team breakouts. There should be a separate WebEx room for each team.
Ensure that the primary and secondary WebEx rooms are different.
- If you are sharing your screen during a WebEx meeting, it is often challenging to take notes. Thus, I recommend that you designate scribes for managing parking lot items, capturing risks or dependencies, etc.
- Pre-PI planning Preparation: The more the preparation prior to the PI planning event, the better or smoother the virtual event will go. Here are a few things to remember:
Ensure that prioritized product features are created and refined at least 3 weeks prior to PI planning.
Bring team break-outs forward. During the breakout sessions, teams estimate their capacity for each iteration, identify risks and dependencies, refine user stories, and create their draft plan for each iteration. All these activities can be planned prior to the PI planning event. As a result, during PI planning, the time needed for team breakouts will be reduced.
Please Note: For the pre-PI planning preparation to be successful, Scrum Masters must plan team capacity for these activities.
- Next is to set-up a virtual Program Board. Based on my research, there are multiple options available to you:
Use Miro: You can use the free version without any issues. However, if this is not an approved product within your organization, you may not be able to leverage this product. I recommend that you consult with your leaders before going ahead with this option.
- If you use Rally, JIRA, or any other agile management tool to track features/user stories, you may explore if there’s a custom board/view available within the tool itself. This will minimize your post-PI planning effort to manually migrate team dependencies, risks, and milestones into the tool.
- Use Confluence. You can build a custom view using the Gliffy Diagram and build the Program Board on Confluence. You can also share the confluence link ahead of time so teams can leverage the same during team breakouts.
Check out my published books on Agile and Lean:
You may also be interested in these articles...
- Leadership Agility: What You Need to Know
- Will OKRs Rule the World?
- Enterprise Agility - Expectations Vs Reality
- Agile and Lean Methodologies - Same or Different?
- Expert Agile Tips and Techniques
- Scrum and Kanban: Same or Different? Which one is better?
- How to Measure Kanban Throughput?
- What are the 12 Agile Principles? Learn, Apply, and Be Agile!
- What is a Sprint Burndown Chart? - Agile Scrum Framework
- Differences between Waterfall and Agile
- 5 Habits that Successful Leaders Have
- 7 Traits of High-Performing People