Gate 2 Release Checklist
Last updated
Last updated
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
| 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
The code freeze occurred on Jun 20
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet.
Yes
@shreya
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
Jagan and Team
We had the following incremental demos with the product owner:
HCM Campaign Screens Preview: April 10, 5:00 – 5:30pm
HCM Campaign Manager Demo: April 15, 2:00 – 3:00pm
End-to-End Flow of HCM Admin Console: April 29, 3:00 – 4:00pm
Final HCM Admin Console Demo: May 10, 4:00 – 4:45pm
Incremental Performance Improvement on HCM Admin Console Demo: Jun 11, 3:00 – 4.00pm
Performance Improvement Changes on HCM Admin Console Demo: Jun 14, 12:00 – 12:45pm
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX.
Yes
Nabeel
@ AndrewJones
UI/UX audit done, and feedbacks incorporated UI/UX Audit 27 May
Incremental demos to the product owners are completed as part of the sprint, and feedback is incorporated.
Yes
Shreya
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
shreya
QA sign-off was completed on May 9, 2024.
UI, and API technical documents are updated for the release along with the configuration documents.
Yes
Ashish Nabeel
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
Shreya
UAT sign-off was completed on May 23, 2024.
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.
Yes
Shreya
The API backward compatibility testing is completed.
shreya
Not Applicable, since it is new service
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
Yes
shreya
UAT sign-off was completed on May 23, 2024.
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable).
Yes
The GIT tags and releases are created for the code changes for the release.
Yes
Verify whether the release notes are updated.
Yes
Ashish
Verify whether all the UAT builds are updated along with the GIT tag details.
Yes
Ashish
Verify whether all MDMS, configurations, infra-ops configurations are updated.
Yes
Ashish
Verify whether all docs will be published to https://egov-digit.gitbook.io/0.1 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
Shreya
Verify whether the UAT credentials' sheet is updated with the details of new users and roles, if any.
This should not go into Gitbook as this is internal to eGov.
Shreya
Verify whether all the localisation data was added in UAT, and updated in the release kits.
shreya
Verify whether the product release notes and user guides are updated and published.
The demo of the released features is done by the product team as part of a sprint/release showcase.
Yes
Yes
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover).
Yes
@Ankit Sharma
HCM Admin Console Final Handover to Impel Team Date: May 30
HCM Admin Console Incremental Handover Date: May 16 HCM Admin Console Final Handover Date: Jun 21
Architect sign-off and technical quality report.
Verify Bug Bash has been completed
Yes
Bug bash done on 21 May 2024
Product roadmap and success metrics.
Yes
Yes
Vignesh
Adoption metrics.
Ankit
Programme roll-out plan.
Ankit
Ranjani
Implementation plan/checklist
Ankit
Ranjani
Gate 2
Yes
Vignesh
ExCos
June 20
The internal release communication along with all the release artefacts are shared by the engineering/ product teams.
Vignesh
To be shared post Gate 2