|
FIN118 (AP56-016)
eFinancials upgrade
Core funded
RAG Status: Red
|
Report by Chris Orrell
- Report Date
- March 2018
Achievements in Last Period
- Testing and retesting is under constant review and for eFinancials and subsidiary systems just about all tests that can be completed have been.
- WIS approved an increase Project Budget of 121 days from 692 days to 813.
- Completed a repeat data migration as per a newly recommended approach by supplier (data export then import) instead of using DataGuard to see if this would fix the sequencing issue, it did not.
- JIRA has been fully reviewed, culling many old JIRAs which were preventing an efficient use of the JIRA system. However, more importantly all JIRAs have been fully reviewed to identify those to be classified 'show stoppers' which without fixing these means we cannot go-live. Including one JIRA as a catch all for eExpenses there are 7 show stopper defects. The impact of all the remaining JIRAs has been assessed and they have been classified must, should, could or won't fix. Overall there are 64 outstanding JIRAs.
- This will allow a more objective go-live assessment so we fully understand the impact of outstanding defects and the contingencies that would need to be in place at go-live.
- To improve defect resolution better alignment of team members to create virtual teams (Tuesday and Thursday mornings) was implemented. But this had limited effect due to impacts from strike action, sickness and resource bookings expiring.
- WIS agreed to increase the priority of FIN118 to highest.
- Defect regarding OpenAM/DJ linked to issues with eAthorisations has been resolved.
- Security Pen Testing started Monday 26th March as planned.
Issues
- 16 April go-live will not be achieved:-
- 22nd March supplier advised that we would need to change version in order to attempt to fix the sequencing issue. This potentially means that we need to repeat five months of UAT.
- Including the sequencing issue 7 show stopper defects must be fixed before go-live can be considered.
- Pen Testing Supplier have advised that they need root directly passwords to progress pen testing. This requirement was not listed in their pre-requisites nor raised at the 8th March pre-meeting which was convened to discuss all pre-requisites.
- Resource bookings for S/W development have all expired and availability of people to progress defect fixing is a significant issue. Although the rating of FIN118 has been increased to highest this is the same rating as other projects competing for resources and so security resource bookings is a significant issue.
Next Steps
- Fix sequencing issue and then depending upon whether a full repeat of UAT is required re-plan the entire project.
- Address issue preventing pen testing progressing.
- Complete defect resolution and UAT.
- Plan go-live preparation and see if these tasks can be ring fenced.
RAG Commentary
ISSUE: RED because the current proposed approach by supplier to fix the sequencing issue potentially means the University will have to rebuild DEV, TEST, Pre-LIVE and repeat DEV & TEST interface testing and most UAT. This will have major time and cost implications. This risk has been escalated within Project Services and Production Management. . |
|
FIN119 (AP67-024)
eInvoicing for Medium Suppliers
RAG Status : AMBER
- RAG Commentary
- ISSUE: Though not yet actually an issue, RISK: 5: Securing Software Development Resource - if resource is not able to be secured during April, then this project will turn RED in the next reporting period.
|
Report by Richard Bailey
- Report Date
- March 2018
Achievements this Period
- A PICCL and budget / funding was finally achieved to take this project forwards, after multiple WIS submissions.
- Milestones have been reset, however might need a further re-review once work package planning has taken place.
- Process model, based on the technical solution, has been agreed with the Business.
- The Business have made excellent progress in identifying the rule sets to use when accepting invoices with the SGS and have identified a draft initial set of waves of Suppliers to engage with.
Issues
- RISK: Securing Software Development Resource - The Senior Analyst Developer's availability to help plan work packages (WP) / complete the ADA is now extremely limited due to commitments against UWP016. The Resourcing Manager / Programme Manager have provisionally agreed time where the Senior Analyst Developer can do the analysis of the technical solution to create the WPs during April. Resource availability remains RED until bookings / WP's are secured.
Next Steps
- Complete the Applications and Data Architecture (ADA) Document and achieve sign off.
- Engage with the Senior Analyst Developer and plan subsequent WPs (based on the decisions made / the Project Proposal & ADA Documents).
- Secure resource to complete the WP's
- Milestones will need to be reset / PICCL'ed
- Get the SR document agreed and sign off / engage with the SG
-
-
-
|
201803-rag.png
