· Be sure that the team reviewed features and enablers before bringing them to PI Planning
· Involve product owners and team by preparing backlogs
· Don’t go too much into the details
· Use timebox
· Use backlog board as a starting point
· Highlight the features which are in planning or already planned
· Use program board and backlog board as a Single Source of Truth
· Have a separate chat open to be able to talk to teams
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.
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.