Gate 2 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 | Code was frozen by 1st Mar 2024. | |||
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet. | Yes | Lata | All test cases are reviewed by the Product Owner and results have been updated in the sheet. QA sign-off is given accordingly. | ||
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 | Lata | Incremental demo given in the sprint and final demo was given on 27th Feb 2024 to the Product Owner. | ||
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX. | Yes | @ AndrewJones | UI/UX audit is done and review comments are incorporated. | ||
Incremental demos to the product owners are completed as part of the sprint, and feedback is incorporated. | Yes | Lata | Incremental demo given in the sprint and final demo was given on 27th Feb 2024 to the Product Owner. | ||
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 | All test cases are reviewed by the Product Owner and QA sign-off is given accordingly. | ||
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 | All test cases are reviewed by the Product Owner. | ||
API automation scripts are updated for new APIs or changes to any existing APIs for the release. API automation regression is completed on UAT; the automation test results are analysed and the necessary actions are taken to fix the failure cases. Publish the list of failure use cases with a reason for failure and the resolution taken to fix these failures for the release. | No | Lata | No new automation scripts are done. | ||
The API backward compatibility testing is completed. | No | Lata | No new API changes that breaks compatibility. | ||
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 | Lata | UAT Regression sign-off was completed on 27th FEB 2024. | ||
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable). | Yes | Product sign-off was completed on 27th Feb 2024. | |||
The GIT tags and releases are created for the code changes for the release. | Yes | Added a new git tag V1.3 | |||
Verify whether the release notes are updated. | Yes | Tech release notes are updated. | |||
Verify whether all the UAT builds are updated along with the GIT tag details. | Yes | All the builds are added with release tag V1.3 | |||
Verify whether all MDMS, configurations, infra-ops configurations are updated. | Yes | All configurations are part of the master promotion document. | |||
Verify whether all docs will be published to http://health.digit.org by the Technical Writer as part of the release. | Yes | Mihika | In progress - review pending | ||
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 | Lata | Signed-off. | ||
Verify whether the UAT credentials' sheet is updated with the details of new users and roles, if any. | Yes | This should not go into Gitbook as this is internal to eGov. | Lata | Signed-off. | |
Verify whether all the localisation data was added in UAT, and updated in the release kits. | Yes | Lata | All localisations added as part of the release. | ||
Verify whether the product release notes and user guides are updated and published. | Yes | Signed-off. | |||
The demo of the released features is done by the product team as part of a sprint/release showcase. | Yes | Release Showcase completed on 29th FEB 2024 | |||
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover). | In Progress | Kaviyarasan | Incremental handover was completed on jan-2(Bales scaner) Jan-10-2024(HF referral) 1-Feb(attendance) 14-Feb(flutter version upgrade) 1-Mar - Final handover Code showcase pending will be closed by 8-Mar-2024 | ||
Architect sign-off and technical quality report. | Yes | Signed-off | |||
Verify Bug Bash has been completed | Yes | conducted by 1-Mar-2024 | |||
Product roadmap and success metrics. | Yes | Vignesh | |||
Adoption metrics. | Yes | Ankit | |||
Programme roll-out plan. | Yes | Ankit | Ranjani | ||
Implementation plan/checklist | Yes | Ankit | Ranjani | ||
Gate 2 | Yes | Ankit | ExCos | Conducted on March 6 | |
The internal release communication along with all the release artefacts are shared by the engineering/ product teams. | Yes | Vignesh | To be shared post Gate 2. |
Last updated