Organisation

Work/Task Breakdown

This is a purely technical project to upgrade the underlying code libraries used by our software - no business analysis is required in this context as there are no business changes in scope.  However, it would be beneficial to have a business analyst provide guidance on what business processes our business testers need to do as a result of a set of technical changes to a given set of screens in EUCLID.

1.     Identify the full set of changes that need to be made when migrating to jQuery 3.3.1.

2.     Identify all of the EUCLID screens that will require one or more of those changes to be made.

3.     Define iteration/release cycle

4.     Plan releases to the live environment. To include records for the acceptance sign off from all stakeholders involved (developers, business owner, SACS support/IS Apps Man) .

5.     Track the enhancement's achievements, issues, and next steps on the monthly project report.

6.     Define communication: involve IS Production and Operations Support, as well as users.

Resources, Skills and Costs

As above, we need a BA to assist in the formation of an appropriate testing plan but there a no proposed business changes to analyse.

Technical work will be progressed by two SSP developers working together within an agile development cycle.

Business testers will be needed to the degree identified by the BA.

We do not expect any need for additional infrastructure or changes to existing infrastructure as part of this project, therefore Development Technology have not been added specifically as stakeholders.  We probably will need DevTech bookings to copy files to servers but that is just a service booking so it should be sufficient to just keep Mark Lang advised of our release plan for booking purposes.

Project Governance

This project will be progressed in an agile way, therefore the team will granted delegated authority and be expected to self-organise under general guidance of the Product Owner.  Project planning, prioritisation and monitoring will be done in the normal ways (release planning, iteration planning, iteration review and iteration retrospective).  Monthly reporting will be used to summarise project progress to the wider stakeholder group.

Regular release planning will identify delivery milestones as the project progresses.

The Product Owner and Project Sponsor will review progress versus budget spent on a per-iteration basis to regularly assess the ability of the project to deliver within the approved budget.

Project Stakeholders

See https://www.projects.ed.ac.uk/project/sac069/communicationplan for explanation of the communication plan.

Project Estimations

Agile estimation will be used, and that data will allow the Product Owner and Project Sponsor to track progress.