cutover plan v2

8/12/2019 Cutover Plan v2

1/32

Anatomy of a Cutover Planor Dont get caught dead in a go-live

s ua on

Mahesh Vallampati


2/32

About the Speaker

Mahesh Vallampati Senior Practice Manager at SmartDog Services Senior Sales Consulting Manager at Hotsos. Worked at Oracle for nine ears

Director of IT Database Services at a company inHouston

Published in Oracle magazine


3/32

Agenda

Go Live ecology Cutover Overview Cutover Plan


4/32

GO LIVE ECOLOGY


5/32

Go Live Ecology What is a Go-Live Anyway?

A move from one defined state to another defined state Typically supposed to

Minimize on-going risk Cost Effective

Involves

Several Stakeholders Co-ordination of tasks

Usually involves a small defined window of time Includes cutover tasks Also includes rollback tasks if needed


6/32

Go Live Ecology Bus.Perspective

..

,

, ,


7/32

Go-Live Ecology IT Perspective

,

,


8/32


9/32

Cutover Definition Is A Process

Execution of Planned Tasks By Several Stakeholders Step by Step Performed at least once or twice to document issues

and timings Variance from cutover for Production should be well

understood Lessons should be definitely learnt


10/32

Cutover characteristics

Plan well ahead Meet Customer Demand Ramp down Business, (Close open items, Notify

customers) Cutover Activities Key Decision point made by stakeholder

Move forward Roll Back

Go-Live or RollBack Business Ramp up


11/32

Cutover Process Pre-Cutover Activities

Build Production Environment Cutover Plan development Test Cutover Plan Wash/Repeat/Rinse

Finalize Cutover Plan Cutover Activities

Execute Cutover Plan Perform checks Go/No Go Decision

Post Go Live Support Issue Management


12/32

Cutover Plan


13/32

Cutover Plan

One document Includes all cutover related tasks Has a section for rollback also

on a ns s a e o ers an e r as s Has decision checkpoints Has detailed timing information for trial cutovers


14/32

Cutover Plan

Facilitates co-ordination between key playersand stakeholders

Owned by a project manager or a key

Business and IT own the cutover plan together A tool to manage cutover process

A tool to report progress against cutover tasks


15/32

Cutover Plan Document

Needs to be managed very tightly Changes to plan made only by cutover team Change risk understood and contingency plan in


16/32

Cutover Plan

Detailed Task List Timings and dependencies for each tasks Parallel execution and co-ordination of

inde endent tasks A contact list Rollback Plan Decision Points Contains readiness criteria


17/32

Readiness Criteria Criteria

Site Technology Training Data Migration Sustainment

Functionality Cutover Planning

Criteria Scores 1-5

1-No Impact

2-Low Impact 3-Medium Impact 4-High Impact 5-Show Stopper


18/32

Risk ScorecardCriteria/Score

1-NoImpact

2-LowImpact

3-Med.Impact

4. HighImpact

5. ShowStopper

Site

Technology

Training

DataMigration

Sustainment

Functionality

CutoverPlanning

Totals

Overall Risk Score


19/32

Contingency Plan


20/32

Cutover Plans Formats


21/32

Cutover Plan Formats

Spreadsheet Homegrown Created out of necessity

PM.030 Transition and Contingency Plan Document


22/32

Spreadsheet

Components Document Control Resources

Cutover Escalation os mp emen a on uppor an

On-Site/Remote Resources War Room Conf. Bridge

Risk Scorecard/Readiness Criteria Cutover Plan DR-Restore


23/32

Document Control

Version Control Owner Contributors

ev ewers Issue List


24/32

Resources

Cutover Escalation Post Implementation Support Plan On-Site/Remote Resources

ame Contact (Cell/Home/Office) Managers Contact

War Room/Conf. Bridge


25/32

A note on War Rooms

War Rooms are effective When there are team chemistry issues Post Go Live issues are certain

around the clock It is for a short period There is a lot on the line


26/32

Cutover Plan Task

Owner Others Involved Dependencies

Planned Start and End Actual Start and End

Variance in duration Status Notes Score Process Improvement Opportunity


27/32

DR-Restore

Same as Cutover Plan Get back to Original State


28/32

AIM Document PM.030

PM.030 Transition and Contingency Plan Owned by the Project Manager

DBA Team Infrastructure/OS Team Development Team Functional Team for Setups

Much easy if done ahead of time


29/32

PM.030 Sections

Detailed Transition Plan Cutover Contingency Plan Preparing for Production

ro uc on c e u e rs ee


30/32

PM.030 Sections Detailed Transition Plan

General Tasks Detailed Checklist Tasks

Cutover Contingency Plan Contingency Steps

pon ys em va a y Preparing for Production

Approach Production Schedule - First Week

Using the Company Support Infrastructure Information Systems Production Feedback Session Support Status


31/32

Walkthrough Cutover Plan Spreadsheet AIM PM.030 Document


32/32

Q U E S T I O N SQ U E S T I O N SA N S W E R SA N S W E R S

cutover plan v2

Documents