Risk Management Plan - Division of Information Technology



Risk Management PlanProject InformationProject Number (if applicable): TBAProject Name: Data Center RelocationDate: Project Ownership: Information Technology ServicesPrepared by: Name, Project ManagerProject Contacts: NamePositionPhonePrimaryOtherOtherVersion Control/ Risk Change LogAdd new rows to the table as versions are created. No changes should me made to this document without approval of the Project Manager, Data Center Relocation project. The first row should reflect the current version in distribution.Version NumberDateDescription, Reasons, Comments ApprovalsV1.0January 12, 2009Initial Draft – C.E. PierceV1.1V1.2After acceptance of this document by the project Advisory committee any new risks or changes to risk table should be listed here for quick identification by stakeholders.Risk No.DateDescription, Reasons, Comments ApprovalsRisk Assessment and Management TableRisk Id.Risk descriptionLikelihoodMitigation StrategyImpactContingencyWho owns1. Construction/Build1.1Does not meet requirements LWW through siteHRectify, Delay move, compromise1.2Requirements were wrongLReviews, WW, early sign-off of critical itemsL-HContingency budget or Accept1.3Cabling/power not completed on timeLWW inspection HDelay equipment installation2. Network2.1Insufficient funds for min. hardware & networkMRe-negotiate budget, redesign networkHStage move over long period2.2H/W Delivery, DOALOrder early, regular enquiries, vendor inspectionHMaintenance contracts & Vendor Certification2.3Incorrect designLExternal peer reviewL-MUse basic functionality. Seek vendor help2.4IP addressing schema failsLDon’t changeL-HRegress2.5Performance issues with WAN LinksLIdentify and implement monitoring and management processes H3. Organizational3.1Insufficient budget or budget over runMIdentify who is the approval & sign-off delegate.Do detailed costingHave budget approvedHIncrease in budget approved Project delayedScope of move reduced and compromise reached.3.2Timetable for move not approved or not workableMSponsor and BU sign-off of timelinePublish timelineHDelay relocation 3.3Cabling/power not completed on timeLWW inspection HDelay relocation4. Systems failure during migration track4.1 Systems fail on cutover dayLDevelop a plan for every system. Test each systemMUse backup system System owners to rectify failures Using regression plans4.2Full and adequate understanding of the complexities and interdependencies of systems and application.MDevelop a plan for every system. Rehearse migration. Appropriate consideration for connectivity requirements.HInvoke rollback plan and redo /correct system documentationDelay migration4.3System latency from MCNC is unacceptableH5. 3rd Party Issues5.1Key 3rd party staff unavailable including :Pinnacle, Sun, CiscoRelocation specialistLDefine migration schedule requirements and engage suppliers/contractors via contracts M-HSeek alternate support6. Resources6.1New Technology – The system staff at UNCC is not familiar with virtualization technologies planned for the project.MWill require extensive training of staff and could cause project delays with respect to time, cost and quality.M6.2Business resources unavailable for user acceptance testingHPublish dates and get buy in.Sign-off system relocation plansDocument test and acceptance plans and authorize IT staff to undertake testing for business.MBackup test resourceIT test on behalfTest in business hours after move Business accepts ‘no test’6.3IT resource contention for migrationHCo-ordination and prioritizationCross skillingUse external resourcesMExternal resources called inExtend relocation time6.4Relocation preparation affected by day to day operations and other projectsM-HUse Change Control process to stop unauthorized system changesBackfill key project staffUse external resourcesM-HUse external resourcesDelay relocation7.Project Management Risks7.1Inadequate project definitionLEnsure Advisory committee approve and sign-off acceptance of Project PlanHGo back to AC and seek mandate for new project definition7.2Project plan deficientLDistribute Project Plan to AC and project team to identify any omissions early.HRewrite project Plan to include all in scope activities7.3Lack of communicationM-HDevelop communication plan and adhere to agreed communication activitiesInclude regular formal reporting in this plan.HSeek agreement from project team and stakeholders to follow Communication activities.Delay project 7.4Scope creepLDetail project scope in PMP and get SC sign-off.Only change scope if agreed to by AC.HSeek additional time and resources to deliver agreed changes to scope of project.8.Security Risks8.1Logical threats – unlabelled equipment.M-HEnsure all equipment in inventoried, labelled and accounted for.HGroup related backups prior to move. May result in data loss.8.2Data is corrupted during move.MCreate system/data backups prior to moveHEnsure that infrastructure is in place to restore systems.8.3Machines won’t start after move.MDefine working start order, working configuration prior to move.HEnsure machines can be restarted prior to move. Maintain working backup of machine in that state.8.4Infrastructure not working (UPS, Network etc).LTest and configure infrastructure prior to move.HDelay move if infrastructure is not working or not in place.8.5Loss of passwords, system documentation.LMake copies of passwords and configuration guides. Keep in secure location, accessible by key persons if needed. Destroy after move.MEnsure current cache of passwords and configuration guides is accessible during move. Fail over to reserve cache if needed.9. Application Risks9.1SAN based replication of Oracle DBs (re:RW email March 3, 2009) This is the last page in the document. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download