Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(dev): Initial write up for managing legacy #2

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

chore(dev): Initial write up for managing legacy #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
19 changes: 19 additions & 0 deletions managing-legacy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.