Report for Sept 2016
- Report Date
- September 2016
Achievements in Last Period
- Continue scenario testing.
- User guides complete
- UAT plan in progress
- Monthly Billing development delivered for testing.
- Deletion / Archiving successfully completed in TEST.
Issues
- Single sign-on (EASE authentication) issue. We have now successfully identified the source of the problem; this requires an estimated 6 days infrastructure re-work – in progress.
- Application Performance (Deletion/ Archiving of ‘old’ data). The deletion and archiving process is now well understood. However, there is a knock-on effect on our legacy applications, caused by moving data from one set of tables to another. An impact analysis is in progress, and this is likely to result in further system changes.
- Inventory Mgmt. We have agreed that new part numbers will need to be allocated to existing inventory, with a naming standard that includes the location as the high-order part of the key. Part of this change is to obsolete an existing table called “NPT”. As with archiving, this has a knock-on effect on our legacy application, which will require further system changes.
- Stability / Reliability of Mobile Devices. A lot of the stability/ reliability issues encountered have been put down to data quality issues in TEST. We have therefore spent a lot of time ensuring SLA etc. are set-up properly, and have recently completed an exercise to clean out old WRs in TEST. We need to repeat our scenario tests and through this gain confidence that we have reached the required levels of handset stability.
- Mobile Device versions. We have bought an additional mobile devices (Android, iOS) into scope, to ensure we have appropriate coverage given the distributed device is no longer available to purchase.
- Given the issues identified above and the overall workload outstanding, it has been recommended (and verbally agreed with the sponsor) that the project go-live date be pushed back to Wednesday December 7th. This date will be further reviewed at the implementation board on Wednesday 26th October, when scenario testing is expected to have completed, and a clearer commitment and communication on dates can be made.
Next Steps
- Adjust budget / milestones / scope to match current plan.
- Complete Scenario Testing.
- Conduct UAT
The project is reporting RED as a result of the new milestones not having yet been pushed through governance.