Impact

Priority and Funding

This project has a normal priority and ring-fenced Core funding.

The estimations completed at Planning show roughly 106 days of effort needed to complete all work in the project plan/work breakdown schedule. Only 40 of these days are chargeable to the project in Project Services time (of which 3 days are contingency), while the remaining 67.5 days are not chargeable to the project and are supplied by the Project Sponsor, Business Lead, and Subject Matter Experts within their own time and work schedule. 

23/24: 14.5 days 

24/25: 25.5 days

Impact and Dependencies

This project will impact researchers and staff working with or at the University of Edinburgh by creating a uniform approach with guidance on appropriate IT systems, services, and enhanced processes to use to help researchers comply with the IT requirements of The NHS LHB Framework. This means the project will require engagement from various Subject Matter Experts to feed in on the content, user experience, and final deliverable. Discovery workshops lead by the Project Team with Subject Matter Experts at the start of the project (O3) will be necessary for the successful completion of O1 and O4, therefore these objectives are dependent on the successful outcome of O3, in particular D3.2 - D3.4. There will be a risk logged on the project to note that SME availability will impact the progression of the project lifecycle, and if their availability as resource to the project is dettered then we cannot move forward to the key deliverables in O1. 

There is a single external dependency which impacts O2, that being the update of the latest version of NHS LHB policies, codes or practice and standards, as referenced in the Framework Agreement. This will need to be compared to its previous versions to ensure the product deliverables continue to meet the latest expectations/changes in the agreement.

Lessons learned from previous projects

No key lessons learned were captured in the MVM317 project. However, there was a lesson learned captured in another project STU268 on creating a TEST environment for their SharePoint product (secured link - Lesson Learned #2). While this project will not be creating any integrations with internal or external services, the SharePoint resource is expected to be used long-term and therefore a plan for integrity and version-saving of the resource must be embedded to ensure a certain level of 'testing' of future resource 'updates'. Our Technical Lead in CMVM will review the version history tool to save and express changes to the resource over time.  

Project Risks