Completion Report
Project Summary:
Overview from Brief
This project was initiated to identify and deliver key enhancements to ABS and IS Apps-developed applications within Finance's SAS team.In order to enable Support to focus on 'Keeping the Show on the Road' activities, it has been agreed that a number of small enhancements will be taken forward under a project. This project will divide the enhancements into separate batches, and deliver as many enhancements as possible within the allocated budget. While the focus will be on ABS applications, there may also be some small changes to software developed in IS Apps.
Enhancements will be tracked via Jira, with a Jira issue for each item. The full list of enhancements will be prioritised using the MOSCOW system. The enhancements will be re-prioritised and selected prior to the start of each new batch, to allow flexibility and accommodate changing priorities.
Scope
Scope from Brief | Scope status |
---|---|
This project has a fixed budget of 50 days. | The project budget was reduced to 40 days on 18-Nov-2016 (see Change 2) |
Those enhancements agreed to be within project scope will be prioritised by the SAS team, in discussion with IS Apps. Any enhancements that are not delivered by the close of this project will be rolled over into the project for next year. | The project has complied with this Scope item. |
Additional enhancement requests may be added at any time during the project. However, each addition must be agreed by the Project Sponsor before being added to the project list. As each new batch begins, the full list will be reassessed and re-prioritised, to determine which should be included in the new batch. | The project has complied with this Scope item. |
Requests for system fixes are outwith the scope of this project. These should continue to be raised as UniDesk calls, and addressed under Finance's Support budget. | The project has complied with this Scope item. |
Deliverables
Deliverable from Brief | Deliverable status |
---|---|
Prioritised list of enhancements | Delivered |
Fully defined requirements for each high priority enhancement | Delivered |
Prioritised batches of enhancements | Delivered |
For each batch approved for action:
| Delivered |
Schedule
Target date from Brief | Milestone from Brief | Delivery date |
---|---|---|
30-Sep-2015 | Brief approved | 30-Sep-2016 |
11-Dec-2015 | Checkpoint: decide whether to unsuspend project | 14-Mar-2016 |
01-Jul-2016 | Delivery of final enhancements batch | 18-Jul-2016 |
15-Jul-2016 | Deployment Sign-off Review of final enhancements batch | 25-Jul-2016 - tbc |
22-Jul-2016 | Closure SIgn-off Review | 25-Jul-2016 - tbc |
Analysis of Resource Usage:
Staff Usage Estimate: 50 days
Staff Usage Actual: 40 days
Staff Usage Variance: -20%
Other Resource Estimate: 0 days
Other Resource Actual: 0 days
Other Resource Variance: 0%
Explanation for variance:
The project budget was reduced to 40 days on 18-Nov-2016 (see Change 2).
13 days of effort on the eAuths universe and reports were subsequently transferred to project FIN112, by agreement (see Decision 4) between the Business Lead and the Programme Manager. This ensured that sufficient days remained available for the work on the eFin password changes, the estimate for which increased from 3 days to 13 days.
Key Learning Points:
The Project Sponsor and Business Lead chose to delay the start of ISA's involvement on the project, in order to allow additional time for new business requirements to arise, and to be appropriately prioritised. This allowed the project's limited budget to be put to the best possible use. It is recommended that this approach be taken with future similar projects.
The project was fortunate in having access to a dedicated contractor, with a high level of BI expertise, to work on the eAuths universe enhancements. The semi-agile approach taken with this work also worked well. The Business Lead expressed the hope that similar expertise also be made available for next year's Finance BI project.
Outstanding issues:
UniDesk Call I160719-0482 - "BI Webfirst Password Error" was raised. This issue has been resolved by John Chan.
Anne Finnan takes forward an action to update the Implementation Plan for the eFin Password Changes, adding a section on the required connection string updates for the BI universes. Once updated, the Implementation Plan should be loaded to the Tech Collaboration wiki, for future reference.