Here is something that surprises people. The project manager running a cloud migration barely touches the cloud. You would think the person leading the move to Azure or AWS would be deep in the technology. They are not. The engineers handle that, and the PM is managing something else entirely.
A cloud migration almost never fails because the technology did not work. It fails because something moved before the thing it depended on, because nobody planned for what happens at two in the morning when a move goes wrong, or because the team that owns a critical system was never brought along. Every one of those is a project management problem.
In this video, I cover:
- The one question the PM owns at every step of a migration
- Phase 1: discovery, and why an undiscovered dependency is what hurts you later
- Phase 2: wave sequencing, maintenance windows, and rollback plans
- Phase 3: the cutover call and the go/no-go decision
- Phase 4: hypercare, and why the promised savings live in the decommission step
- The nightly job that failed an hour from done, and the rollback we called anyway
Ready to close the Experience Gap? Join The Eddie System and gain real PM experience inside a live PMO environment.
Want the full breakdown? Read the complete article →
Ready to gain real PM experience?
Infrastructure work is learned by running it. Inside The Eddie System you work through governed IT projects in a live PMO environment and make the calls yourself.
