Cloud Readiness Assessment. @cloud-readiness-assessment

Cloud migrations run over budget when the assessment was optimistic: hidden dependencies, licensing traps, data gravity, and workloads that should never have moved. The Cloud Readiness Assessment finds these before the migration starts. Engineers review your application portfolio, infrastructure, and operating constraints — compliance, latency, cost ceilings — and map what each workload actually needs from a cloud target.

The finish state is a readiness verdict per application — rehost, replatform, refactor, retain, or retire — and a phased roadmap that sequences the migration by risk and dependency, with the cost drivers made explicit.

Application Portfolio Review

Each in-scope application profiled: architecture, state, data, licensing, and operational load — the facts a migration decision needs.

Dependency Mapping

The dependency graph between applications, databases, integrations, and shared infrastructure, so nothing moves that breaks something left behind.

Migration Options

A disposition per workload — rehost, replatform, refactor, retain, retire — with provider considerations, cost implications, and the trade-offs of each path.

Readiness Roadmap

A phased migration sequence ordered by dependency and risk, with the gaps to close first: skills, landing zone, security controls, and operational readiness.

1. Scope — Fix the portfolio in scope, the drivers for the migration, and the constraints — compliance, budget, downtime tolerance.
2. Build — Profile the applications, map dependencies, evaluate target options, and assign a disposition per workload.
3. Handover — The readiness report and phased roadmap walked through with your infrastructure and engineering leads.

The Cloud Readiness Assessment is a menu item on the Scrums.com delivery catalog, available at every plan tier. Add it to your plan backlog and your delivery team schedules it like any other item — scoped, tracked, and reported through the SEOP. See Delivery Plan Tiers.

Do you recommend a specific cloud provider?

Only where the evidence points one way. The assessment is vendor-neutral: it evaluates AWS, Azure, GCP, and hybrid options against your workloads and constraints, and says when the choice genuinely does not matter.

Does this include performing the migration?

No. The assessment produces the verdict and roadmap. The migration itself lands through your delivery plan as its own scoped items — sized accurately, because the assessment did the discovery.

What if some systems should not move?

That is a normal outcome. The retain and retire dispositions are as valuable as the migrations — they stop spend on moves that would never have paid back. Legacy candidates often route into the Modernization Roadmap Sprint instead.