From 3ab9b6b51f9f5b16005d8dc68daa4897f914edc6 Mon Sep 17 00:00:00 2001 From: Chris Heathwood Date: Fri, 21 May 2021 15:26:37 +0100 Subject: [PATCH] chore(dev): Initial write up for managing legacy --- index.md | 1 + managing-legacy.md | 19 +++++++++++++++++++ 2 files changed, 20 insertions(+) create mode 100644 managing-legacy.md diff --git a/index.md b/index.md index 64a1d06..f584b1b 100644 --- a/index.md +++ b/index.md @@ -21,6 +21,7 @@ We iterate and refine them as we learn more. * [Process](process.md) * [Roles](roles.md) * [Service Delivery Teams](service-delivery-teams.md) +* [Managing Legacy](managing-legacy.md) * Coming soon... * Metrics & Measurement * Technology diff --git a/managing-legacy.md b/managing-legacy.md new file mode 100644 index 0000000..15d0ecd --- /dev/null +++ b/managing-legacy.md @@ -0,0 +1,19 @@ +## Managing legacy + +We take a pragmatic view to our legacy applications at the university, we have code that is many years old running important business functions for the University that needs to be maintained as well as maintaining future projects. + +This document is is very much inspired by the government guidance on [Managing legacy technology](https://www.gov.uk/guidance/managing-legacy-technology). + +We are making the transition over to [service delivery teams](service-delivery-teams.md) and as part of this transition we have split down the portfolio of applications across the relevant teams. + +This is currently mapped in a [trello board](https://trello.com/b/xfwEF8HJ/esg-service-ownership) and will be for the forseeable future. + +As part of service ownership a team will be expected to triage the applications in their portfolion and apply the [5 Rs](https://www.gov.uk/guidance/managing-legacy-technology#issues-that-stop-legacy-technology-migration) to each of those applications: + +* retain (do nothing) +* retire (drop) +* re-host (lift and shift) +* repurchase (shop and drop) +* re-platform (lift and shape) + +This work will involve the teams to gauge the maintenance involved in *retain* and almost certainly Product Owners and Business Analysts for any final decisions.