Risk description Likelihood Mitigation Strategy Impact Contingency Who owns 1. Construction/Build 1.1 Does not meet requirements L WW through site H Rectify, Delay move, compromise 1.2 Requirements were wrong L Reviews, WW, early sign-off of critical items L-H Contingency budget or Accept 1.3 Cabling/power not completed on time L WW inspection H Delay equipment installation 2. Network 2.1 Insufficient funds for min. hardware & network M Re-negotiate budget, redesign network H Stage move over long period 2.2 H/W Delivery, DOA L Order early, regular enquiries, vendor inspection H Maintenance contracts & Vendor Certification 2.3 Incorrect design L External peer review L-M Use basic functionality. Seek vendor help 2.4 IP addressing schema fails L Don’t change L-H Regress 2.5 Performance issues with WAN Links L Identify and implement monitoring and management processes H 3. Organizational 3.1 Insufficient budget or budget over run M Identify who is the approval & delegate. Do detailed costing Have budget approved H Increase in budget approved Project delayed Scope of move reduced and compromise reached. 3.2 Timetable for move not approved or not workable M Sponsor and BU sign-off of timeline H Delay relocation
virtualization technologies planned for the project. delays with respect to time, cost and quality. 6.2 Business resources unavailable for user acceptance testing H Publish dates and get buy in. Sign-off system relocation plans Document test and acceptance plans and authorize IT staff to undertake testing for business. M Backup test resource IT test on behalf Test in business hours after move Business accepts ‘no test’ 6.3 IT resource contention for migration H Co-ordination and prioritization Cross skilling Use external resources M External resources called in Extend relocation time 6.4 Relocation preparation affected by day to day operations and other projects M-H Use Change Control process to stop unauthorized system changes Backfill key project staff Use external resources M-H Use external resources Delay relocation 7.Project Management Risks 7.1 Inadequate project definition L Ensure Advisory committee approve and sign-off acceptance of Project Plan H Go back to AC and seek mandate for new project definition 7.2 Project plan deficient L Distribute Project Plan to AC and project team to identify any omissions early. H Rewrite project Plan to include all in scope activities 7.3 Lack of communication M-H Develop communication plan and adhere to agreed communication activities Include regular formal reporting in this plan. H Seek agreement from project team and stakeholders to follow Communication activities. Delay project
7.4 Scope creep L Detail project scope in PMP and get SC sign-off. Only change scope if agreed to by AC. H Seek additional time and resources to deliver agreed changes to scope of project. 8.Security Risks 8.1 Logical threats – unlabelled equipment. M-H Ensure all equipment in inventoried, labelled and accounted for. H Group related backups prior to 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 after move. M Define working start order, working configuration prior to move. H Ensure machines can be restarted prior to move. Maintain working backup of machine in that state. 8.4 Infrastructure not working (UPS, Network etc). L Test and configure infrastructure prior to move. H Delay move if infrastructure is not working or not in place. 8.5 Loss of passwords, system documentation. L Make copies of passwords and configuration guides. Keep in secure location, accessible by key persons if needed. Destroy move. M Ensure current of passwords and configuration guides is accessible during move. Fail over to reserve cache if needed. 9. Application Risks 9.1 SAN based replication of Oracle DBs (re:RW email March 3, 2009)