Программа "Booty Challenge" от Ashy Bines. Неделя 4.
P12Q02.V2Descrição completa
P07Q02. V2
Программа "Booty Challenge" от Ashy Bines. Неделя 4.Full description
P04Q03. V2
P08Q06. V2
This is the Document that HB Gary Federal tried to sell the FBI in an attempt to unmask the leaders of Anonymous. Thus silenceing their right to freedom of speech and to protest (as guarente…Descripción completa
P13Q04. V2Descrição completa
Pocket Mars Reglamento en españolDescripción completa
Anatomy of a Cutover Plan or Don’t get caught dead in a go-live s ua on Mahesh Vallampati
About the Speaker 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 in Houston – Published in Oracle magazine
About the Speaker 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 in Houston – Published in Oracle magazine
Agenda •
Go Live ecology
•
Cutover Overview
•
Cutover Plan
GO LIVE ECOLOGY
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
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
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
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
Cutover Plan
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
Cutover Plan •
Facilitates co-ordination between key players and 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
Cutover Plan Document •
Needs to be managed very tightly
•
Changes to plan made only by cutover team
•
Change risk understood and contingency plan in
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
Readiness Criteria •
Criteria –
–
–
–
–
–
–
•
Site Technology Training Data Migration Sustainment Functionality Cutover Planning
Site Technology Training Data Migration Sustainment Functionality Cutover Planning Totals Overall Risk Score
4. High Impact
5. Show Stopper
Contingency Plan
Cutover Plans Formats
Cutover Plan Formats •
Spreadsheet –
Homegrown
–
Created out of necessity
–
PM.030 – Transition and Contingency Plan Document
•
Spreadsheet •
Components –
–
Document Control Resources •
•
•
•
•
–
–
–
Cutover Escalation os mp emen a on uppor On-Site/Remote Resources War Room Conf. Bridge
an
Risk Scorecard/Readiness Criteria Cutover Plan DR-Restore
Document Control •
Version Control
•
Owner
•
Contributors
•
ev ewers
•
Issue List
Resources •
Cutover Escalation
•
Post Implementation Support Plan
•
On-Site/Remote Resources –
•
ame
–
Contact (Cell/Home/Office)
–
Manager’s Contact
War Room/Conf. Bridge
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
Cutover Plan •
•
•
•
Task Owner Others Involved Dependencies –
–
•
•
•
•
•
Planned Start and End Actual Start and End
Variance in duration Status Notes Score Process Improvement Opportunity
DR-Restore •
Same as Cutover Plan
•
Get back to Original State
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
PM.030 Sections •
Detailed Transition Plan
•
Cutover Contingency Plan
•
Preparing for Production
•
ro uc on c e u e –
rs
ee
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 –
