Retired
Aims of the Retired phase
Core goal: to retire the service without impeding users
Your service may have several reasons for retirement - being replaced by a new service, changes to policy or the service becoming obsolete. It’s important to still consider user needs in retiring a service.
Key work
- Carry out user research to determine how the service retirement should fit into the user journey (e.g. are they redirected elsewhere, or is explanatory content required?)
- Create redirection content (including technical implementation)
- Carry out necessary administration to retire the service
Templates (WIP)
- TBC
Core team
The core team required will be defined once the timeframe to decommission the service has been decided. If the user impact is not known, this team should include a user researcher.
Assurance requirements
DDTS Stage Gate 5 (Operations Review and Benefits Realisation) [Optional]
It may be relevant to rerun DDTS Stage Gate 5. This would be initiated by the Programme Manager, Programme Delivery Manager or the Senior Responsible Office (SRO) attached to the project.