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 | Kalyan | Code merged to master branch on May 12th. | ||
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet. | Yes | Guruprasad | Mrunal | Signed-off by Roshan/ Mrunal. | |
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 | PGR - April 26th. HRMS & Mobile Offline Reports - May 11th. | |||
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX. | Yes | Sai Neelakantan Bhanu | Andrew | PGR, Dashboard HRMS - UX audit complete and high priority issues fixed. | |
Incremental demos to the product owners are completed as part of the sprint, and feedback is incorporated. | Yes | Guruprasad | Mrunal | PGR - April 26th. HRMS & Mobile Offline Reports - May 11th. | |
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 | Guruprasad | PGR - Provided on April 28th. Dashboard v1.1 - Provided on May 2nd. HRMS and Mobile Offline reports - Provided on May 10th. | ||
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. QA team has shared the UAT regression test cases with the product owners. | Yes | Guruprasad | PGR - Provided on April 28th. Dashboard v1.1 - Provided on May 2nd. HRMS and Mobile Offline reports - Provided on May 10th. | ||
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 | Done for FLW App. | |||
The API backward compatibility testing is completed. | Not applicable | Reason: This is the first version of product. | |||
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 | Frontline Worker's App - On March 23rd. Complaints - On April 28th. Dashboard v1.1 - On May 2nd. HRMS and Mobile Offline reports - On May 10th. | Kalyan | ||
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable). | Yes | Frontline Worker's App - On March 23rd. User Management - On April 28th. Dashboard - On May 2nd. HRMS and Mobile Offline reports - On May 10th. | Mrunal | Kalyan | |
The GIT tags and releases are created for the code changes for the release. | Yes | Roopesh/ Kavi | Need to be created for the flutter component. | ||
Verify whether the release notes are updated. | Yes | Roopesh/ Kavi | Kalyan | Tech release notes are updated. | |
Verify whether all the UAT builds are updated along with the GIT tag details. | Yes | Roopesh/ Kavi | |||
Verify whether all MDMS, configurations, infra-ops configurations are updated. | Yes | Roopesh/ Kavi | All configurations are part of the master promotion document. | ||
Yes | Mihika | Signed-off. | |||
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 | Guruprasad | 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 | Guruprasad | Signed-off. | |
Verify whether all the localisation data was added in UAT, and updated in the release kits. | Yes | Roopesh | This should be part of the release kit. This will be shared internally with the team. | ||
Verify whether the product release notes and user guides are updated and published. | Yes | Mrunal | Jojo | Signed-off. | |
The demo of the released features is done by the product team as part of a sprint/release showcase. | Yes | Mrunal | Done. | ||
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover). | Yes | Kalyan | Prasanna | ||
Architect sign-off and technical quality report. | Yes | Roopesh | Signed-off. | ||
Product roadmap and success metrics | Yes | Mrunal | Published. | ||
Adoption metrics | Yes | Ankit | Pradipta | Ankit has shared the draft for this. However, final discussion is pending with NMCP. | |
Programme roll-out plan | Yes | Ankit | Pradipta | ||
Implementation checklist | Yes | Aparna | Elzan | ||
Implementation roll-out plan | Yes | Aparna | Elzan | ||
Gate 2 | Ankit | ExCos | Scheduled on June 9th. | ||
The internal release communication along with all the release artefacts are shared by the engineering/product teams. | Mrunal | 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. | Not applicable currently. | This is not the final release. Hence, external communication is not required. |
Last updated