Release Checklist
Checklist | Yes/No/Partially | Reference Link/ETA | Owner | Reviewer | Remarks |
The development is complete for all the features that are part of the release. | Yes | ||||
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet. | Yes | ||||
The incremental demo of the features showcased during the sprint showcase and feedback is incorporated. If possible, list out the JIRA tickets for feedback. | Yes | 12-June-24 | |||
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX. | Yes | 30-May-24 | Mail has been communicated to Andrew Jones for UI/UX audit | ||
QA sign-off is completed by the QA team and communicated to product owners. All the tickets’ QA sign-off status is updated in JIRA. | Yes | Lata | |||
UI, and API technical documents are updated for the release along with the configuration documents. | Yes | ||||
UAT promotion and regression testing from the QA team is completed. The QA team has shared the UAT regression test cases with the product owners. | Yes | Lata | |||
The API backward compatibility testing is completed. | Yes | No breaking changes are made. | |||
The communication is shared with product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a product sign-off within one week of this communication. | Yes | 4-June 24 | As part of admin console product owner sign-off has been completed | ||
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable). | Yes | 20-June-24 | As part of admin console product owner sign-off has been completed | ||
The GIT tags and releases are created for the code changes for the release. | Yes | ||||
Verify whether the release notes are updated. | Yes | Link | |||
Verify whether all the UAT builds are updated along with the GIT tag details. | Yes | Link | Lata | ||
Verify whether all MDMS, configurations, infra-ops configurations are updated. | Yes | ||||
Verify whether all docs will be published to http://health.digit.org by the Technical Writer as part of the release. | Partially | ||||
Verify whether all test cases are up-to-date and updated along with the necessary permissions to view the test cases sheet. The test cases sheet is verified by the test lead. | Yes | ||||
Verify whether the UAT credentials' sheet is updated with the details of new users and roles, if any. | Yes | Link | |||
Verify whether all the localisation data was added in UAT, and updated in the release kits. | Yes | No functional changes were made | |||
Verify whether the product release notes and user guides are updated and published. | No | No product functional changes were made | |||
The demo of the released features is done by the product team as part of a sprint/release showcase. | Yes | 20-June-24 | Demo has been give as a part of the HCM Console release | ||
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover). | Yes | ||||
Architect sign-off and technical quality report. | Yes | ||||
Verify Bug Bash has been completed | Yes | 31-May-24 | |||
Gate 2 | 21-Jun-24 | ||||
The internal release communication along with all the release artefacts are shared by the engineering/ product teams. |
Last updated