Sl No | Checklist | Yes/No | Reference link | Owner | Remarks |
1 | Development is completed for all the features that are part of the release. | Yes | Development completed as a part of this release along with B&D module. | ||
2 | Test cases are documented by the QA team, 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 | Incremental demo’s and incremental sign-off are followed. | ||
4 | UI/UX Audit review by UX Architect is completed along with feedback incorporation for any changes in UI/UX. | No | Architect feedback in the form of bugs and improvements done all except BnD | ||
5 | Incremental demos to the product owners are completed as part of the sprint and feedbacks are incorporated. | Yes | Multiple Incremental demos were completed during the sprint cycle. | ||
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 | These docs will be Published to Gitbook within 2 working days of the release. | ||
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. | Yes | |||
10 | The API backward compatibility testing is completed. | Yes | |||
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 | |||
12 | UAT Product Signoff communication is received from the Product owners along with the release notes and User guides (if applicable). | Yes | Product sign-off received for the below :
-Common Search and lightweight create
10. Citizen Profile | ||
13 | The GIT tags and releases are created for the code changes for the release. | ||||
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 | |||
17 | Verify whether all docs will be Published to http://docs.digit.org by the Technical Writer as part of the release. | No | It will be done within a week post the release communication. | ||
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 | |||
20 | Verify whether all the localization 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 | National Dashboard and State DSS Release Notes 2.7 Common Features UI/UX Revamp 2.7 | OBPS release is not part of the this release due to the following UAT issues . Bug fixing and internal testing is in-progress. | |
22 | The Internal release communication along with all the release artefacts are shared by the Engineering team. | No | |||
23 | The Demo of released features is done by the product team as part of the Sprint/Release showcase. | Partially done | National Dashboard Demo is completed on Feb 25th 2022. Another Sprint showcase scheduled on May 27th 2022. | ||
24 | 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. | This will be done by GTM post to the Release communication from Engineering | |||
25 | Technical and Product workshops/demos are conducted by the Engineering and Product team based on the need from the implementation team and partners. | No | |||
26 | 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. |
Manage space
Manage content
Integrations
0 Comments