Cloud Migration Project Language
5 exercises — master the project management vocabulary of cloud migrations: sponsors, hypercare periods, go-live, success criteria, the migration factory model, and common budget risk vocabulary.
0 / 5 completed
Cloud migration project vocabulary quick reference
- Migration sponsor — executive who provides air cover, budget protection, and escalation authority
- Air cover — executive advocacy that shields the project from competing priorities and organisational resistance
- Go-live — the cutover moment when production traffic switches to the cloud environment
- Hypercare period — intensive support window (2–4 weeks) immediately after go-live
- Steady state — normal operations phase; migration team hands off to standard ops team
- Migration success criteria — objective, measurable definition of when a migration is complete
- Migration factory — standardised, repeatable, automated approach for migrating many workloads at scale
- Shadow work — unplanned effort discovered mid-migration (undocumented deps, security debt, licensing issues)
1 / 5
A CTO presents the cloud migration project structure to the board. She introduces the key roles: "Our migration sponsor is the CFO, providing executive air cover. The migration team is led by our Cloud Programme Manager." What does the term "executive air cover" mean in a project management context?
"Executive air cover" is one of the most important — and most commonly cited — success factors in large cloud migration projects.
What the migration sponsor provides:
① Organisational authority — can mandate that other business units cooperate (share resources, provide access, deprioritise conflicting work)
② Budget protection — ensures the migration budget is not reallocated mid-project during financial reviews
③ Escalation path — when the migration team encounters a blocker involving another VP's team, the sponsor can escalate peer-to-peer at the executive level
④ Strategic endorsement — signals to the entire organisation that this initiative is a priority
Why migrations fail without it:
Cloud migrations touch every department — infrastructure, security, compliance, finance, and application teams. Without a sponsor who can override competing priorities, migration timelines slip as each team deprioritises migration work in favour of their own roadmap.
Key vocabulary:
• Migration sponsor — the executive accountable for the migration programme's success (typically CTO, CIO, or CFO)
• Air cover — executive protection and advocacy for a project or team facing organisational headwinds
• Programme governance — the formal decision-making structure for the migration (steering committee, RACI, escalation paths)
What the migration sponsor provides:
① Organisational authority — can mandate that other business units cooperate (share resources, provide access, deprioritise conflicting work)
② Budget protection — ensures the migration budget is not reallocated mid-project during financial reviews
③ Escalation path — when the migration team encounters a blocker involving another VP's team, the sponsor can escalate peer-to-peer at the executive level
④ Strategic endorsement — signals to the entire organisation that this initiative is a priority
Why migrations fail without it:
Cloud migrations touch every department — infrastructure, security, compliance, finance, and application teams. Without a sponsor who can override competing priorities, migration timelines slip as each team deprioritises migration work in favour of their own roadmap.
Key vocabulary:
• Migration sponsor — the executive accountable for the migration programme's success (typically CTO, CIO, or CFO)
• Air cover — executive protection and advocacy for a project or team facing organisational headwinds
• Programme governance — the formal decision-making structure for the migration (steering committee, RACI, escalation paths)