Staffing not in place at project start
· Key project directing/managing staff already in post.
· GIS specialist available as required to support project.
· No recruitment is necessary for project start up.
Absence, illness or loss of key staff during the project
· A ‘pool’ of analysts and technical resource exists within IT Services the workload of these could be reprioritised to support this initiative.
· Team-based culture with collaborative practice to share learning and knowledge amongst team members.
Scope of project over-ambitious
· Strong Project Board involvement to provide realistic and pragmatic project guidance.
· Early refinement of detailed work packages in consultation with stakeholders represented on Project Board.
· Approach to project has been to identify a mix of deliverables covering working enhancements, feasibility studies and designs to support future work.
Lack of buy-in, engagement or commitment from internal stakeholders
· Very high level commitment at senior levels in Genetics and IT Services.
· Issues with and priority of addressing research requirements well understood within UoL.
· Strategic importance of developing integrated HALOGEN database well recognised.
· Experienced in-house technical resource available to help with design and implementation of technical solutions.
· Objective is to exploit existing data management infrastructure within IT Services and UoL. The technical solution will be aligned with the UoL IT Strategy.
· The evaluation criteria for any new infrastructure components will be weighted to reflect the need for ‘well proven’ and ‘robust’ solutions wherever possible.
Lack of relevance of lessons learned to wider JISC/UK RDS Community
· Involvement of JISC and UKRDS on Project Board to align initiatives with broader requirements of the HE community.
Wednesday, 2 March 2011
Project Plan Post 3 of 7: Risk Analysis and Success Plan
The initial risk analysis is detailed below.