Completion Report
Project Summary:
The project has delivered 2 work packages for the Research Information Systems team:
- Enablement of Single Sign On for Research Professionals
- Proof of concept for Snowball metrics which enables data to be sent to Elsevier securely and efficiently
Acknowledgement of these deliverables has been provided by Dominic Tate Head of Library Research Support.
|
O1. To deliver small enhancements/fixes that provide immediate benefits/quick wins to the user community |
||
|
WP1 |
Benefits |
Success Criteria Achieved |
|
D1 Enable Single Sign On while using Research Professional |
|
Single Sign On available for Research Professional User satisfaction owing to increase in sign on efficiency Achieved -YES |
|
WP3 |
|
|
|
D2 Investigate and resolve issue recorded under JIRA log - RES058-172. |
|
Resolve issue recorded under JIRA log - RES058-172 Achieved - under RES058 in April 2017 Resolve issue recorded under JIRA log - RES058-169 Not achieved - see outstanding issue section below |
|
WP4 |
|
Not required as agreed with RIS team |
|
D3 Replace legacy ‘HR portal’ with a more secure method of accessing HR data with audit logging |
|
Provide a replacement for the legacy ‘HR portal’ N/A
|
|
D4 Move existing users to the new system
|
|
N/A |
|
D5 Provide RSO with access to Oracle HR |
To allow the RSO team to undertake data checks when completing and validating research grant costings. |
RSO can successfully access Oracle HR system
N/A
|
|
WP 8 |
|
|
|
D6 Produce proof of concept for the Snowball metrics project |
Boosts the reputation of the University by ensuring we are involved in a consortium of research intensive universities
|
Complete and deliver proof of concept for Snowball metrics system Achieved -YES
|
|
D7 Send data to the Elsevier hosted Snowball metrics exchange via an uploader PHP widget feed |
Allows the University to benchmark itself against competitor’s data |
Data able to be sent to Elsevier securely and efficiently Achieved - YES |
Work Package 4 Removed from scope :
Research Information Systems Manager advised to withdraw the requirement for a replacement because:
- The current lookup does what it needs to do.
- The current lookup just works (no reported issues).
- Ultimately, this should be dispensed with this in its entirety, but checks are still required to cross reference information in Worktribe, particularly around non-standard salary grades.
- Agreement with Business Lead to review this separately and assess if a future project is required.
Analysis of Resource Usage:
Staff Usage Estimate: 50 days
Staff Usage Actual: 17 days
Staff Usage Variance: 34% spend (underspend 66%)
Other Resource Estimate: 0 days
Other Resource Actual: 0 days
Other Resource Variance: 0%
Explanation for variance:
- Original budget allocation to project was 50 days following review of requirements whereby a number were placed 'on hold' the agreed project brief estimate was 26 days.
- Actual spend on project 17 days as :
- WP3 JIRA RES058-172 fix completed within RES058 project;
- and JIRA RES058-169 unable to be progressed due to activities on other projects e.g. Pure upgrade to v5.7 and RES069 project using code
- WP4 withdrawn
Key Learning Points:
- This project was originally initiated in August 2016 and given a lower priority within the overall RES programme at that time to be delivered as and when Business and IS Applications resource were made available, this resulted in the project brief not be fully agreed for a number of months and delays in completing work packages.
- A suggested approach for this type of project in the future would be to gather known requirements and agreed small budget upfront. The project can drawn down as each requirement is assessed and agreed to deliver. This would allow the project brief to be completed early in the project lifecycle. Examples of project which have used this approach in the past were: COM007 and COM021.
- This project allowed one of the Student interns within Project Services to gain insight and experience on completing the revised project brief and working with stakeholder during re-planning stage
- Also collaboration with Alain Forester, Service Management to help with Snowball Metrics activity
Outstanding issues:
- Resolution of JIRA RES058-169 - although fixed in Development this will require comprehensive testing and also dependent on Pure to be upgrade to v5.7. Request has been made to resolved under RES069 however proposes this is estimated under and implemented under a small separate project or under RES057. Meeting arranged to review work to date as key developer is due to leave University in April and estimate effort to complete this activity.