RTE Responsibilities: Part - 3

RTE Responsibilities: Part 1

RTE Responsibilities: Part 2

….Continued from RTE Responsibilities: Part 2

Now come the tasks those needs to be taken care after the PI Planning ceremony.

Post PI Planning Tasks

Some of these tasks needs to be executed right after the PI Planning ceremony and few of the tasks/follow-ups can be done next morning or during the course of Iteration (Sprint) 1.

• RTE to collect/capture PI objectives from all the teams to derive ART level PI objectives and communicate to the stakeholders.
• Capturing the Program board details and sharing it with the remote teams at the same time moving the physical Program board near team’s area so that team can update the board throughout the PI Execution period.
• Follow-up items including risks & dependencies those are to be discussed later are well documented and followed-up post PI planning to take it to the closer
• Sending invites for Program level ceremonies like – Scrum-of-Scrum, ART Sync, Inspect & Adapt, PI System demo etc.
• Finally cleaning up the mess in the facility (Removing post-its from wall, removing charts, cleaning up whiteboards etc.)

If you just consider this ceremony (PI Planning) alone, the degree of coordination and support a RTE would require to ensure that PI Planning goes smoothly is humongous! This efforts grows multifold when PI Planning happens at multiple locations.

Okay, I understand that in ideal world, all the stakeholders/teams should gather in one facility for a successful PI Planning, however many times bringing all stakeholder together might not be possible because of certain logistical/financial constraints. During such times, RTE can identify and appoint a Proxy RTE at each location to ensure that events of PI planning goes smooth.

Both RTE and RTE-Proxy should have good understanding and should be in sync with each other in coordinating and facilitating PI Planning events. For example, there should be common understanding of how artifacts will be share across multiple locations;  or how to involve remote teams in breakout discussions (Video conference, Conference Bridge, confluence/JIRA, emailing etc.) or how the vote of confidence would be collected or PI retro points would be communicated etc.

At the end of it, one has to understand that big ceremonies like PI Planning would evolve and get better over time as we focus and put deliberated efforts in improving on the "lessons learnt" a.k.a "improvement areas" and "good practice to be continued" identified during PI retro.