Clarifying requirements and scope
Aligning business expectations, technical impacts and priorities jointly.
Case study · Platform migration
Steering migration and go-live without interrupting operations.
Bringing together business requirements, technical delivery, testing and rollout planning in a telecommunications project.
RoleIT project manager
EnvironmentTelecommunications
FocusMigration, testing and go-live
ClientO₂ Telefónica
Starting point and challenge.
A platform migration combines business requirements with technical dependencies and a tight rollout window. Ongoing operations must not be affected.
Consistent alignment between the business unit, development and other parties involved was decisive, as was robust preparation of the rollout.
My responsibility.
I steered the migration as project manager and coordinated requirements, delivery, testing, open dependencies and the preparation of the go-live.
Steering migration and testing
Tracking progress, defects, dependencies and acceptance criteria transparently.
Safeguarding the go-live
Preparing rollout, responsibilities and response paths for the production start.
Contribution and outcome
Successful go-live without downtime.
The migration was introduced successfully without interrupting ongoing operations. The decisive factors were consistent alignment and the joint control of business requirements, technology, testing and rollout.
Are you facing a comparable initiative?
If a migration is due without an available maintenance window: describe the system landscape, the time window and the project phase. You will get an assessment of how to approach it.
Discuss your project