1

Cloud Migration: Tales from the TrenchesProject Management - In the Clouds!

• This webinar is being recorded and an on-demand version will be available at the same URL at the conclusion of the webinar

• Please submit questions via the button on the upper left of the viewer• If we don’t get to your question during the

webinar, we will follow up with you via email• Download related resources via the

“Attachments” button above the viewing panel• On Twitter? Join the conversation:

#cloudmigration @HOSTINGdotcom

2

Housekeeping

3

Our speakers today:

Catherine Roy, Director of PMO&

Kellen Amobi, Program Manager

4

Hosting PMO Statistics

• Responsible for over 200+ customer implementation projects• Private Cloud, AWS, Azure Cloud• Migrations• Disaster Recovery and Compliance

• According to ZDNet the global impact of IT failure could be as high as $3 trillion annually• CIA World Factbook estimates the US accounts

for $1.2 trillion of failed projects

5

Statistics

6

Balance

Scope

7

• Must increase timeline or cost• Critical to understand

customer’s requirements • Includes level of quality• When you start off with a bad

scope it ends up being a bad project – hard to recover from a bad scope

8

Balancing Scope as the Priority

• Build in a discovery phase• Define what success looks like

9

Defining the Scope

10

Scope Creep – can you control it?• Accept there will be a certain amount

of scope creep with a large number of projects• Between 2001 and 2005, the FBI’s Virtual Case

File project failed. Costs overran by 89% or just over $200M. A project that should have taken 3 years, failed after 4 years with requirements still not met. It is widely used as an example of a failed IT project.

• Change Management used to control scope creep

Schedule

11

• Must increase cost or reduce scope• In today’s cloud environment

customers assume projects will happen quickly

12

Balancing Schedule as the Priority

• Develop realistic schedules, despite what your executives are telling you.

• Plan contingency time for unknowns• Allow time to test network speeds

13

Developing a schedule

Migrations

14

• Migrations are some of the most stressful projects• Unknown for most customers since they tend

to migrate only once during their IT tenure.

15

Cloud Migrations

• The more details about the environment, the better

• Make sure you always have a test plan• Do realistic testing• Test your network speeds

• Make sure you have a detailed project management plan for cutover• Need clear roles and responsibilities

• Do a test migration prior to final cutover• A good baseline for estimating schedules

16

Lessons Learned from Migrations

• Plan for contingency time during migration• There will ALWAYS be a few small items/issues

that occur• Communication during migrations• How to support a phased migration• When you are down during the migration how

do you plan to communicate to staff

17

Lessons Learned from Migrations

• Avoid “cleaning up” and migrating at the same time

• Separate into 2 different projects or phases if possible to make troubleshooting easier

• Ensure you have a database expert involved

18

Lessons Learned from Migrations

Issues

19

Defining a problem for the software developer is completely different than defining the same issue to your VP of Operations, CEO, or customer• Know your audience• Keep it simple

20

Problems

• Best practices still apply• Testing, testing, testing• Know your environment!• Consider a phased approach• Have a roll back plan

21

Key Takeaways

22

Q&AFor more information about [insert relevant solution] by HOSTING,

please contact our team at 888.894.4678.