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		Kaviyarasan		Code merged to master branch on 14th Nov
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet.	Yes	link	Tumul	Mrunal/Vignesh	Vignesh Nayak
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	link	Tumul	Mrunal/Vignesh
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX.	Partially		Naveen	Andrew	impel pull from product should be done, will be reviewed by andrew on wednesday
Incremental demos to the product owners are completed as part of the sprint, and feedback is incorporated.	Yes	link	Tumul	Mrunal/Vignesh
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		Tumul	Kaviyarasan
UI, and API technical documents are updated for the release along with the configuration documents.	Yes		Kavi	Ghanshyam
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		Tumul
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	API Automation Script			No new automation scripts are done, due to lack of resource
The API backward compatibility testing is completed.	Yes		Tumul		Beneficary tag, client audit details tested for backward comaptiability
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		Tumul	Mrunal/vignesh	communication done on 16th Nov
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable).	Yes		Mrunal/Vignesh	Kaviyarasan	Mrunal Surve
The GIT tags and releases are created for the code changes for the release.	Yes	link	Kaviyarasan
Verify whether the release notes are updated.	Yes	link	Kaviyarasan	Kaviyarasan	Tech release notes are updated.
Verify whether all the UAT builds are updated along with the GIT tag details.	Yes	link	Kaviyarasan
Verify whether all MDMS, configurations, infra-ops configurations are updated.	Yes	link	Kaviyarasan		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.	In progress	https://health.digit.org/	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	link	Tumul	Mrunal/Vignesh	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	Tumul		Signed-off.
Verify whether all the localisation data was added in UAT, and updated in the release kits.	Yes		Tumul	Kavi	release kit pending review
Verify whether the product release notes and user guides are updated and published.	Yes		Mrunal/Vignesh	Jojo	Signed-off.
The demo of the released features is done by the product team as part of a sprint/release showcase.	Yes		Mrunal/Vignesh		Done on 15th Nov
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover).	Yes	demo link https://docs.google.com/document/d/1v_PPVSRcpnrBw0NXIQNroRDXuewAxkCyUZqFN7wgyiw/edit?usp=sharing	Kaviyarasan	Vishal	Incremental releases were with the Impel team
Architect sign-off and technical quality report.	Yes		Kaviyarasan		Signed-off (Quality report pending)
Product roadmap and success metrics.	Yes		Mrunal/Vignesh
Adoption metrics.	Yes		Ankit	Pradipta
Programme roll-out plan.	Yes		Ankit	Pradipta
Implementation checklist.	Yes		Ankit	Elzan
Implementation roll-out plan.	Yes		Ankit	Elzan
Gate 2			Ankit	ExCos
The internal release communication along with all the release artefacts are shared by the engineering/ product teams.			Mrunal/Vignesh		To be shared post Gate 2.
Plan for upgrading the staging/demo instance with the release product within 2-4 weeks based on a period where no demos are planned from staging for the previous version of the released product.	Not applicable currently.
The release communication to partners is shared by the GTM team, and a webinar is arranged by the GTM team after the release communication, within 2-4 weeks of the release.					To be done by Dec 15th