You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

Module

STOP TB Mobile App (TBMJA)

Release / Version

2.4 – Jira fix version 2.4

Purpose

Define and lock the scope of features/modules/fixes going into v2.4 so BSAs, Delivery Manager, Product and Engineering have one place to review owners, bandwidth and timeline before the sprint begins.

Total Jira tickets

50 (4 Closed, 46 open or in progress)

Page status

DRAFT for review – owners, estimates and dates are proposals pending team confirmation

Prepared on

09-Oct-2026

PRD reference

TBMJA PRD (v186)

Release 2.4 priorities

Priority focus for this release, in order:

  1. TPT module improvements – STOP-603, 604, 620, 351

  2. Contact Tracing module improvements – STOP-602, 618, 619 (plus the related Confirmed TB follow-up change STOP-600)

  3. Inventory module – additional fields – STOP-623

  4. Wrong-password attempts counter on login – STOP-599

  5. Dashboard change – STOP-606

  6. Everything else – registration and location capture, referrals and counselling, ABHA/ABDM, bug fixes, sync, platform tasks (sections F to K below)

Team and roles

Role

People

Mobile developers

Rohit, Deepak, Ankit, Ashutosh

Backend developers

Sehjot, Vishwa, Chetan

API developer

Vanitha

UI developer

Sneha

QA

Deepshika, Brijesh

Delivery Manager

Rupesh

Product Manager

Shivani

Engineering

Mithun

BSA

Madhava, Vanshika

Senior Manager

Syed

Assumptions used for owners and estimates

  • Owners are proposed from the nature of the work, not copied from Jira. Several tickets in Jira are currently assigned to people outside the delivery team list above (Puneet Sharma, Agraj Parashar) or to managers (Rupesh, Shivani, Syed); these are re-proposed below. Jira assignees have not been changed.

  • Estimates are indicative remaining effort in person-days (d) and need to be confirmed by each developer. "M" = mobile app work, "API" = backend/API work.

  • Capacity window: 12-Oct to 20-Nov-2026 = 30 working days. At an 80% focus factor this gives about 24 productive days per person. Public holidays and planned leave are not yet deducted.

  • Sneha is assumed to own pure UI/layout/copy changes; mobile developers own logic.

Scope by theme

A. P0 – TPT module

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-603

TPT follow-up: remove "Adherence to Medicines", rename ADR to "Side effects"

Highest

Todo/Open

Deepak (M 2d), Vanitha (API 1d)

Deepshika (1.5d)

Build together with 600 and 604. Old records must still display.

STOP-604

TPT follow-up: replace outcome status options; "Other" becomes optional Remarks

Highest

Todo/Open (unassigned)

Deepak (M 4d), Vanitha (API 2d)

Deepshika (3d)

5 open clarifications (outcome mapping, date rules, removed "Developed active TB" redirect, Remarks limit, migration of old values). Blocks start.

STOP-620

TPT: "Start TPT" and "TPT Follow Up" buttons, 6 regimens, first-visit details in follow-up

Highest

Todo/Open (unassigned)

Deepak (M 6d), Vanitha (API 2d)

Deepshika (3d)

4 open questions (regimen month mapping, 250–500 words rule, default instruction text, follow-up gating).

STOP-351

Search bar in ADR (treatment follow-up), ADR of TPT follow-up, Key population and risk factors

Low

Todo/Open (Shivani)

Deepak (M 2d)

Deepshika (1d)

Wording must change from "ADR" to "Side Effects" (per 600/603). Do after 603.

B. P0 – Contact Tracing module

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-618

Add "Household" option, view/edit/update after submit, "Any other Significant Information" (500 words)

Highest

Todo/Open (Rupesh)

Ankit (M 6d), Vishwa (API 2d)

Brijesh (3d)

Open question: should Household reuse the existing Members screen?

STOP-602

HHC tracing follow-up: Referred to = PHI / TB Camp, Remarks, auto Date, "Recommend for ATT Treatment"

Medium

Todo/Open (Rupesh)

Ankit (M 3d), Vishwa (API 1d)

Brijesh (2d)

Test both Counsellor and Surveillance Officer roles. Old referral values (TU/DH/CHC/PHC, DOTS) must still display.

STOP-619

Enable household-member "follow-up" button for Surveillance Officer role

Highest

Todo/Open (unassigned)

Ankit (M 1.5d)

Brijesh (1d)

Blocker question: "Surveillance Officer" is not in PRD roles. Does the role exist in the app or must it be created?

STOP-600

Confirmed TB follow-up: rename title, remove "Adherence to Medicines", ADR to "Side Effects"

Medium

Todo/Open (Rupesh)

Ankit (M 3d), Vishwa (API 1d)

Deepshika (2d)

Related change to TPT; keep labels consistent with 603.

C. P0 – Inventory module

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-623

Additional Improvements in Inventory Modules (additional fields)

Highest

Todo/Open (Rupesh)

Ashutosh (M 5d), Sehjot (API 3d)

Brijesh (3d)

Ticket has no description or field list. Estimates are placeholders (TBD) until Product (Shivani) provides the field specification.

D. P0 – Login: wrong-password attempts

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-599

Wrong-password error should show remaining attempts (max 5)

High

Todo/Open (Puneet)

Ashutosh (M 1.5d), Vanitha (API 2d)

Deepshika (1.5d)

Lockout message after attempt 5 is still TBD. Decide whether to show attempts for a non-existent username (security). Backend must expose remaining count.

E. P0 – Dashboard

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-606

Screening Coverage Summary: "Total Eligible Population for TB Screening" with demographic breakdown

Low

Todo/Open (unassigned)

Ashutosh (M 4d), Vishwa (API 1.5d)

Deepshika (2d)

3 open clarifications (definition of eligible population, filter rule, replace or sit alongside STOP-500 breakdown). Depends on STOP-500 (2.3, in QA). Jira priority is Low but the release priority list places it in P0.

F. Registration and location capture

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-509

Populate village master with PIN codes

Medium

Ready for Development (Puneet)

Vishwa (API/data 3d)

Deepshika (1d)

Blocks STOP-412. Start first. Villages without a PIN code must be listed to Product.

STOP-412

Pincode and Residential Area captured once per village (supersedes GPS approach STOP-308)

Highest

Todo/Open (Sehjot)

Rohit (M 5d), Sehjot (API 2d)

Deepshika (3d)

Depends on 509. STOP-404 depends on this.

STOP-404

Auto-select "Elderly" (60+) and "Urban Slum" in Key Population / Risk Factors

Medium

In Development (Deepak)

Deepak (M 2d remaining)

Brijesh (1d)

Urban Slum rule needs Residential Area from 412. Confirm villages are not mixed slum / non-slum.

STOP-414

Location capture changes (Digipin only, progress bar, edit location)

High

In Development (Puneet)

Deepak (M 6d), Sehjot (API 1d)

Brijesh (3d)

Dev owner changes from Puneet; confirm hand-over status with Puneet.

STOP-408

Auto population of mobile number from HH registration

High

Todo/Open (Rohit)

Ashutosh (M 2d)

Brijesh (1d)

Build with STOP-165.

STOP-165

Mobile number checkbox in HH registration

High

Todo/Open (Ashutosh)

Ashutosh (M 2d)

Brijesh (1d)

Same screen as 408.

STOP-171

Village name as default address

High

Todo/Open (Ankit)

Ankit (M 1d)

Brijesh (0.5d)

Check against GPS/address behaviour in 412 and 414.

STOP-144

Handling locked-door cases in HH enumeration

High

Todo/Open (Puneet)

Ashutosh (M 5d), Sehjot (API 1d)

Brijesh (2d)

Needs a "door locked" flag on the HH record.

STOP-164

Anthropometry screen changes

High

Todo/Open (Agraj)

Ankit (M 1d), Sneha (UI 1d)

Brijesh (1d)

Group with 433 (Examine button behaviour).

STOP-433

Examine button state reflects complete form submission

Low

Todo/Open (Ashutosh)

Ankit (M 1.5d)

Brijesh (0.5d)

Do with STOP-164.

STOP-581

Update "Type of House" options

Medium

Todo/Open (Rupesh)

Sneha (UI 1.5d)

Brijesh (1d)

"Other" field: letters only, 50 chars, speech-to-text. A mobile dev may need to pair on speech-to-text.

STOP-583

Update "Primary source of fuel used for cooking" options

Medium

Todo/Open (Rupesh)

Sneha (UI 1d)

Brijesh (0.5d)

Dropdown change, mandatory, single select.

STOP-557

District, Block and Village names blank for 222 records

Highest

Todo/Open (Vishwa)

Vishwa (API/data 2d)

Deepshika (1d)

Data fix plus root-cause check so it does not recur.

G. Referrals, counselling and TrueNat

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-576

New TB Screening questions: Abnormal functionality not showing in 2.3.25

Highest

Todo/Open (Ankit)

Ankit (M 3d)

Brijesh (1.5d)

Regression from 2.3.25; fix early.

STOP-528

Beneficiary not moving to Liquid Culture referral card

High

Todo/Open (Ankit)

Ankit (M 2d)

Brijesh (1d)

STOP-506

Add "Clinical Assessment and Diagnosis" referral queue

Medium

Todo/Open (Deepak)

Rohit (M 4d)

Brijesh (2d)

Re-assigned from Deepak to balance load.

STOP-504

NPY and DOTS helper text in Counselling Section C

Medium

Analysis (Sehjot)

Sneha (UI 1.5d)

Brijesh (0.5d)

Hindi translation must be provided by Product before release.

STOP-552

TrueNat: close test order when test not conducted

Low

Pending QA

Dev complete

Brijesh (1.5d)

STOP-553

TrueNat: auto-close open orders at EoD

Low

Pending QA

Dev complete

Brijesh (1.5d)

H. ABHA / ABDM

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-136

ABDM M2 Phase 1 – General OPD flow

Highest

In Development (Rohit)

Rohit (M 8d remaining), Vanitha (API 6d)

Deepshika (6d)

Largest item. Remaining effort is an assumption; Rohit to confirm progress.

STOP-386

Unable to create ABHA on Play Store build

High

Analysis (Deepshika)

Vanitha (API 3d), Rohit (M 2d)

Deepshika (1.5d)

Needs dev investigation; currently sitting with QA.

STOP-182

"Yes" button not clickable for ABHA card download

High

In QA

Dev complete

Deepshika (1d)

STOP-524

ABHA screen UI breaks on tablet; consent text layout

Medium

Todo/Open (Rupesh)

Sneha (UI 2d)

Brijesh (1d)

STOP-243

Create ABHA using Face authentication

Low

Todo/Open (Rohit)

Rohit (M 8d), Vanitha (API 2d)

Deepshika (3d)

STRETCH – not counted in bandwidth totals. Recommend moving to 2.5 unless capacity frees up.

I. Bugs, stability and sync

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-502

Card counts (All HH / All Beneficiary / Non-Household) fluctuating

Highest

Analysis (Ashutosh)

Ashutosh (M 3d)

Deepshika (1.5d)

STOP-449

Android Wi-Fi captive-portal check disconnects on networks without internet validation

Highest

Todo/Open (Syed)

Deepak (M 3d)

Brijesh (1.5d)

Needs device/network setup for testing.

STOP-523

Incremental beneficiary sync for large datasets

High

Todo/Open (Rohit)

Rohit (M 6d), Chetan (API 4d)

Deepshika (4d)

High regression risk; test with more than 500 beneficiaries.

STOP-556

Wrong toast count for registered family members; inconsistent purple colour

High

Todo/Open (Agraj)

Ankit (M 0.5d), Sneha (UI 0.5d)

Brijesh (1d)

STOP-607

OK / Cancel buttons overlap in Chief Complaint popup

Low

Todo/Open (Ankit)

Sneha (UI 0.5d)

Brijesh (0.5d)

STOP-163

"Add HoF member" alert; HoF icon on card

High

Pending QA

Dev complete

Brijesh (1d)

STOP-593

Default UAT URL for Connect Camp Hub in UAT build

Medium

Pending QA

Dev complete

Brijesh (0.5d)

J. Platform, DevOps and performance

Ticket

Summary

Jira priority

Jira status

Proposed dev owner(s) and estimate

QA (est.)

Notes / dependencies

STOP-252

Performance testing of STOP_TB (reopened)

High

Reopened (Sehjot)

Sehjot (API 3d)

Deepshika (1.5d)

STOP-580

Push production builds via MDM (Intune); sunset Play Store releases

High

Todo/Open (Agraj)

Chetan (DevOps 3d)

Brijesh (1.5d)

Needs the production device group (Krishna) and 4–5 test devices.

STOP-491

Soft launch ID generator on 2 camp laptops

Low

Todo/Open (Syed)

Chetan (1.5d), Syed to coordinate

Brijesh (0.5d)

STOP-564

Local environment setup on Deepsikha's and Pratiksha's laptops

Highest

Todo/Open (Rupesh)

Rupesh to arrange (non-dev)

–

Prerequisite for QA handover.

K. Already Closed in 2.4

Ticket

Summary

Note

STOP-308

PIN code and address via GPS

Closed; superseded by STOP-412 (GPS unworkable offline).

STOP-397

Duplicate work orders / duplicate names on TrueNat

Closed

STOP-460

Optimise beneficiary photo size to prevent sync failures

Closed

STOP-582

House ownership radio button (Rented / Owned)

Closed

Developer bandwidth for 2.4

Capacity per person: about 24 productive days (30 working days × 80%), before holidays and leave. Effort excludes STOP-243 (stretch).

Mobile developers

Developer

Allocated tickets

Est. effort

Utilisation

Comment

Rohit

136, 412, 523, 386, 506

25d

~104%

Slightly over. ABDM (136) is the largest risk. Face authentication (243) not possible without dropping other work.

Deepak

603, 604, 620, 351, 404, 414, 449

25d

~104%

Owns the whole TPT stream; P0 portion (603, 604, 620, 351 = 14d) done first. Slightly over.

Ankit

602, 618, 619, 600, 576, 528, 171, 164, 433, 556

22.5d

~94%

Owns the Contact Tracing stream plus referral bugs.

Ashutosh

623, 599, 606, 502, 165, 408, 144

22.5d

~94%

Inventory, login, dashboard and registration fixes. 623 is an estimate placeholder.

Backend / API / UI

Developer

Allocated tickets

Est. effort

Utilisation

Comment

Vanitha (API)

136, 599, 386, 603, 604, 620

16d

~67%

Carries ABDM and TPT APIs.

Vishwa (Backend)

509, 557, 606, 602, 618, 600

10.5d

~44%

Has headroom; can take overflow from Vanitha.

Sehjot (Backend)

412, 623, 252, 144, 414

10d

~42%

Has headroom.

Chetan (Backend)

523, 580, 491

8.5d

~35%

Has headroom. Can support DevOps/MDM and sync.

Sneha (UI)

524, 581, 583, 504, 607, 164, 556

8d

~33%

Available for screen designs for TPT / Contact Tracing and Counselling UI (STOP-434).

QA

QA

Allocated tickets

Est. effort

With regression/UAT support (5d)

Utilisation in dev window

Deepshika

136, 182, 252, 351, 386, 412, 502, 509, 523, 557, 599, 600, 603, 604, 606, 620

34.5d

39.5d

~165%

Brijesh

144, 163, 164, 165, 171, 404, 408, 414, 433, 449, 491, 504, 506, 524, 528, 552, 553, 556, 576, 580, 581, 583, 593, 602, 607, 618, 619, 623

36d

41d

~170%

Key observation: QA, not development, is the bottleneck. Developers can finish in about 6 weeks, but two QAs need about 9–10 weeks of effort across the same scope.

Completion estimate (TBD)

All dates are TBD and will be firmed up once owners confirm estimates and open questions below are closed.

Milestone

Target (TBD)

Basis

Sprint start

Mon 12-Oct-2026

P0 dev complete (TPT, Contact Tracing, Inventory, Login, Dashboard)

~05-Nov-2026

Deepak's TPT stream is the longest P0 path (14d ÷ 0.8).

P0 QA complete

~13-Nov-2026

23.5d of P0 QA across two QAs.

Full scope dev complete / code freeze

~20-Nov-2026

25d highest individual load ÷ 0.8 focus.

Full QA sign-off including regression

~11-Dec-2026

QA-bound: ~77.5d QA effort ÷ 2 QAs ÷ 0.8.

2.4 complete build (release candidate) after QA

~15 to 18-Dec-2026 (TBD)

Includes regression, fixes and UAT with BSA.

Options to pull the date in (for discussion):

  • Release 2.4 as a P0-focused build first (about mid-Nov) and move the rest to a 2.4.1.

  • Move STOP-243 (Face authentication, Low) to 2.5.

  • Developers self-test and attach evidence on small UI tickets (581, 583, 607, 504, 164) to reduce QA load.

  • BSAs (Madhava, Vanshika) take UAT on form-option and copy tickets.

  • Backend headroom (Vishwa, Sehjot, Chetan) used for API test automation and overflow from Vanitha.

Open questions and blockers

#

Item

Needed from

Affects

1

Inventory "additional fields" – no description or field list in the ticket

Shivani / Madhava

STOP-623

2

TPT outcome clarifications (5 questions)

Shivani / Vanshika

STOP-604

3

TPT regimen mapping, "250–500 words" rule, default instruction text, Follow-up gating (4 questions)

Shivani

STOP-620

4

Does the "Surveillance Officer" role exist in the app? What else can it access?

Shivani / Madhava

STOP-619

5

Household option: same Members screen or new form?

Shivani

STOP-618

6

Eligible population definition, filter rule and relation to STOP-500 breakdown

Shivani / Vanshika

STOP-606

7

Lockout message after the 5th wrong attempt; show attempts for unknown usernames?

Shivani / Engineering

STOP-599

8

Village master PIN code data source; list of villages with no PIN

Product / Data team

STOP-509, STOP-412

9

Hindi translation of NPY / DOTS helper text

Product

STOP-504

10

Confirm hand-over of work from Puneet Sharma and Agraj Parashar (assigned in Jira but not in the delivery team list)

Rupesh / Mithun

144, 164, 414, 509, 556, 580, 599

11

Re-assign Jira owners to match this page (tickets currently with Rupesh, Shivani, Syed, Puneet, Agraj, and 4 unassigned: 604, 606, 619, 620)

Rupesh

All

12

Leave and public-holiday calendar for 12-Oct to 18-Dec

Rupesh

All dates

Risks

  • QA capacity is roughly 1.7× the dev-window capacity. Mitigations listed above.

  • TPT and Contact Tracing are blocked by unresolved PRD questions. Highest-priority tickets (604, 619, 620) are unassigned and still have open clarifications.

  • Sequencing dependencies: 509 → 412 → 404; 603 + 604 + 600 to be built together; 351 after 603.

  • Rohit and Deepak are above 100%; any slippage in ABDM (136) or TPT lands on the critical path.

  • STOP-623 estimate is a placeholder because there is no requirement.

Review and sign-off

Name

Role

Sign-off

Rupesh

Delivery Manager

Shivani

Product Manager

Madhava

BSA

Vanshika

BSA

Mithun

Engineering

Syed

Senior Manager

  • No labels