This lesson is about Remote PI Planning in the shoes of Product Management and System Architects. I bundled the roles of Product Management and System Architecture together. The simple reason, participating a Remote PI Planning, System Architects tackle the same challenges as Product Management.

First of all, every Features and Enabler you want to bring into the PI Planning have to be reviewed by the teams who are most likely the ones who will going to plan and execute it. Questions not asked before the PI Planning, will come up during the PI Planning. Spend a reasonable amount of time preparing the Backlog, involving Product Owners and teams. Use the time box at the beginning of the PI Planning to remind all participants about why and what Features they are going to plan. You shouldn't need to go into much detail, as the Features have already be reviewed by the teams and agreed as ready.

Use a what I call Backlog Board as starting point. It's not only going to support you presenting your Top10 Features. It also helps to keep a progress overview during PI Planning. Highlight those Features which are in planning or already planed. Use the Backlog Board and Program Board as single source of truth. What's not visualized on the Program Board is not planed and therefore no team will ever give its commitment to it. Be ready to get triggered by the teams and avoid to disturb them all the time. I suggest to have a separate chat open including all Product Owners to get into close on demand conversations with them whenever the teams need you. If a team needs your support, they will raise a visual indicator or you'll read about it in the chat. From what I've seen, that's the most effective way to support the teams as Product Manager or System Architect.

‍