@Sl No | Checklist | Yes/No/Partially | Reference link | Owner | Reviewer | Remarks | |
1 | Development is completed for all the features that are part of the release. | Yes | Code is frozen by 14-APR-2023 | ||||
2 | Test cases are documented by the QA team, and reviewed by the product owners and test results are updated in the test cases sheet. | Yes | |||||
3 | The incremental demo of the features showcased during the sprint showcase and feedback incorporated. If possible list out the JIRA tickets for feedback. | Yes | |||||
4 | UI/UX Audit review by UX Architect is completed along with feedback incorporation for any changes in UI/UX. | Yes | UI/UX audit is done and review comments are incorporated. | ||||
5 | Incremental demos to the product owners are completed as part of the sprint and feedbacks are incorporated. | Yes | |||||
6 | QA signoff is completed by the QA team and communicated to the product owners. All the tickets QA signoff status is updated in the JIRA. | Yes | QA signoff was completed. | ||||
7 | UI, API Technical documents are updated for the release along with the configuration documents. | Yes | |||||
8 | 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 | |||||
9 | 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 analyzed and 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 | Not picked up in this release due to lack of resources. We do not have QA resource who can write automation scripts. | ||||
10 | The API backward compatibility testing is completed. | Yes | Use cases are run with the existing scripts, no new API structures changes are added in the release. | ||||
11 | The communication is shared with the product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a Product signoff within one week of this communication. | Yes | UAT sign-off was completed. | ||||
12 | UAT Product Signoff communication is received from the Product owners along with the release notes and User guides (if applicable). | Yes | All modules are signed off, release notes and user guides are updates | ||||
13 | The GIT tags and releases are created for the code changes for the release. | Yes | |||||
14 | Verify whether the Release notes are updated | Yes | |||||
15 | Verify whether all UAT Builds are updated along with the GIT tag details. | Yes | |||||
16 | Verify whether all MDMS, Configs, InfraOps configs updated. | Yes | Added as part of the builds sheet | ||||
17 | Verify whether all docs will be Published to http://urban.digit.org by the Technical Writer as part of the release. | Yes | |||||
18 | Verify whether all test cases are up to date and updated along with necessary permissions to view the test cases sheet. The test cases sheet is verified by the Test Lead. | Yes | |||||
19 | Verify whether the UAT credentials sheet is updated with the details of new Users and Roles if any | Yes | UAT credentials shared internally to product and implementation teams | ||||
20 | Verify whether all the localisation data was added in UAT including Hindi and updated in Release Kits. | Yes | |||||
21 | Verify whether the product release notes and user guides are updated and published | Yes | Product Owners | Release notes and user guides are published in gitbooks. | |||
22 | The Demo of released features is done by the product team as part of the Sprint/Release showcase. | Yes | Yes - all features of 2.8 are demoed to the eGov team. | ||||
23 | Technical and Product workshops/demos are conducted by the Engineering and Product team to the implementation team (Implementation handover) | Yes | Migration process has been explained, all the Docs are added to the master migration doc based on feedback from impel team | ||||
24 | Architect SignOff and Technical Quality Report | Yes | Sign off is given with privacy disabled and encryption process disabled for W&S,PT modules. Redesign of privacy will be taken up by DPG based on the shortcomings shared in Tech council. | ||||
25 | Success Metrics and Product Roadmap | Product road map post digit 2.8 is not clear yet as we have less visibility and trimming down the operations/resources in urban team. | |||||
26 | Adoption Metrics | Adoption Metrics added in Program Roll Out Page | |||||
27 | Program Roll-out Plan | ||||||
28 | Implementation checklist | Yes | Prepared. | ||||
29 | Implementation Roll-out plan | Yes | |||||
30 | Gate 2 | Yes | |||||
31 | The Internal release communication along with all the release artefacts are shared by the Engineering/Product team. | Yes | |||||
32 | Plan for upgrading the staging/demo instance with the release product - within 2-4 weeks based on the period where no demos are planned from staging for the previous version of the released product. | In progress | After upyog upgradation, will start this task after getting confirmation from marketing team. | ||||
33 | The Release communication to partners is shared by the GTM team and the Webinar is arranged by the GTM team after the release communication - within 2-4 weeks of the release. |
Page Comparison
Manage space
Manage content
Integrations