# Step Description Who

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

# Step Description Who

1 Outline Business Goals Outline the business goals and capabilities that Executive Team
should be in place once a migration to the Business Team
cloud is complete. Technology Team
Note: A typical migration takes place in
phases, so start by listing all goals and
capabilities, and later work to prioritize/assign
to phases.
2 Perform Infrastructure Assess the state of the corporate infrastructure. Business Team
Assessment This includes an inventory of hardware, Technology Team
software, etc., and an understanding of the
cloud-relevant skill sets in place at your
organization.
3 Evaluate Results Once steps 1 and 2 are complete, set up a Executive Team
meeting with all participants to review and Business Team
evaluate the results. Technology Team

4 Define Project Define the scope of the project to begin Executive Team
moving to the cloud. This includes features and Business Team
functionality, high-level steps, timeline, and Technology Team
budget.
5 Develop Project Plan In this step, a detailed project plan is Business Team
developed. This includes the Technology Team
features/applications/databases to be
implanted in the cloud, and the steps to Reviewed by:
develop/migrate/implement. This also includes Executive Team
developing a post-production support process.
6 Build Baseline Cloud Implement the initial non-production version of
the cloud with a limited set of features and
small set of users. Review with all teams to
ensure that what is being implemented matches
the overall vision.
Note: This is the step in which to implement key
features such as hybrid cloud functionality,
device enablement, etc.
7 Develop and Test This is an iterative step during which
applications, databases, etc. slated for
Cloud Readiness Checklist

implementation in the cloud are


developed/upgraded and tested.
8 Go Live Once testing has completed, applications,
databases, and features and switched on in
production. There can be an iterative
approach versus turning on everything at once.
9 Implement Post-Go-Live Plan Once the cloud is live, the post-production
support plan is implemented.
10 Hold Post-Go-Live Reviews For a period of time after the cloud systems go
live (usually 2 or more months), post-go-live
review meetings are held with all teams to
address issues and plan upcoming
enhancements.

Page 1

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy