Overview
Background
This project will manage developments to be made to the Peace Agreements web application and database PA-X (https://www.peaceagreements.org/) for 24/25. The application has been developed over the last 10 years by Development Services to support and publish research carried out by the Political Settlement Research Programme, (now PeaceRep), and the School of Law. . Every year, PeaceRep put budget towards additional improvements and a Senior Analyst Developer in the Software Development team is employed to carry out the work on the PA-X. 154 days have been pledged this year, up to the end of March 2025.
John Allison had been the primary contact/developer for the work up and remains involved as Senior Supplier. The main purpose of the project is to maintain a view on the Jira log to assist with the organisation and prioritisation of work on PA-X, and budget monitoring (including regularly reporting to the budget holder).
Scope
- Using the Jira Backlog to manage all work on the Peace Agreements database
- Ensuring all work is organised and prioritised, and deliverables agreed on a fortnightly basis
- Ongoing Production handover
- Python upgrade decommissioning following work to move the Amnesties database (agreed with the INF169 project) No work will be charged to the HSS048 project for this.
Out of scope
- Decommissioning of servers hosting Amnesties db
Objectives and Deliverables
Objectives and Deliverables | Requirement |
---|---|
O1. Organise Jira Backlog | |
D1.1 All JIRA tickets are organised/prioritised | Must |
O2. Deliver continuous improvements Sprints | |
D2. Deliver improvements in fortnightly sprints | Must |
O3. Production handover | |
D3.1. Complete TAD and SDS documents | Must |
D3.2. Handover to Production | Must |
O4. Python Upgrade Decommissioning | |
D4.1. Complete Amnesties DB move to new Python server | Must |
D4.2. Pass decommissioning request to Production Management | Must |
Benefits
- Jira Backlog will keep a record of all work planned/completed
- Supports sponsor in meeting funding requirements
- Budget updates shared regularly to ensure no overspend occurs
- Creates better support for future issues and improvements
Success Criteria
- Stakeholders know what improvements are in the pipeline, what order / when they will be delivered, how they will be resourced
- Continuous Improvements delivered to PA-X
- Business is satisfied with progress and communication
- Process for managing improvements established and handover to Production
Project Milestones
Stage | Milestone | Due Date | Previous Date | Complete | |
---|---|---|---|---|---|
Initiate | Project Initiated | 04-Oct-2024 | No date available | No | |
Execute | Fortnightly Sprints Start - MAJOR MILESTONE (Continuous Improvements) | 31-Oct-2024 | No date available | No | |
Initiate | End of Planning - MAJOR MILESTONE | 14-Nov-2024 | 11-Oct-2024 | No | |
Execute | New Senior Software Developer starts | 18-Nov-2024 | No date available | No | |
Execute | Handover between Software Developers completed | 29-Nov-2024 | No date available | No | |
Deliver | Amensties DB Upgrade Completed & Decommissioning Started (MAJOR MILESTONE) | 17-Jan-2025 | No date available | No | |
Close | Project Closure - MAJOR MILESTONE | 31-Mar-2025 | No date available | No |