With such a large programme to deliver, it was essential that the delivery was based on some core principles and structures that would drive the progress to reach the ambitious goals of the programme.
- Building a culture of one programme across all the organisations and people involved in delivery.
- A programme structure and method that emphasised pace and quality of delivery.
- A governance approach that that put business leaders at the heart of the decision making within the programme.
Programme Culture
Early on, it was a very conscious choice to ensure that there was no blame culture. Transformation on this scale relies on pace and decisive decisions and everyone was empowered to make decisions knowing they would be supported if any rework was needed.
The Darwin Programme was allocated a dedicated office suite at the Telenet HQ in Mechelen from which to execute the programme. By co-locating the core team in a fresh and Darwin-branded environment, the leadership was able to drive a strong programme identity and sense of belonging, regardless of the company name on everyone’s badge.
Programme structure and method
The programme utilised a high degree of parallel activity across each of the three phases:
1. Blueprinting – requirements definition and solutioning. Teams worked in 8-week sprints to complete the detailed designs for tranches of scope which were then passed into the Development Teams. All the Blueprinting effort was led by business product owners with the relevant Analysts and Solution Architects working within their teams. These streams covered key underlying business processes e.g. Lead to Order, Order to Bill, Bill to Cash, Billing and Product Modelling. Darwin Blueprinting has generated 1550 Epics and 6486 IT User Stories.
‘This business-led approach was key to securing, and maintaining, business buy-in over the sustained period required to deliver such a complex transformation as Darwin.’
2. Development – at the end of each Blueprinting sprint the designs were passed to the Development Teams. They completed their Unit and Integration Testing, and code was then deployed to Production in integrated release packages every 12 weeks.
3. System Integration Testing (SIT)/ Business Acceptance Testing (BAT) and Deployment into operation – E2E testing was completed across the Origin by validating E2E business flows covering the full scope of BASE & Telenet’s services. SIT was completed by a dedicated Test Team, BAT was completed by ‘Darwineers,’ people seconded from the business operations teams who brought real world experience. The SIT Team executed over 90k Test Cases and raised over 22,500k bugs.
Governance and programme leadership
Running such a complex, multi-year, geographically dispersed Transformation Programme as Darwin required strong governance. A strong programme leadership model was embedded in Darwin from the outset based on an overarching Steering Group for the Programme, and contributory IT/ Technology & Business Change governance boards.
The business was fully embedded in Darwin along with IT from day one. A dedicated Business Change workstream was a core part of the Programme Delivery Team, focused on driving the requirements and solutioning, and to prepare the organisation for the changes that Darwin was delivering. Business Change drove key elements such as Business Acceptance Testing (BAT) for each release, Friendly User Trials with real customers, and defect prioritisation based on customer/ channels impact.
The Origin Launch Group (OLG) was formed as the first ‘Go-live’ approached and remained in place. It became a key weekly forum bringing together senior leaders from across the Commercial Business, Channels, Back Office Operations, IT, and the Darwin Programme, to provide direction and steering.
‘The decision to initiate Darwin was a decision that the whole Telenet SLT made together. This support from the top, and continued engagement throughout the duration of the Programme has been the critical success factor.’