Report for August 2019

CSG015

Risk Management System Procurement

Milestones - under review following unsuccessful ITQ exercise

RAG Status

AMBER

Achievements in Last Period:

• Project review and agreement on next steps following unsuccessful ITQ exercise

Issues:

• A further review of the market and potentially a more complex procurement exercise may be required

Next Steps:.

• To proceed with procurement of the desired Enterprise Risk Management System for the University, via completion of an ITT-based procurement exercise.
• The Project Sponsor has secured additional budgets from 19/20 to support this more complex procurement exercise and to also procure a higher cost SaaS solution.
• To undertake additional CSG015 project replanning support by Project Services during 19/20

CSG016

Industry Relationship Management (IRM) Service

Milestones

Agreed / approved at WIS after Planning (12-Jul-2019):

RAG Status:  AMBER

Report for August 2019, prepared by Richard Bailey

Achievements this Period

• The Business Analyst has started to work through the following Project deliverables:
  • Work with EI to map existing processes
  • Work with EI to understand training requirements
  • Begin requirements workshops with Service Management and EI which will inform the SDD and other supporting documentation such as OLA
• Sophie Milner will take over as Project Manager once the current Project Manager (Richard Bailey) leaves - 27-Sep-2019. Richard will work with Sophie to arrange Governance, Project Meetings, for the remainder of the Project 

Issues

• Risk #9:  Lack of Existing Service Process Definition Documentation  (Red)  -  It has come to light during the early stages of Business Analysis that the existing Service process definition documentation is not in place / is still to be documented, this was a prerequisite of the Project and could see a greater amount of upfront analysis required in order to determine the Service Definition that will be required for IS to take the support model over
• Risk #10:  Agreement of a Standard Service Definition Across all Customers of IRM Might not be Reached  (Amber)  -  During initial analysis and in light of the fact that the existing support for the IRM service is not fully defined / documented it would appear that there is a risk that existing Customers of IRM are utilising CRM in different methods, if a common / standard approach cannot be adopted this could have consequences to providing Support
• Risk #1:  Project Budget insufficient to complete the project  (Amber)  -  Fully analysing both risks #9 and #10 above will likely have a knock on to both the Project time frame (milestones) and budget (tbc)
• Risk #5:  Availability of Key Resource  (Amber)  -  The Project has experienced lag in obtaining availability from various key resource, both due to annual leave commitments and illness. This has impacted the timeline and will need careful review

Next Steps

• Determine any requirement with EI / Service Management to discover if IS can facilitate documenting the existing service process definition (Risk #9 above) and replan the timeline accordingly, with a view against budget
• Continue to work through / look to complete the Project deliverables:
  • Work with EI to map existing processes
  • Work with EI to understand training requirements
  • Begin requirements workshops with Service Management and EI which will inform the SDD and other supporting documentation such as OLA