Overview

Background

This is the second year of a three-year plan to improve the current Undergraduate and Postgraduate Degree Finders. The previous related project, STU247, focussed entirely on migrating these two applications to seamlessly work in the new EdWeb framework. This project will now implement those changes which are highest priority to the business from those listed in the project proposal, within the available budget.

Scope

The project will be managed in the same way as for STU246, with the work being consolidated into two work packages: WP1 Priority JIRA’s, system outputs and exports, and WP2 Admin system changes and improvements. The scope will be based on those jiras as prioritised in the Business Requirements.

Out of scope:

Changes to Campus Maps, and associated implementation of Bamboo.

Objectives

To work with CAM to deliver small enhancements to the CAM UG & PG Degree Finder applications.

To continue using the amended way of working which was tested in STU246 (noted in Completion Report) and continued effectively in STU247 (noted in Completion Report), whereby CAM define the requirement, test cases and success criteria in jira rather than Project Services, and peer testing is undertaken by Applications Management rather than Software Development.

To vary the scope of which jiras are included to remain within the allocated budget. To resolve the jiras prioritised in the Business Requirements as far as can be accommodated within the current 88d allocation.

To implement Bamboo to automate deployment to TEST and LIVE potentially for the UG Administration and PG Administration applications. This will be done only if requirements are prioritised that mean that changes to these applications are required.

Deliverables

Small enhancements to the CAM applications, as detailed in the prioritised jira issues.

Benefits

Improvements to the CAM applications, expected to be primarily UG And PG applications.

Better balance of work between IS Applications Management and IS Software Development for calls which are enhancement requests rather than fixes to LIVE applications.

Continuing the new method of working, whereby CAM define the requirement, test cases and success criteria in jira rather than Project Services and Applications Management peer test rather than Software Development.

If Bamboo is implemented for one or more of the UG Administration and PG Administration applications this will improve the ability to resolve issues and deploy to TEST/LIVE for this and future projects improving these applications, and also improve the ability of support to administer and deploy changes outside of project work.

Success Criteria

The success criteria for each enhancement request / issue will be logged by CAM in jira.

The overall success criteria for the project is that as many of the enhancements can be delivered within the project timescale and budget as possible.

Amendments to Standard Methodology

A number of changes to the standard methodology have been implemented for STU246 and STU247 and have been found to work well, and so this approach will be repeated in this project.

• CAM will take on the Business Analyst role, and will detail the requirement, test conditions and success criteria in the jira log, with screenshots to support developer understanding.
• The documentation produced will be commensurate with that normal for support, rather than for the full software project. Each jira will have its own implementation plan if needed; the majority will use Bamboo for deployment.
• There will be no PPBR stage, rather Applications Management will peer test the changes in DEV before agreeing promotion to TEST. Applications Management will then check the changes are in TEST and pass to CAM for testing, so there will be no formal PPIR meeting or milestone.