Single Sign-On has now now been successfully configured via the Test EASE environment
Testing to determine the impact of implementing SSO has commenced and all testing to-date has been successful
It has now been agreed that the two-phase login is technically acceptable, whereby;
the user is required to have a valid account within the application
the user is required to have an active EASE account
SSO has now been configured for the Live environment, and is now ready to be switched-on
Email Issue
An issue regarding the email address being generated by the system has been resolved
Project Closure
The project closure report has been completed and approved by the the project sponsor and senior business user
Issues
Final SSO testing regarding visitor accounts has been delayed due to a number of factors
Issues with the generation of visitor accounts - now resolved
Unavailability of the project team to complete testing in October through a combination of holidays and illness
Email
the issue regarding the email address being generated by the system, after the last upgrade, has been resolved
The project is currently predicting an overspend of 12 days, including 1 day to complete all remaining project activity
Next steps
SSO
Complete technical implementation for SSO, on the live environment, if pertinent
Complete project closure
RAG Commentary
The scheduled project closure in October has been delayed whilst final testing for visitor accounts is completed, whilst noting that all other SSO testing has been successfully completed. Final testing is scheduled to be completed in early November. There is currently no impact to the either the system usage nor the business.
Deployment of UG and PG to TEST gave "Too many authentication failures". This was resolved before Dev Tech's annual leave, but required a bamboo deployment the following week. There was an issue raised as the developer was not sure where to deploy the code as there are a number of active pages where the code could be deployed to. This was resolved with the help of Production, but the delay reduced the time testing could be carried out by production.
Issue raised regarding the completion of the deployment to TEST and would affect LIVE - Production and Development recommended that the person deploying to TEST should be the person deploying to LIVE, and also requires someone from EdWeb involved. The deployment steps required Development, Production and EdWeb involvement. This was pointed out when attempting to carry out the deployment to TEST and as a result was not completed. EdWeb contact for this was on annual leave, returning on 04/11.
Cost to be reviewed as 5 extra days required. Project is Amber as a result
Next Steps
Complete the deployment to TEST with the involvement of all teams
Work on overall implementation plan in conjunction with Fivium to schedule resource.
Commence internal process regarding case migration to the replacement eCase.
Engage with Procurement and Legal regarding process to purchase preferred solution.
Continued engagement with Fivium regarding various aspects of transition process.
Issues
Delay in procurement process is delaying fully engaging with Fivium in the technical aspects of the transition process. Project has now been re-assigned to our third UoE procurement contact this year.
Overall project delay will mean that the milestones need to be revised.
Next Steps
Progress with Procurement regarding process to purchase preferred solution. Aim to complete by the end of November.
Work on overall implementation plan in conjunction with Fivium to schedule resource.
Engagement with Fivium regarding case migration process to the replacement eCase.
Rescheduled milestone dates still to be approved by project , USG and ISG governance
AMBER RAG Commentary
The project as a whole has progressed more slowly that planned. This means that although the contract should be signed in November / December the initiation date will be early Jan with a go live date in early March. Having reviewed revised timescales with Records Management this will fit better with their resource availability.
The planning stage was approved by the project team
An architecture diagram showing the 'as-is' system set-up was produced
Further discussions have taken place on preparing how to capture business requirements
Issues
The project budget increase was approved (from 25 days to 35 days) so the Cost RAG moves to GREEN this month.
The business analyst assigned to the project was re-assigned to another programme; this has prevented the business requirements work starting, which increases the risk of missing the business requirements milestone. A new business analyst starts next week. The increased risk means that the Time RAG remains at AMBER this month.
Next steps
Sign off project planning stage
Undertake requirements capture sessions and document requirements
STU actual spend to end of Oct 2019
