Impact
Priority and Funding
Priority - 2
Funding - Discretionary
Impact and Dependencies
The developed solution will need to be capable of supporting the continuing information needs of ESPA and their stakeholders after the formal end of the ESPA programme (March 2019) at least until a legacy partner is identified and involved in the programme's legacy. This is a matter for ESPA alone.
The current website and back-end is supported by EDINA and ERI on behalf of ESPA. It is assumed that with the end of the programme, support needs will reduce to a minimum of the continued running of the website on its technical infrastructure.
It is also assumed that the decommissioning of existing infrastructure will not be carried out by this project.
Project Risks
(as at Monday 5th June 2017)
| Ref | Title | Description | Impact | Probability | RAG |
| 1 | Stakeholders and requirements | There is a risk that stakeholder groups may will not be able to agree upon or prioritise requirements for improvement of front-end features and capabilities. | Medium | Low | GREEN |
| 2 | Staff availability | There is a risk that critical project staff may depart (PM is a contractor) or be unavailable (project is Priority 2) before delivery, leading to suspension or slippage of project activities against plan. | Medium | Low | GREEN |
| 3 | Supplier and end-user culture & language | There is a risk that cultural and linguistic diversity among stakeholder groups and suppliers will lead to misunderstanding and / or poor definition of requirements and needs, leading to compromise and inappropriate delivery. | Low | Medium | GREEN |
| 4 | Technology reach and bandwidth | There is a risk that technology reach and bandwidth will be simply insufficient for extremely remote Technology reach end-users needs to be met satisfactorily. | Low | Medium | GREEN |
| 5 | Legacy funding | There is a risk that legacy funding for service delivery and maintainability will not be available and agreed. | Low | Medium | GREEN |
| 6 | Access to end-users | There is a risk that inadequate, mediated or non-existent access to end-users (and potential end-users) will compromise the quality of product and fitness for purpose. | Medium | Low | GREEN |
| 7 | Front and back end dependencies | There is a risk that inter-dependencies between front and back end developments may lead to complex delivery schedule and problems with stakeholder expectations. | Low | Low | GREEN |
| 8 | Funding availability and timescales - 2017/18 | There is a risk that limited budget and constrained time may either or both run out before significant beneficial functionality can be delivered. | High | Medium | AMBER |
| 9 | Supplier engagement and focus | There is a risk that a decision to engage a 3rd-party supplier of development expertise may not yield value for money or a quality product. | Low | Medium | GREEN |
| 10 | Assumption re MI Reporting | There is an assumption that MI reporting for ESPA will not be required after the programme closes, and that the existing (simple) MI reports can be migrated 'as-is' from Access to Drupal. There is a related risk that the MI needs of the ESPA programme may change as it completes its activities, resulting in new requirements that cannot be met by simple end-user requests via the new Drupal facilities. | Low | High | AMBER |