| Project Info |
Project Managers Commentary |
|
FIN108 (AP56-042)
Essential enhancements (FIS)
Category: Discretionary
Milestones
tbc - dependent on the Supplier's delivery of a successful fix. Milestones to be re-planned in June.
RAG Status : SUSPENDED
|
Report by Emma McNab for May 2017
This project is due to be unsuspended in early June as a date for the FPM patch being applied and signed off in DEV has been confirmed.
Testing is currently underway in Finance for the latest patch which was released and applied to DEV. Initial testing was positive and if the patch is signed off in DEV .
Next Steps
- Progress latest patch to Test
- Re-plan the project's remaining milestones
|
|
FIN111 (AP56-036)
eExpenses enhancements
Category: Discretionary
Milestones
RAG Status : AMBER
Milestones
|
10-Mar-2017
|
Project Restart
|
|
13-June-2017
|
Delivery
|
|
23-Jun-2017
|
Closure
|
|
Report by Emma McNab for May 2017
Achievements this Period
- Iteration 6 was closed on 11th May.
- User stories for iteration 7 were agreed and initiated
- The project backlog has been fully reviewed prior to closure.
Issues
- Amber - ISSUE Due to the size and complexity of work required to resolve concerns relating to financial code selection within eExpenses the risks aligned to this will remain as critical going into closure. This issue is aligned to previously proposed (issue 11) remedial work. Unfortunately, due to budgetary and resource restraints the final iteration of the project could not take forward the remedial work and now consists of work to address other prioritised stories. No other feasible technical solution could be identified that addressed the concerns whilst remaining within budget. The Project Sponsor and Programme Manager accepted this issue and associated risks.
- Amber - ISSUE There are user stories in backlog aligned and dependant to the e-Authorisation project (FIN115). These could not be initiated until FIN115 completed (22nd May). This resulted in little time within iteration 7 to complete tasks (due to close on 6th June). Due to resourcing constraints extending iteration 7 is not possible.
Next Steps
- Complete iteration 7
- Initiate closure procedures
Minor changes have been made to milestones (within tolerance).
|
|
FIN115 (AP67-026)
Financial systems user de-provisioning
Category: Compliance
Milestones - WP1
|
Target date
|
Title
|
Complete
|
|
07/09/16
|
WP1 Planning
|
YES
|
|
11/04/17
|
Delivery
|
YES
|
| 02/06/17
|
Closure
|
NO
|
|
RAG Status : AMBER
|
- Report by Richard Bailey for May 2017
Achievements this period
WP2
- All minor bug fixes completed and tested
- UAT completed
- WP2 code / fixes deployed to live
- Draft completion report completed, for Project Team review 08/06/2017
Risks/Issues
WP2
Next Steps
WP2
- Update TAD
- Complete Project (expected 09/06/2017)
|
|
FIN116 (AP67-022)
eTime - guaranteed hours
Category: Compliance
Milestones
RAG Status : AMBER
|
Report by Richard Bailey for May 2017
Achievements in last period
- Development almost complete and progressing to plan
- eSignature estimate handed to Business / Programme Manager for agreement / decision to move forwards
Issues / Risks
Next Steps
- Complete build tasks
- Start integration and acceptance tasks / complete testing
|
|
FIN117 (AP56-054)
Finance BI Improvement
Category: Discretionary
Milestones
| Target Date |
Title |
Complete |
| 15-Dec-2016 |
Planning Sign-off |
Yes |
| 26-May-2017 |
Delivery |
No |
| 02-June-2017 |
Closure |
No |
RAG Status: Green
|
Report by Richard Bailey for May 2017
Achievements this period
- Finance analysis of BI reports still underway with the target population of reports being analysed
- It was confirmed with Service Management (Andrew McFarlane) that the hiding of universes could be done under service, rather than project if required
Risks
- Key project resource may be unavailable at critical times due to higher priority work
- The remaining BI development activity may take longer to complete than initially estimated if not conducted by specialist
Next steps
- Continue BI report analysis, then begin universe rationalisation analysis (i.e. which universes have no/few reports, and can any remaining reports be either removed or pointed to a newer universe)
- 'Security Workshop' arranged for 07/06/2017
- Time secured from Software Development w/c 19th June in order to review / look to address the remaining JIRA stories (if required)
|
|
FIN118 (AP56-016)
eFinancials upgrade
Core funded
RAG Status: Green
|
Report by Chris Orrell for May 2017
Achievements in Last Period
- At 6 June as-is eFinancials test progress as follows: TEST 93% complete, DEV 58% complete.
- IS Integration Testing is 80+% (by number of applications). Some applications are undocumented and identifying and accessing these is proving to be time consuming. Tests are added to TestRail as an application and means to test it is identified.
- Weekly progress meetings with Advanced are taking place and this has ensured the following have been completed:-
- Number of required contracted days has reduced from 110 to currently 62.5 and controls have been agreed (final discussions ongoing).
- Pre-installation survey and Advanced Statement of Works received (documents to be reviewed).
- Technical discussion involving Dev Tech & Advanced Installer agreed approach for OpenAM / OpenDJ (Advanced will install 4th July).
- DEV set up plan drafted.
Issues
- FIS testing started later and for circumstances beyond the control of the project this did not progress as intended. FIS currently suggesting as-is DEV tests may not be required but this has yet to be discussed. Testing rescheduled for 7 June.
- Agree number of contracted days with Advanced and raise purchase orders split by project phases that do not straddle the year end.
- Vulnerability scan report results have been shared with Advanced and assurances requested against these. Security testing requirements for FIN118 are still to be fully agreed and discussions are ongoing.
- Advanced have advised a second installer is required for V1 forms set up. Dates have been booked but a meeting is required with this installer and Dev Tech to confirm respective tasks and approach.
Next Steps
- Complete SAS & FIS as-is DEV and TEST application testing.
- Ensure lessons learned are captured.
- Complete interface definition and then testing in as-is DEV and TEST.
- Review Advanced Statement of Works, Pre-Installation Survey and confirm is this is sufficient to define work the required from University and Advanced pre, during and post DEV set up.
- Progress outstanding items with Advanced including: Java Webstart configuration documentation, control of JIRAs, V1 installation tasks.
- Sign-off TAD (End of Analysis / Design Stage milestone) scheduled for 14 June.
- Define change Control Board terms of reference, discuss these with Head of Development and communicate these to project and programme managers.
- Prepare detailed plan for August and obtain commitment for resources necessary to set up DEV, test it and be prepared to upgrade TEST 4th September.
|
may2017.png
