Penalty and advance

• Penalty and advance features added for consumers (Note: penalty/advance can be disabled from MDMS for a particular tenant)

Collect advance amount

• Advance amount collection enabled (Note: Can be disabled from MDMS)

Father/husband column in the household register

• Additional column added in Household Register screen and PDF.

Receipt and bill enhancements and fixes

• Advance and penalty fields added

• Localisation issue fixed

Dashboard data and graph data mismatch fixes

• Due to the data mismatch, from two APIs, for both the graph and table, the data is taken from a single API

APK fixes

• APK was showing a white screen in Android > 12, Fixes

Penalty configuration change

ws-services-calculation

Penalty Change

Added new penalty taxhead

Access Control

Updated actions-test.json

Updated roleactions.json

Updated actions-test.json

Penalty and Advance Enabled

BillingService

Enabled Penalty and Advance

Role added

Added role

Enabled Time penalty

BillingService

Enabled Time penalty

Added Business service json in Billing service

BillingService

Added Business service json in Billing service for enable and disable Advance and penalty in Tenant level

Added TaxHeadMaster json in Billing service

BillingService

Added TaxHeadMaster json in billing service for enable and disable advance and penalty in tenant level

Added TaxPeriod json in Billing service

BillingService

Added TaxPeriod json in Billing service for enable and disable advance and penalty in tenant level

Penalty Type changing

ws-services-calculation

Updated the penalty type in this path - users can modify based on the requirement in tenant (verify document for penalty type)

Demand Penalty Details and action roles

Added demand penalty details and action roles

By Enabling and disabling this we can able change the payment type from state level to tenant level

By enabling and disabling this we can change the payment type from state level to tenant level

App Force Update

We need to update the version in MDMS with the latest version to be deployed in PlayStore or AppStore

Advance and Penalty changes

Code changes related to advance and penalty parameters

egov-persister

Syntax correction

pdf-service

data config changes for advance and penalty

format config changes for advance and penalty

dashboard-analytics

1

Development is completed for all the features that are part of the release.

Yes

@Sandhya K

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

@Vasanth Kumar

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

@Satish N @Vasanth Kumar

Sprint Showcase (12-Dec-2022) and internal team demo(14-Sep-2022 ) with Product owner completed

4

UI/UX Audit review by UX Architect is completed along with feedback incorporation for any changes in UI/UX.

Yes

@Ramkrishna Sahoo @Antriksh Kumar

5

Incremental demos to the product owners are completed as part of the sprint and feedbacks are incorporated.

Yes

@Sandhya K

@Vasanth Kumar

Multiple Incremental demos (8-Sep-22 & 14-Sep-22) 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

@Vasanth Kumar

QA sign-off done (20-Sep-22)

7

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

Yes

@Sandhya K

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

@Vasanth Kumar. @Nirupama

UAT regression test cases. Signed off on 8-Dec-2022

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

@Vasanth Kumar

No API Automation for mgramSeva

10

The API backward compatibility testing is completed.

No

@Vasanth Kumar

No API Automation for mgramSeva

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

@Nirupama Karanam @Satish N

QA Communication was done on 28-Nov-22 UAT Sign off was on 5-Dec-22 Product sign-off was on 9-Dec-22

12

UAT Product Signoff communication is received from the Product owners along with the release notes and User guides (if applicable).

Yes

@Satish N

Signed off on 9-Dec-2022

13

The GIT tags and releases are created for the code changes for the release.

Yes

@Sandhya K

14

Verify whether the Release notes are updated

Yes

@Sandhya K

15

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

Yes

@Vasanth Kumar

16

Verify whether all MDMS, Configs, InfraOps configs updated.

Yes

@snehal.gothe @Sandhya K

17

Yes

@Sandhya K

@Anjoo Narayan

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

@Vasanth Kumar

19

Verify whether the UAT credentials sheet is updated with the details of new Users and Roles if any

Yes

@Vasanth Kumar

It will be internally shared.

20

Verify whether all the localisation data was added in UAT including Hindi and updated in Release Kits.

Yes

@Vasanth Kumar

21

Verify whether the product release notes and user guides are updated and published

Yes

@Satish N

22

The Demo of released features is done by the product team as part of the Sprint/Release showcase.

Yes

@Satish N

Release showcase done on 12-Dec-22

23

Technical and Product workshops/demos are conducted by the Engineering and Product team to the implementation team (Impel handover)

Yes

@Satish N @Arindam Gupta

Workshop Oct17, 22

24

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.

NA

25

Architect SignOff and Technical Quality Report

No

@Ghanshyam

No dedicated Architect to mgramseva & Phani has done code review during the dev cycle. As discussed in the show case, Ghanshyam would be doing the sign-off. Sandhya will be coordinating with ghanshyam on this. This will be taken after the release since we are already late for the product release.

26

Success Metrics and Product Roadmap

Yes

@Satish N

27

Adoption Metrics

Yes

28

Program Roll-out Plan

Yes

29

Impel checklist

Yes

@Arindam Gupta

30

Impel roll-out plan

Yes

@Arindam Gupta

31

Gate 2

Yes

Gate 2 Review is scheduled on 14-Dec-2022

32

The Internal release communication along with all the release artefacts are shared by the Engineering team.

Yes

@Sandhya K

Communication will be done by Engineering team 14-Dec-2022

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.

No

GTM Team