Completion Report
Project Summary:
The project delivered a set of functionality to allow staff (admin and academic) to enter engagement events for PGR students as this was an identified gap for CSE.
Were the project goals met? Yes
Were the project deliverables fully or partially accomplished? Yes, all the functionality which was within scope has been been delivered including document upload, which it was unsure originally whether there was time for.
- Access for all staff to view engagement events for a given student via the EUCLID student hub
- Access for Admin and Academic Staff to create events within the student hub
- Access for students to be able to see the events which have been entered, no update access.
Did the project deliver a solution to the problems being addressed? Yes
Does the Project Sponsor agree that this project can be closed at this time? Yes, the Project Sponsor has agreed the sign-off of this base functionality, which will be built on in SAC033, Tier 4 Engagement Monitoring.
| IS Apps Staff Resources Estimated on Project Brief (Days) | 25 days IS Apps resource Breakdown estimates: SSP Core: 24.5d Apps Management 0.5d |
| Actual IS Apps Staff Resources Used (% Variance) | 15.5 days IS Apps resource (-38%) Breakdown: SSP Core: 15 days IS Apps other Apps Management 0.5 days |
| SSP non IS Staff Resources Estimated on Project Brief (Days) | 25 days |
| Actual SSP non IS Staff Resources (Days) (% variance) | 17.5 days (-30%) |
Analysis of Resource Usage:
Staff Usage Estimate: days
Staff Usage Actual: days
Staff Usage Variance: 0%
Other Resource Estimate: days
Other Resource Actual: days
Other Resource Variance: 0%
Explanation for variance:
The SSP Non-IS resource used on the project has been 16.5 days
The variance was positive as a lot of the functionality could be re-used from other developments which meant that developing it in SSP was quick and easy. The scope of the project was also very limited and did not attempt to make the event structures very complicated which made the implementation straightforward.
Key Learning Points:
Consider carefully whether or not a development should go to Tribal especially where the development is very similar to work we have done before. The overhead of using Tribal should always be considered: this overlaps with the feedback from SAC028 Award Upload.
Project is a good example to stress to the users that keeping things simple allows us to deliver more quickly.
This project will now lead on to SAC033 Tier 4 Engagement Monitoring.
Outstanding issues:
There are no outstanding issues for the project. A subsequent project will build on top of this project base.