· Be well prepared, make sure you agree on working agreement
· Thing about right channels: turn on your video camera, put a chat on etc.
· Replace the physical and program board with a digital board
· Work on small batches
· Plan features one by one
· Visualize progress
· Don’t forget about the dependencies, solve them as soon as possible
· Have a working agreement
· Be prepared to present your plan
Hi everyone, welcome back to Remote PI Planning in the shoes of a Team. I hope your RTE did a great job and created an amazing stage for you to be able to focus on planning the next Program Increment. As a Team make sure you've prepared yourself and agreed on a few working agreements helping you being effective. I recommend to have three permanent channels open.
Avoid to plan multiple Features or Enablers at the same time. Work on small batches. Planning Features one by one will keep you focused and allows you to work with short feedback loops. Being able to visualize a planed Feature already after 1 hour team breakout session shows progress and minimizes risks.
During planning, don't forget about dependencies. The ones you have, but also the ones you may get from other teams. Based on the overarching Program Backlog priorities, solve Dependencies as soon as possible. If the Feature from another team has higher priority, you should focus on solving that dependency first. Afterwards you can move on with the Features YOU have pulled from the Backlog Board.
Make sure you're having working agreements which trigger the conversations you need. A good practice is definitely to use digital stickers. For instance... raising a blue question mark triggers Product Management, as you have questions regarding content. Raising a red exclamation mark shows, that you're facing an impediment. All participants should speak the same visualization language to avoid confusion.
I'd like to add a few words about Draft and Final Plan Review. This stage is yours! Be prepared to present your plan to all participants. And I mean to all. I’ve often seen the Draft Plan and Final Plan Review used as kind of Status Reporting towards Product Management and Business Owners. That’s not the main purpose of a Plan Review. To get alignment across the whole ART presenting your plan to other teams is as important as presenting it to Business Owners.
Going into a Remote PI Planning is a totally new experience. Not everything will work perfect. Be open, honest and support your Scrum Master and Release Train Engineer to continuously improve your Remote PI Plannings.
We will take a look at all the well-known roles - RTE, Scrum Master, Team Member, Product Management, System Architect, Product Owner and Business Owner - in PI Planning and see how they can best prepare to make remote PI Planning successful.
Intermediate / Advanced
CEO & Founder PEDCO AG, Chief Methodologist Applied SAFe
Creator of the product Applied SAFe. Started to program for money at the age of 14. Ex-professional sportsman with a passion for software and a knack in engineering. 30+ years working experience with 50+ publications. SAFe SPC since 2011, Agile (XP) since 1999. Happy father and married to a wonderful woman.
Head of Product, SPC5
Silvio is a certified SAFe® Program Consultant and as Head of Product at Rentouch responsible for the innovation of piplanning.io.
Business and Agile Leadership Coach
Shane is a business focused change agent, specialising in enterprise level digital Lean/Agile transformations. More than 17 years consulting experience across a variety of industries from pharma to banking Shane is a specialist when it comes to context and culture-specific transformations.
Ian J Franks
SAFe® 5 Program Consultant & RTE
Ian has a deep knowledge of Scrum, Kanban and Scaled Agile, and 30 years’ experience in international IT Transformation Programs. He is a successful PO, SM & RTE and as a Consultant/Trainer he coaches his clients develop a strong Agile Mindset that delivers real change and measurable improvements.