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

The code freeze occurred on Dec 9th

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 @lata check and update the status

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

  1. Sprint Demo v0.3 Admin Console: Tuesday, October 15, 12:00 – 1:00pm

  2. Sprint Demo v0.3 Admin Console: Monday, October 28, 4:00 – 5:00pm

  3. Incremental Handover of HCM Console v0.3: Tuesday, November 5, 4:15 – 5:00pm

  4. Admin Console Sprint Demo: Wednesday, November 13, 5:00 – 6:30pm

  5. Incremental Handover of HCM Console v0.3 - Session 2: Friday, November 15, 4:30 – 5:00pm

  6. Impel Handover HCM Microplan & Console: Monday, November 25⋅3:30 – 4:30pm

We had the following incremental demos with the product owner:

UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX.

Yes

Bhavya

@ AndrewJones

UI/UX audit done, and feedbacks incorporated 1st review - 29oct

Follow up review - 12 Nov

@bhavya update the status and link

Incremental demos to the product owners are completed as part of the sprint, and feedback is incorporated.

Yes

Lata

@lata / satya add the dates of incremental handovers

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

Conditional QA Signoff on Nov 13, 2024

QA sign-off was completed on Nov 27, 2024.

UI, and API technical documents are updated for the release along with the configuration documents.

Yes

Nitish Bhavya

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

UAT Promotion: Nov 14 - Nov 16

UAT Testing Completion: Nov 27

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

Lata/

The API backward compatibility testing is completed.

Lata

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

Lata

Communication is shared with PO: Wed Nov 20

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

Nitish

Verify whether all the UAT builds are updated along with the GIT tag details.

Yes

Nitish

Verify whether all MDMS, configurations, infra-ops configurations are updated.

Yes

Link

Nitish

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

Lata

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.

Lata

Verify whether all the localisation data was added in UAT, and updated in the release kits.

Lata

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

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

Last updated

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.