December 2019 | Project Management

Achievements in Last Period

None as no resources onto the project for analysis or sytem changes, or PM
PM will restart assignment on the project from Feb once other resources are available

Issues

The experienced BA has left the project to work on Core Systems https://secure.projects.ed.ac.uk/unpublished/project/sac077/issues/9 and has not been replaced yet- Impact the analysis to QA data ahead of new statutory returns
Decision was made in Nov to suspend system design/development over Dec/Jan as a result of the lead developer being conflicted with PCIM work (Service Excellence) for 6 weeks (Dec 2019 and Jan 2020): https://secure.projects.ed.ac.uk/unpublished/project/sac077/issues/10
As a result of resource contsraints, a second developer is only available to start on the project from Feb 2020

Note that 2nd stream - new data required to be captured at the next registration. PM secured and analysis work in progress see separate initiated project https://secure.projects.ed.ac.uk/project/sac078

Next Steps

Complete mode of study design from Feb 2020 post PCIM work
Start build (population) in Feb 2020, with 2nd developer
Plan work with new PM, incl clarify what changes are required to use standard SITS (and not the IS programme workaround) to complete statutory returns in 20/21

Milestones

Revised dates confirmed in July by HESA, new dates replanned over 3 years

Implementation to HECoS by end Jan 20, so that statutory returns for 19/20 is done using legacy systems with new HECoS codes
TBC -20/21 likely 3 statutory returns using legacy returns (i.e. keep using current data model. Impact: will need ability to churn data volume and quality) .
TBC- 21/22 3 new statutory returns

Project Status

RAG Status

RAG Commentary: Several issues: -1) the Business Analyst who has left the project (conflict with Core Systems) in Oct has not been replaced. Impact to data quality analysis to remove barrier to future returns. Plan to resolve: Request for her return in February has been escalated by sponsor to CIO/USG deputy secretary. - 2) Constraints Dec resource. Impact: Delay in starting build a. Plan to resolve: 2nd Dev resource has been secured from Feb 20. -3) Lead developer has been conflicted with PCIM work over Dec/Jan. Impact of 1, 2 & 3: project is delayed, development and system changes activities were suspended over Dec and Jan . Plan to resolve: Secure return of conflicted resources but additional resources amy be needed to meet statutory requirements for 2020/21 returns. In addition, there is also uncertainty about the HESA requirements and when this will be communicated. This risk is on the need for future additinal scope. Plan to resolve: Current scope of work for 19/20 will prepare foundation for both system and data quality.

Change Status

Activity

This article was published on Jan 10, 2020

Initiate

Plan

Execute

No documents

Deliver

No documents

Other

No documents