As Software Developer
I want to have a clear template for managing Service Manual and deprecation notices
So that all the future deprecation is correctly communicated in the Service Manual
Description
During the process of preparing the standardise documentation for the future releases it was identified that we need to create standard process for managing communication of deprecation or new components in Service Manual.
This template should be stored in Confluence and contains relevant tasks.
Refer to the page:
https://confluence.ons.gov.uk/display/SDC/Deprecation+Implementation+and+Release+Process
Acceptance Criteria
Template format is agreed between Dev team
Template is covering all the tasks necessary to prepare clear guidance about communication of deprecation or new components in Service Manual.
Documentation is stored in Confluence.
Visualisation/Input from UCD
Needs design input @MagdalenaLarge to review ticket to cover this requirement
Linked User stories/epics
Technical details (optional)
MVP (optional)
Sri & Precious looked into what should be the content and location in the Service Manual. It still needs to be reviewed with Dina.
Magda booked meeting with Team to discuss it on Thursday 26.09.
As Software Developer I want to have a clear template for managing Service Manual and deprecation notices So that all the future deprecation is correctly communicated in the Service Manual
Description During the process of preparing the standardise documentation for the future releases it was identified that we need to create standard process for managing communication of deprecation or new components in Service Manual. This template should be stored in Confluence and contains relevant tasks. Refer to the page: https://confluence.ons.gov.uk/display/SDC/Deprecation+Implementation+and+Release+Process
Acceptance Criteria
Visualisation/Input from UCD Needs design input @MagdalenaLarge to review ticket to cover this requirement
Linked User stories/epics Technical details (optional) MVP (optional)