Slide 1: Risk Identification 

- In this slide, you will create a Risk Breakdown Structure (RBS) to include all the key risks of
your project. You can use the template in Video 4 or create your own.

Datacenter
Migration

Project
Technical Externals Organizational
Management

Project
Requirements Regulators Culture
Dependencies

Technology Customer Staffing Quality Estimating

In red box is included
the key risks of the
Complexity and Staffing
References
Markets
Sufficiency
Planning project

Process Weather Decision Making Controlling

Analytical Partners Prioritization Communications

Funding
Slide 2: Risk Assessment - In this slide, you will include either the Risk Severity Matrix or FMEA to assess these risks and
identify the top risk. You can use the templates in videos 6 and 7 or create your own.

4
Resources not in Workloads with
expert level to highly legacys
Likelihood

complete tasks dependencies non

3 analyzed

Bad planning
estimation

Partners not ready

to do a Datacenter
2 Migration

Bad cloud billing Changes in local

estimations laws about cloud

1 2 3 4 5
Impact
Slide 3: Risk Response Development - In this slide, you will include 3–5 bullet points outlining the strategies you would
use to respond to the top risk you have identified.

Top RISKS

1. Workloads with highly legacys dependencies non analyzed

a. Customers need to know that a dc migration project needs to be executed with a real exhaustive
analyze.
b. Separate workloads by level of dependencies allows to segregate what will be the workloads impacted
into a non analyzed servers. Also allows to start migrations without impact the business.
c. This must be communicated since day 0 of the project.
d. In case you find a non detected servers (it could happen with companies that has very old servers) we
can define with the customer a plan that includes pause the workloads affected without stop the non
affected and the focus in another solution.
e. Work scope plan must be prepared to handle this scenario.

2. Bad planning estimation

f. Reserve a 15% extra budget for variations in the implementation.
g. Discuss an agile plan with the customer, working an iteration and measure the success using sprints
instead a single end date.
Slide 4: Risk Response Control - In this slide, you will include 3–5 bullet points outlining your plan to control that risk
once the risk strategies are being implemented.

1. Workloads with highly legacys dependencies non analyzed

a. As working in sprints, review the analyze of the next sprint at least 2 sprints prior the execution to be sure
there won’t be risks in the process of migration.
b. Rerun tools of migration if possible to assure no changes in the landscape to migrate
c. Present results in Weekly comitees to understand next actions

2. Bad planning estimation

d. Provide feedback of each migration sprint to retrospectives about each iteration and correct the next one.
e. Fix deviation and understand the impact of each sprint in the whole process.
f. Communicate the deviation in the weekly commitees to understand next actions.