Report for June 18

Report Date

June 2018

Achievements in Last Period

• UAT completed
• LTW documentation tasks completed

Issues

• UAT successfully completed but a showstopper appeared following UAT signoff that had not been on LTWs test plan
• The issue is with WebDAV which allows users to create local connections to content and upload files – this is no longer working and is creating errors. Used mainly by power users but is an integral part of the work they do. As there was no local workaround LTW asked Blackboard if they could supply a standalone patch but they informed they don’t do standalone patches but the issue would be fixed if we were to move to CU3. Blackboard confirmed that CU3 has been out for a long time on their SaaS and was confident in CU3 for UoE.
• We revised timescales and therefore moved to CU3.  Although we had a plan we kept the RAG status as AMBER due to this happening so close to deployment.
  • Testing on Dev was torturous with LTW receiving 502 errors and Page unavailable errors but with eventually were able to deploy to Test. Unfortunately we are now experiencing issues on Test with the original issue resolved but new issues uncovered. Blackboard are working with LTW and dev team to resolve however this is slow and arduous as they are fixing the issues one at a time and we don’t know how long this is going to take.
  • Escalated RAG to RED as deployment on 17 July is now in danger

• Project team has agreed that we rollback to CU2 and do a new install with Blackboard checking the logs to see what the failures are

Next Steps

• Resolution of CU3 issue
• Revise timescales if needed

Milestones

RAG commentary

Project is RED as deployment date of 17 July is in jeopardy.

A showstopper issue was found at the end of UAT which had no fix in CU2 or a local workaround. Advice from Blackboard was to move to CU3 which unfortunately is not working and to which our development teams cannot find a resolution. Issue has been escalated to Blackboard who are continuing to work with us to resolve.  Issue has been escalated to Blackboard who are continuing to work with us to resolve. We are now in the process of rolling back to CU2 to re-install CU3. A resource conflict has also been raised as developer was booked to HSS024 (normal priority and not required for start of term) but now required for the issues in Learn. This has been escalated to HSS portfolio manager explaining that this is a high priority, high profile system required for start of term.