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.

Timelines

Q2 2023 (w/c May15, 2023): Field testing

TBD: Tentative - 2023-end.

Tentative Q1 24

Value bundle

Value delivered

Feature list

Feature list

Feature list

Feature list

Campaign setup

Enable system administrators and program managers to set up the platform quickly, easily configure roles and role-based permissions, update master data, and manage users.

1. Campaign manager: Create and update campaigns (single round campaigns). 2. User management with UI. 3. Out-of-the-box standard dashboards.

1. Campaign manager with support for multi-round campaigns. 2. Forms engine.

1. Campaign manager with UI. 2. UI for setting up custom dashboards. 3. Forms designer with UI.

1. Mobile Device Management

Service delivery

Mobile app with a user-friendly design and easy, intuitive navigation. This will guide the field teams to easily register eligible beneficiaries, and deliver the healthcare intervention with built-in checks that enforce data collection protocols and validations to avoid data entry errors.

1. Register new households and individuals. 2. Search registered beneficiaries from the list. 3. Update service delivery information against a beneficiary. 4. Decision support for the resource delivery of LLIN's. 5. Creation of household and individual registries. 6. Re-use beneficiary data from the registries.

1. Proximity-based search using GIS map on the mobile app. 2. Routing assistance to locate beneficiaries. 3. Support voucher generation and scanning for tracking service delivery. 4. Last-mile delivery tracking: Record stock received from the warehouse for delivery. 5. Adverse events reporting. 6. Enhance decision support logic for MDA campaigns.

1. Beneficiary eligibility checker. 2. Generation of due lists for multi-round campaigns. 3. In-app alerts and reminders to improve medication adherence.

Inventory management

Mobile app that enables the warehouse manager to capture the inflow and outflow of resources from the warehouse and monitor delivery data against consumption data to identify potential stock outs, wastage, fraud, as well as take corrective action.

1. Record stock receipts and issues. 2. Stock reconciliation to view the balance stock on hand.

Consumables management

Dashboards and reports

Enable program managers, supervisors and frontline workers to view key performance indicators for assessing campaign efficiency and effectiveness before, during, and after the campaign via near real-time dashboards and preemptive alerts for course corrections.

1. Offline mobile reports to view task completion and campaign coverage. 2. Offline mobile reports to asses the performance of frontline teams. 3. Out-of-the-box online web dashboard to view campaign coverage and efficiency indicators. 4. Export tabular reports from web dashboards.

1. Automate preemptive email/SMS notifications. 2. Automate report generation.

Configure rule-based alerts on dashboards with enhanced predictive analytics.

1. Online GIS-enabled web dashboards for real-time monitoring 2. Dashboard with basic rule-based prescriptive analytical support.

Training

Enable program managers and supervisors to track training progress, evaluate training attendees and provide on-demand refreshers to attendees. Ensure that the campaign staff is equipped and trained to perform their duties efficiently.

1. Capture PII, bank details and performance data of hired campaign staff for longitudinal tracking. 2. Creation of the staff registry.

1. UI to find and hire campaign staff from the staff registry to enable better skill-requirement match. 2. On-demand access to job-aids.

1. Training refreshers. 2. Pre and post evaluation of the training. 3. Track the status of the training sessions.

Payments

Enable program managers to decrease the time to pay frontline workers while increasing financial accountability and reducing fraud.

1. Manage attendance for the campaign staff. 2. View payment due for services delivered.

1. Automate invoice generation for incentive payments. 2. Automate payment to campaign staff 3. Track status of payment processing. 4. Send notification on payment completion.

SBCC/demand generation

Enable program managers, frontline workers and citizens to easily access and recieve SBCC messages digitally to improve disease awareness and decrease refusals.

1. On-demand access to IEC material within the mobile app.

1. Broadcast SMS for one-way messaging to beneficiaries. 2. Post service delivery surveys.

Grievances and complaints

Enable program managers and supervisors to ensure speedy and efficient resolution of complaints while providing them with an intuitive system that helps to initiate corrective actions in a timely manner.

1. Log grievances/complaints. 2. Manage complaints: View and resolve complaints. 3. Dashboards for viewing complaints and grievances.

1. Assign complaints to the appropriate actor for resolution. 2. Track the status of complaints. 3. Notification on complaint resolution.

1. Automatic prioritization of complaints from the list. 2. Auto-routing and escalation of complaints.

Planning

Enable program managers to improve the efficiency and effectiveness of the planning process by leveraging GIS systems and data from other sources to create planning templates that make it easy to generate, validate and share micro-plans.

Micro-planning: Template for capturing targets from the micro-plans.

Workflow management.

1. Macro-planning: Estimating population numbers and resource requirements. 2. Micro-planning: Input based template to generate micro-plans. 3. Micro-planning: Workflow to share micro-plans for reviews and approvals. 4. Micro-planning: Track the status of the micro-planning activity.

GIS-enabled micro-planning using digital maps.

Supervision

Enable supervisors to to track the campaign staff's adherence to campaign SOP's and protocols and record inspection details.

Submit supervision checklists.

In-app notifications to the field teams.

WhatsApp integration to enable a two-way communication.

Offline capability

Enable frontline teams to collect data in low and no internet areas.

1. Data collection in low/no internet areas. 2. Enable location services while offline to track GPS coordinates.

Peer-to-peer sync.

User experience delighters

Enable all frontline workers to do their best work by providing a feature set in the mobile application that enables the app to act as a co-pilot to help the user perform their tasks while improving technology adoption.

1. In-app walkthrough of the application. 2. Progress bar to monitor the work status. 3. Multi-language support. 4. Call help desk: SOS button.

Interoperability and integration

Enable the adoption of the HCM platform by allowing a hassle-free integration of the capabilities with widely-used applications.

Integration with DHIS2.

1. Interoperability with FHIR for data exchange. 2. Supply chain management: Integration with OpenLMIS. 3. Integration with other visualization tools like PowerBI, and Tableau. 4. Integration with Reveal.

Citizen's portal

Registration 1. Self-Registration for campaigns. 2. Appointment scheduling and booking.

Demand generation: 1. Post-service delivery surveys. 2. Help desk service for citizens.

Service delivery: 1. Download the certificates after receiving the health intervention. 2. Self-reporting of adverse events.

Grievances and complaints: 1. Log grievances/complaints regarding service delivery. 2. Feedback post issue resolution. 3. Track the status of complaints.