MIP Executive Steering Committee - OpsCo Summary Report

DELIVERY TEAMS AVBOB IMPLEMENTATION FRAMEWORK Date: 05 May 2026.

[Audio] Today, we will be discussing the key components of our AVBOB Implementation Framework and how it will guide our delivery teams towards a successful and seamless execution. The vision for our implementation framework is to have seven parallel streams operating as one cohesive team, guided by shared governing principles. This will not only ensure excellence in our delivery, but also mitigate risks that come with large-scale enterprise implementations. Let's dive into the four governing pillars of our framework. Firstly, the Governance Architecture has a five-tier operational model for decision making, reporting, and escalations. This will ensure efficient communication and alignment across all teams. Next, the Agile Delivery Framework follows a scaled Scrum approach with strict scope control. This allows us to adapt to changes and deliver results in a timely manner. Additionally, we have Finance and cross-stream dependency management in place to ensure smooth financial management and coordination. Our third pillar is Execution and Deployment Cadence, which includes synchronized 2-week sprints and Big Data in-person days, along with automated pipelines. This approach helps us stay on track and quickly address any issues. Finally, we have Accountability and Roles as our fourth pillar. This involves clear role delineation, escalation matrices, and framework activation to ensure that everyone knows their responsibilities and can escalate any issues in a timely manner. With these key components in place, we are confident in our ability to successfully implement and deliver excellence for our organization. Please stay tuned for the rest of our presentation..

[Audio] Delivery Teams are essential for the success of the AVBOB Implementation Framework. They play a crucial role in our implementation strategy and are at the heart of our governance stack. At the base of our governance stack, there are 7 delivery teams or streams, each with a specific focus on executing tasks and developing software. These teams handle various aspects of the implementation, including ILR, GLR, FMS, finance, migration, big data, and research and innovation. On a daily basis, they work diligently to complete their assigned tasks and contribute to the overall success of the implementation. They follow a structured approach with detailed to-do lists and efficient software development practices to ensure timely and accurate delivery. Above the delivery teams, there is the Scrum of Scrums (SoS), which is a cross-stream coordination layer that meets twice a week. This team is responsible for aligning the efforts of the different delivery teams and ensuring a smooth and conflict-free work process. They also maintain a Master SoS sheet and oversee the Change Control Board, which evaluates and approves any changes to the project plan or scope. The Project Management Office (PMO) is a crucial layer in our governance stack and meets weekly. They are responsible for maintaining project plans, risk and issue logs, and standardized reporting suites. The PMO closely monitors the progress of the implementation and quickly addresses any issues or risks that arise. With their expertise and attention to detail, they ensure that the project stays on track and meets its objectives. The OpsCo layer, which meets weekly, is responsible for making operational decisions, aligning performance, and evaluating the scope of the implementation. They play a critical role in ensuring that all aspects of the project are running smoothly and achieving the desired outcomes. Lastly, at the top of our governance stack, is the Steering Committee (SteerCo) which meets monthly. This committee includes individuals who oversee and guide the overall implementation process..

[Audio] We will now discuss the team coordination model implemented at AVBOB to ensure delivery team success. At the top, SteerCo and Executive Oversight make strategic decisions and serve as final escalation points. Below that, the PMO and Reporting maintain project plans and standardized reporting. The Scrum of Scrums (SoS) coordinates with all delivery teams to identify and manage dependencies and operate the Change Control Board. Each Delivery Lead reports to the SoS for efficient escalation. Our 7 streams - FMS, ILR, GLR, FINANCE, MIGRATION, BIG DATA, and R&I - operate on synchronized 2-week sprint cycles to promote collaboration and alignment. Coordination also exists within each stream, such as between Funeral Management, Individual Life & Risk, and Group Life & Risk, for a holistic approach. Overall, our key principle is synchronization and alignment across streams for a seamless implementation. Let's now move on to discussing the specifics of our delivery teams..

[Audio] Slide number five will cover the AGILE CEREMONIES AND RULES OF ENGAGEMENT in the AVBOB implementation framework. These are essential for a successful implementation. Our teams must align during the sprint, with the Scrum of Scrums (SoS) coordinating deliverables and resolving cross-team dependencies and blockers. We will have a 2-week synchronized sprint cycle, with meetings twice a week and daily meetings during the sprint. The delivery teams will focus on one functional area at a time. Our integration sprints will bring all 7 project streams together, allowing us to track dependencies and address them promptly. Only a maximum of 2 areas will work in parallel if they logically integrate. Our sprint commitment is a strict deadline, with any changes needing approval from the Change Control Board led by the SoS. The Master SoS Sheet will be used to ensure project health and tracking. Public holidays may affect capacity, but end dates will not be shifted. All scope changes and architectural decisions will require written approval and will be logged in the PMO RAID log. Delivery Leads and Scrum Masters will attend the ceremonies as ambassadors to keep everyone informed and accountable. Let's work together to successfully implement AVBOB by following these ceremonies and rules of engagement..

[Audio] Today, we will discuss the operating model and location for our AVBOB implementation framework. Our implementation date is May 05, 2026, and a clear plan is crucial for our delivery teams. We will have in-person days every Wednesday for all teams to come together and foster a sense of camaraderie and alignment. On other days, we will have a hybrid model with a mix of working from home collaboration days and remote days for deep work and daily execution, ensuring a balance between focused development time and collaboration. On Wednesdays, we will have sprint close and kick-off meetings for 30 minutes per team in the morning, followed by a sprint review lasting 2-4 hours in the afternoon. We will also have daily stand-ups using Jira to address any impediments and ensure progress. Additionally, on the 6th Wednesday of each sprint, we will have a mid-sprint sync and half-sprint check-in, including product backlog refinement and cross-pollination with big data resources. Our 10th day of each sprint will consist of a sprint wrap-up and polish at our MIP offices, including virtual participation from our Cape Town and remote staff for all in-person ceremonies, such as testing, integration, and showcase preparation. We have chosen this hybrid model for the benefits of in-person days in promoting camaraderie and alignment, while remote days allow for focused development time. Thank you for your attention and let's continue working together for a successful AVBOB implementation. See you on the next slide.".

[Audio] Slide number 7 of the AVBOB Implementation Framework presentation will focus on the important steps leading up to our official kickoff on Wednesday, June 3rd, 2026. The delivery teams have been diligently preparing for this day and will have their preparations kickoff meetings on Monday, June 1st. The following day, Tuesday, June 2nd, marks the start of our sprint. During this time, the teams will finalize their setup and alignment with the AVBOB Implementation Framework and be introduced to each other. Additionally, the Jira setup will be finalized, and the definition of ready and done has been formalized. Our backlog has also been groomed and prioritized for execution to ensure alignment and readiness among the teams. By the end of the first day, the master SoS sheet will be activated and our key milestone confirmed, with all seven streams operating on a synchronized two-week cadence. Each team will have completed their sprint planning and committed to a sprint goal. They will also have a prioritized set of product backlog items ready for execution. This milestone marks our readiness to officially begin on Wednesday, June 3rd. We appreciate the hard work and dedication of our delivery teams and are confident that with our framework in place, we will achieve success in our implementation. The remaining slides will continue to delve into the specifics of the AVBOB Implementation Framework..

[Audio] As we implement the AVBOB framework, we have established a reporting and performance structure. This will bring transparency to our progress, blockers, and any changes to the scope. Our reporting chain includes the MIP and AVBOB executives, as well as a global roll-up, to ensure clear communication and alignment throughout the organization. Additionally, we have implemented a SCRUM OF SCRUMS (SoS) structure to facilitate collaboration and coordination between our delivery teams. This includes regular sprint forecasting, retrospective notes, progress tracking, and quality assurance testing. Every day, we will provide a comprehensive Scrum Report and Master SoS Sheet detailing our sprint health, progress metrics, and potential blockers. This will allow us to continuously monitor our sprint stats, predicted vs. actual burndown, and backlog changes. At the end of each sprint, we will review a Backlog Report to gain a clear understanding of the backlog size, blocked items, and pending estimations. Our reporting and performance structure will serve as a central coordination and aggregation point, enabling us to effectively manage and track the progress of the AVBOB implementation framework. Let's continue to work together towards our goal..

[Audio] In preparation for the official start date of June 3rd, each delivery lead should have a clear call to action and ensure that their teams are prepared for Sprint 1. This includes completing tasks such as confirming team roster and capacity, grooming the backlog, and ensuring access and configuration of Jira boards. It is also important to communicate any blockers or dependencies early on. All streams should be ready for Sprint Planning on June 3rd. Additionally, an initial velocity estimate and draft of the sprint goal should be prepared. Teams should also be briefed on the schedule and locations for in-person or remote work. Thank you all for your dedication to this project. Let's continue to work together for a successful implementation of the AVBOB framework..

[Audio] Ladies and gentlemen, we have now reached the final slide of our presentation. The tenth slide discusses the implementation framework for AVBOB, which is dated May 05, 2026. This framework outlines the key steps and processes that will be followed for a successful execution of our project. As we approach the kickoff date of June 01, 2026, it is crucial to have a clear understanding of the implementation framework. We have carefully selected the delivery teams that will be responsible for the different aspects of the implementation process. These teams have been chosen based on their expertise and experience, and we have full confidence in their ability to play a crucial role in the successful implementation of AVBOB. We would like to remind you that on the kickoff date of June 01, 2026, we will be hosting a Q&A session. This will be an opportunity for you to address any queries or concerns you may have regarding the project. Your feedback and involvement are highly valued, and we look forward to your active participation. Thank you for your time and attention throughout this presentation. We appreciate your support and are excited to work together towards achieving our goals. We will be available for a Q&A session on the kickoff date of June 01, 2026, and we hope to see you there. Thank you..