Transcription
Risk Management PlanTable of ContentsPROJECT INFORMATION . 2VERSION CONTROL/ RISK CHANGE LOG . 2RISK ASSESSMENT AND MANAGEMENT TABLE . 3Construction/Build . 3Network . 3Organizational. 3Systems failure during migration track. 4rd3 Party Issues . 4Resources . 5Project Management Risks. 6Security Risks. 6Application Risks . 7
PROJECT INFORMATIONProject Number (if applicable):Project Name: Data Center RelocationDate:Project Ownership: Information Technology ServicesPrepared by: Project Manager Name Project Contacts:NamePositionPhonePrimaryOtherOtherVERSION CONTROL/ RISK CHANGE LOGAdd new rows to the table as versions are created. No changes should be made to thisdocument without approval of the Project Manager, Data Center Relocation project. Thefirst row should reflect the current version in distribution.VersionNumberDateDescription, Reasons, Comments ApprovalsV1.0January 12, 2009Initial Draft – C.E. PierceV1.1V1.2After acceptance of this document by the project Advisory committee any new risks orchanges to risk table should be listed here for quick identification by stakeholders.Risk No.DateDescription, Reasons, Comments ApprovalsDataCenterTalk provides free Resources/Tools for Data Center Professionals.For our professional services please contact us at info@datacentertalk.com
RISK ASSESSMENT AND MANAGEMENT TABLERiskId.Risk descriptionLikelihoodMitigation StrategyImpactContingencyConstruction/Build1.1Does not meet requirementsLWW through siteH1.2Requirements were wrongLReviews, WW, early sign-off ofcritical items1.3Cabling/power not completed ontimeLWW inspectionHDelay equipment installationL-HRectify, Delay move, compromiseContingency budget or AcceptNetwork2.1Insufficient funds for min.hardware & networkMRe-negotiate budget, redesignnetworkHStage move over long period2.2H/W Delivery, DOALOrder early, regular enquiries,vendor inspectionHMaintenance contracts & VendorCertification2.3Incorrect designLExternal peer reviewL-MUse basic functionality. Seekvendor help2.4IP addressing schema failsLDon’t changeL-HRegress2.5Performance issues with WANLinksLIdentify and implementmonitoring and managementprocessesHMIdentify who is the approval & sign-HOrganizational3.1Insufficient budget or budgetIncrease in budget approvedDataCenterTalk provides free Resources/Tools for Data Center Professionals.For our professional services please contact us at info@datacentertalk.comWho owns
RiskId.Risk descriptionLikelihoodover runMitigation StrategyImpactoff delegate.Project delayedDo detailed costingScope of move reduced andcompromise reached.Have budget approved3.2Timetable for move not approvedor not workableMContingencySponsor and BU sign-off oftimelineHDelay relocationWW inspectionHDelay relocationDevelop a plan for everysystem. Test each systemMUse backup systemDevelop a plan for everysystem. Rehearse migration.Appropriate consideration forconnectivity requirements.HPublish timeline3.3Cabling/power not completed ontimeLSystems failure during migration track4.14.24.3Systems fail on cutover dayLFull and adequate understandingof the complexities andinterdependencies of systemsand application.MSystem latency from MCNC isunacceptableHSystem owners to rectify failuresUsing regression plansInvoke rollback plan and redo/correct system documentationDelay migration3rd Party Issues5.1rdKey 3 party staff unavailableincluding :LDefine migration schedulerequirements and engageM-HSeek alternate supportDataCenterTalk provides free Resources/Tools for Data Center Professionals.For our professional services please contact us at info@datacentertalk.comWho owns
RiskId.Risk descriptionLikelihoodPinnacle,Mitigation StrategyImpactContingencysuppliers/contractors viacontractsSun, CiscoRelocation specialistResources6.1New Technology – The systemstaff at UNCC is not familiar withvirtualization technologiesplanned for the project.MWill require extensive training ofstaff and could cause projectdelays with respect to time, costand quality.M6.2Business resources unavailablefor user acceptance testingHPublish dates and get buy in.M6.3IT resource contention formigrationHBackup test resourceSign-off system relocation plansIT test on behalfDocument test and acceptanceplans and authorize IT staff toundertake testing for business.Test in business hours after moveCo-ordination and prioritizationBusiness accepts ‘no test’MCross skillingExternal resources called inExtend relocation timeUse external resources6.4Relocation preparation affectedby day to day operations andother projectsM-HUse Change Control process tostop unauthorized systemchangesM-HUse external resourcesDelay relocationBackfill key project staffUse external resourcesDataCenterTalk provides free Resources/Tools for Data Center Professionals.For our professional services please contact us at info@datacentertalk.comWho owns
RiskId.Risk descriptionLikelihoodMitigation StrategyImpactContingencyProject Management Risks7.1Inadequate project definitionLEnsure Advisory committeeapprove and sign-offacceptance of Project PlanHGo back to AC and seek mandatefor new project definition7.2Project plan deficientLDistribute Project Plan to ACand project team to identify anyomissions early.HRewrite project Plan to include allin scope activities7.3Lack of communicationDevelop communication planand adhere to agreedcommunication activitiesHSeek agreement from project teamand stakeholders to followCommunication activities.M-HInclude regular formal reportingin this plan.7.4Scope creepLDetail project scope in PMPand get SC sign-off.Delay projectHSeek additional time andresources to deliver agreedchanges to scope of project.Ensure all equipment ininventoried, labelled andaccounted for.HGroup related backups prior tomove. May result in data loss.Only change scope if agreed toby AC.Security Risks8.1Logical threats – unlabelledequipment.M-H8.2Data is corrupted during move.MCreate system/data backupsprior to moveHEnsure that infrastructure is inplace to restore systems.8.3Machines won’t start after move.MDefine working start order,working configuration prior tomove.HEnsure machines can be restartedprior to move. Maintain workingbackup of machine in that state.DataCenterTalk provides free Resources/Tools for Data Center Professionals.For our professional services please contact us at info@datacentertalk.comWho owns
RiskId.Risk descriptionLikelihoodMitigation StrategyImpactContingency8.4Infrastructure not working (UPS,Network etc).LTest and configureinfrastructure prior to move.HDelay move if infrastructure is notworking or not in place.8.5Loss of passwords, systemdocumentation.LMake copies of passwords andconfiguration guides. Keep insecure location, accessible bykey persons if needed. Destroyafter move.MEnsure current cache ofpasswords and configurationguides is accessible during move.Fail over to reserve cache ifneeded.Application Risks9.1SAN based replication of OracleDBs (re:RW email March 3,2009)This is the last page in the document.DataCenterTalk provides free Resources/Tools for Data Center Professionals.For our professional services please contact us at info@datacentertalk.comWho owns
move. May result in data loss. 8.2 Data is corrupted during move. M Create system/data backups prior to move H Ensure that infrastructure is in place to restore systems. 8.3 Machines won't start after move. M Define working start order, working configuration prior to move. H Ensure machines can be restarted prior to move. Maintain working
