Closure Report
Project Summary
Previously up to 2016, there was no consistent Disaster Recovery review and testing performed for over 10 years.
Significant technical debt in the Disaster Recovery was built up, leaving University priority services at risk in case of major Disasters.
This project has two main objectives:
-
Build upon the 2016 Disaster Recovery project (INF120), by picking up recommendations:
- Review Disaster Recovery documentation location.
- Improve documentation related to Disaster Recovery for Top and medium priority services.
- Review and update the Disaster Recovery documentation produced in the 2016 initial Disaster Recovery project.
Project Scope
This project’s focus was to review the University’s priority services managed by IS Applications, this included Top and Medium Priority Services. Please note where any of these services are managed by 3rd party supplier (e.g. Cloud based) the project documented components that are shared and collaborated with the owning infrastructure area, such IT Infrastructure, to link to their documented Disaster Recovery Plans.
Out of scope: Project budget was set at 15 days max (late revised to 20 days), therefore this project could not complete any DR tests (including Top or Medium priority services). Please note that there are other services which are not classed as top or medium priority - reviewing the documentation for these services was out of scope on this project.
Analysis of Resource Usage:
Staff Usage Estimate: 20 days
Staff Usage Actual: 17.6 days
Other Resource Estimate: 0
Other Resource Actual: 0
Other Resource Variance: 0
Explanation for variance
-
n/a
Outcome
|
No. |
Description |
Priority (MoSCoW) |
Outcome |
| O1 | To establish the set of components which are used by the priority services Applications | ||
| D1.1 | Review all applications and components which make up the Top and Medium priority services | Must Have | Achieved |
| O2 | To review and update a Disaster Recovery plan, where required, for each of the applications noted as top and medium priority services | ||
|
D2.1 |
Establish a DR position for each top priority application, where required |
Must Have |
Achieved |
| D2.2 | Establish a DR position for each medium priority application, where required | Must Have | Achieved |
| D2.3 | For each Top and Medium priority service, if none already available, produce a DR document/plan. This must include a written document, if none already available, on how to recover each application. This may link to other documents | Must Have | Achieved |
| O3 | Review Disaster Recovery plans in established central repository and communicate any changes to appropriate support teams | ||
| D3.1 | Review storage and access to Master Documentation containing DR position for each component and detailing each Top and Medium priority Service DR Document / Plan | Should Have | Achieved |
Key Learning Points
- An agreement that going forward this documentation is maintained as a BAU activity by Technology Management.
- 18 recommendations for DR documentation process delivered in report. The DR documentation can be found on the IS Applications System Documentation Dashboard SharePoint site.
Outstanding Issues
There are no outstanding issues.