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) |
Proposed sprint start | Fri 23-Oct-2026 (first full working week starts Mon 26-Oct) |
Page status | DRAFT for review – owners, bandwidth view and duration are proposals; not confirmed |
Prepared on | 09-Oct-2026 |
PRD reference | TBMJA PRD (v186) |
Release 2.4 priorities
Priority focus for this release, in order:
TPT module improvements – STOP-603, 604, 620, 351
Contact Tracing module improvements – STOP-602, 618, 619 (plus the related Confirmed TB follow-up change STOP-600)
Inventory module – additional fields – STOP-623
Wrong-password attempts counter on login – STOP-599
Dashboard change – STOP-606
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
No effort estimates are included. The team has not yet estimated individual tickets. Everything below about bandwidth and duration is based on the number of tickets per person and the kind of work involved, and is deliberately approximate.
Owners are proposed from the nature of the work, not copied from Jira. Several tickets are currently assigned in Jira 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.
Sneha is assumed to own pure UI/layout/copy changes; mobile developers own logic.
Public holidays and planned leave are not yet deducted. Diwali falls around 8-Nov-2026 and the festival period will reduce availability in late October and November (to be confirmed against the company holiday calendar).
Scope by theme
A. P0 – TPT module
Ticket | Summary | Jira priority | Jira status | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
TPT follow-up: remove "Adherence to Medicines", rename ADR to "Side effects" | Highest | Todo/Open | Deepak (Mobile), Vanitha (API) | Deepshika | Build together with 600 and 604. Old records must still display. | |
TPT follow-up: replace outcome status options; "Other" becomes optional Remarks | Highest | Todo/Open (unassigned) | Deepak (Mobile), Vanitha (API) | Deepshika | 5 open clarifications (outcome mapping, date rules, removed "Developed active TB" redirect, Remarks limit, migration of old values). Blocks start. | |
TPT: "Start TPT" and "TPT Follow Up" buttons, 6 regimens, first-visit details in follow-up | Highest | Todo/Open (unassigned) | Deepak (Mobile), Vanitha (API) | Deepshika | 4 open questions (regimen month mapping, 250–500 words rule, default instruction text, follow-up gating). | |
Search bar in ADR (treatment follow-up), ADR of TPT follow-up, Key population and risk factors | Low | Todo/Open (Shivani) | Deepak (Mobile) | Deepshika | 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) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
Add "Household" option, view/edit/update after submit, "Any other Significant Information" (500 words) | Highest | Todo/Open (Rupesh) | Ankit (Mobile), Vishwa (API) | Brijesh | Open question: should Household reuse the existing Members screen? | |
HHC tracing follow-up: Referred to = PHI / TB Camp, Remarks, auto Date, "Recommend for ATT Treatment" | Medium | Todo/Open (Rupesh) | Ankit (Mobile), Vishwa (API) | Brijesh | Test both Counsellor and Surveillance Officer roles. Old referral values (TU/DH/CHC/PHC, DOTS) must still display. | |
Enable household-member "follow-up" button for Surveillance Officer role | Highest | Todo/Open (unassigned) | Ankit (Mobile) | Brijesh | Blocker question: "Surveillance Officer" is not in PRD roles. Does the role exist in the app or must it be created? | |
Confirmed TB follow-up: rename title, remove "Adherence to Medicines", ADR to "Side Effects" | Medium | Todo/Open (Rupesh) | Ankit (Mobile), Vishwa (API) | Deepshika | Related change to TPT; keep labels consistent with 603. |
C. P0 – Inventory module
Ticket | Summary | Jira priority | Jira status | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
Additional Improvements in Inventory Modules (additional fields) | Highest | Todo/Open (Rupesh) | Ashutosh (Mobile), Sehjot (API) | Brijesh | Ticket has no description or field list. Scope and size unknown until Product (Shivani) provides the field specification. |
D. P0 – Login: wrong-password attempts
Ticket | Summary | Jira priority | Jira status | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
Wrong-password error should show remaining attempts (max 5) | High | Todo/Open (Puneet) | Ashutosh (Mobile), Vanitha (API) | Deepshika | 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) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
Screening Coverage Summary: "Total Eligible Population for TB Screening" with demographic breakdown | Low | Todo/Open (unassigned) | Ashutosh (Mobile), Vishwa (API) | Deepshika | 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) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
Populate village master with PIN codes | Medium | Ready for Development (Puneet) | Vishwa (API/data) | Deepshika | Blocks STOP-412. Start first. Villages without a PIN code must be listed to Product. | |
Pincode and Residential Area captured once per village (supersedes GPS approach STOP-308) | Highest | Todo/Open (Sehjot) | Rohit (Mobile), Sehjot (API) | Deepshika | Depends on 509. STOP-404 depends on this. | |
Auto-select "Elderly" (60+) and "Urban Slum" in Key Population / Risk Factors | Medium | In Development (Deepak) | Deepak (Mobile) | Brijesh | Urban Slum rule needs Residential Area from 412. Confirm villages are not mixed slum / non-slum. | |
Location capture changes (Digipin only, progress bar, edit location) | High | In Development (Puneet) | Deepak (Mobile), Sehjot (API) | Brijesh | Dev owner changes from Puneet; confirm hand-over status with Puneet. | |
Auto population of mobile number from HH registration | High | Todo/Open (Rohit) | Ashutosh (Mobile) | Brijesh | Build with STOP-165. | |
Mobile number checkbox in HH registration | High | Todo/Open (Ashutosh) | Ashutosh (Mobile) | Brijesh | Same screen as 408. | |
Village name as default address | High | Todo/Open (Ankit) | Ankit (Mobile) | Brijesh | Check against GPS/address behaviour in 412 and 414. | |
Handling locked-door cases in HH enumeration | High | Todo/Open (Puneet) | Ashutosh (Mobile), Sehjot (API) | Brijesh | Needs a "door locked" flag on the HH record. | |
Anthropometry screen changes | High | Todo/Open (Agraj) | Ankit (Mobile), Sneha (UI) | Brijesh | Group with 433 (Examine button behaviour). | |
Examine button state reflects complete form submission | Low | Todo/Open (Ashutosh) | Ankit (Mobile) | Brijesh | Do with STOP-164. | |
Update "Type of House" options | Medium | Todo/Open (Rupesh) | Sneha (UI) | Brijesh | "Other" field: letters only, 50 chars, speech-to-text. A mobile dev may need to pair on speech-to-text. | |
Update "Primary source of fuel used for cooking" options | Medium | Todo/Open (Rupesh) | Sneha (UI) | Brijesh | Dropdown change, mandatory, single select. | |
District, Block and Village names blank for 222 records | Highest | Todo/Open (Vishwa) | Vishwa (API/data) | Deepshika | 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) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
New TB Screening questions: Abnormal functionality not showing in 2.3.25 | Highest | Todo/Open (Ankit) | Ankit (Mobile) | Brijesh | Regression from 2.3.25; fix early. | |
Beneficiary not moving to Liquid Culture referral card | High | Todo/Open (Ankit) | Ankit (Mobile) | Brijesh | ||
Add "Clinical Assessment and Diagnosis" referral queue | Medium | Todo/Open (Deepak) | Rohit (Mobile) | Brijesh | Re-assigned from Deepak to balance load. | |
NPY and DOTS helper text in Counselling Section C | Medium | Analysis (Sehjot) | Sneha (UI) | Brijesh | Hindi translation must be provided by Product before release. | |
TrueNat: close test order when test not conducted | Low | Pending QA | Dev complete | Brijesh | ||
TrueNat: auto-close open orders at EoD | Low | Pending QA | Dev complete | Brijesh |
H. ABHA / ABDM
Ticket | Summary | Jira priority | Jira status | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
ABDM M2 Phase 1 – General OPD flow | Highest | In Development (Rohit) | Rohit (Mobile), Vanitha (API) | Deepshika | Largest item in the release. Rohit to confirm how much is already done. | |
Unable to create ABHA on Play Store build | High | Analysis (Deepshika) | Vanitha (API), Rohit (Mobile) | Deepshika | Needs dev investigation; currently sitting with QA. | |
"Yes" button not clickable for ABHA card download | High | In QA | Dev complete | Deepshika | ||
ABHA screen UI breaks on tablet; consent text layout | Medium | Todo/Open (Rupesh) | Sneha (UI) | Brijesh | ||
Create ABHA using Face authentication | Low | Todo/Open (Rohit) | Rohit (Mobile), Vanitha (API) | Deepshika | STRETCH – not counted in the bandwidth view. Recommend moving to 2.5 unless capacity frees up. |
I. Bugs, stability and sync
Ticket | Summary | Jira priority | Jira status | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
Card counts (All HH / All Beneficiary / Non-Household) fluctuating | Highest | Analysis (Ashutosh) | Ashutosh (Mobile) | Deepshika | ||
Android Wi-Fi captive-portal check disconnects on networks without internet validation | Highest | Todo/Open (Syed) | Deepak (Mobile) | Brijesh | Needs device/network setup for testing. | |
Incremental beneficiary sync for large datasets | High | Todo/Open (Rohit) | Rohit (Mobile), Chetan (API) | Deepshika | High regression risk; test with more than 500 beneficiaries. | |
Wrong toast count for registered family members; inconsistent purple colour | High | Todo/Open (Agraj) | Ankit (Mobile), Sneha (UI) | Brijesh | ||
OK / Cancel buttons overlap in Chief Complaint popup | Low | Todo/Open (Ankit) | Sneha (UI) | Brijesh | ||
"Add HoF member" alert; HoF icon on card | High | Pending QA | Dev complete | Brijesh | ||
Default UAT URL for Connect Camp Hub in UAT build | Medium | Pending QA | Dev complete | Brijesh |
J. Platform, DevOps and performance
Ticket | Summary | Jira priority | Jira status | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|
Performance testing of STOP_TB (reopened) | High | Reopened (Sehjot) | Sehjot (API) | Deepshika | ||
Push production builds via MDM (Intune); sunset Play Store releases | High | Todo/Open (Agraj) | Chetan (DevOps) | Brijesh | Needs the production device group (Krishna) and 4–5 test devices. | |
Soft launch ID generator on 2 camp laptops | Low | Todo/Open (Syed) | Chetan, Syed to coordinate | Brijesh | ||
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 |
|---|---|---|
PIN code and address via GPS | Closed; superseded by STOP-412 (GPS unworkable offline). | |
Duplicate work orders / duplicate names on TrueNat | Closed | |
Optimise beneficiary photo size to prevent sync failures | Closed | |
House ownership radio button (Rented / Owned) | Closed |
Bandwidth view (approximate, TBD)
This view is based on how many tickets each person holds and the kind of work involved, for a sprint starting 23-Oct-2026. It is not based on ticket-level estimates, which the team has not provided yet. "Load" is relative to what one person can reasonably deliver in a roughly 6-week sprint after allowing for festival days and normal overheads (meetings, reviews, bug-fixing, support).
Mobile developers
Developer | Tickets | Kind of work | Approx. load for a ~6-week sprint |
|---|---|---|---|
Rohit | 5 – STOP-136, 412, 523, 386, 506 | Two large, high-risk items (ABDM OPD flow, incremental sync), one medium (village-level capture), one investigation, one referral card | Over-allocated (~110–120%). Face authentication (STOP-243) cannot be added. |
Deepak | 7 – STOP-603, 604, 620, 351, 404, 414, 449 | TPT form changes (medium to large, blocked by open questions), location capture (large), a device-level bug | Over-allocated (~110–120%). Owns the whole TPT stream, which is the longest priority path. |
Ankit | 10 – STOP-602, 618, 619, 600, 576, 528, 171, 164, 433, 556 | Contact Tracing (one medium-large, rest small to medium), plus several small bug fixes and UI tweaks | Full (~100–110%). Many tickets means a lot of context-switching. |
Ashutosh | 7 – STOP-623, 599, 606, 502, 165, 408, 144 | Inventory (scope unknown), login change, dashboard (needs clarifications), a bug under analysis, two small registration tickets, locked-door flow (medium-large) | Full (~100–110%). Could rise if the Inventory ticket turns out to be large. |
API and Backend
Developer | Tickets | Kind of work | Approx. load for a ~6-week sprint |
|---|---|---|---|
Vanitha (API) | 6 – STOP-136, 599, 386, 603, 604, 620 | ABDM APIs (large), TPT APIs, login attempt count, ABHA Play Store investigation | Medium-high (~70–80%) |
Vishwa (Backend) | 6 – STOP-509, 557, 606, 602, 618, 600 | Village master data, data fix, dashboard queries, contact-tracing API changes | Medium (~50%); has headroom for overflow from Vanitha |
Sehjot (Backend) | 5 – STOP-412, 623, 252, 144, 414 | Village-level fields, inventory API, performance re-test, small flags | Medium-low (~45–50%) |
Chetan (Backend) | 3 – STOP-523, 580, 491 | Incremental sync API, MDM pipeline, ID generator rollout | Low (~40%); can support DevOps, sync testing and hotfixes |
UI
Developer | Tickets | Kind of work | Approx. load for a ~6-week sprint |
|---|---|---|---|
Sneha (UI) | 7 – STOP-524, 581, 583, 504, 607, 164, 556 | Mostly small layout, option-list and copy changes | Low-medium (~35–40%); can also support screen designs for TPT, Contact Tracing and Counselling UI |
QA
QA | Tickets | Kind of work | Approx. load |
|---|---|---|---|
Deepshika | 16 – STOP-136, 182, 252, 351, 386, 412, 502, 509, 523, 557, 599, 600, 603, 604, 606, 620 | Fewer tickets but the heavy ones: ABDM, sync, village-level capture, all TPT form changes, performance | Over-allocated (~170–190%) once regression is included |
Brijesh | 28 – STOP-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 | Many small form, option-list, UI and bug verifications plus Contact Tracing and Inventory | Over-allocated (~170–190%) once regression is included |
Key observation: developers are roughly full to slightly over in a 6-week sprint, but QA carries almost twice what two people can test in the same period. QA, not development, is the bottleneck. Only Vishwa, Sehjot, Chetan and Sneha have real headroom.
Approximate sprint duration (TBD – not confirmed)
Item | Approximate (TBD) | Basis |
|---|---|---|
Sprint start | Fri 23-Oct-2026 | Proposed |
Development phase | ~6 weeks (range 5–7), i.e. to roughly early to mid December | Highest mobile load (Rohit, Deepak) plus festival days around Diwali (~8-Nov) |
Priority items (TPT, Contact Tracing, Inventory, Login, Dashboard) dev complete | ~4 weeks, i.e. around late November | TPT stream with Deepak is the longest priority path; Inventory depends on a missing spec |
QA, regression and UAT | Runs alongside development, with a tail of ~2–4 weeks after code freeze | QA load is almost twice capacity in the same window |
Complete 2.4 build after QA | Late December 2026 to early January 2027 (TBD) | QA-bound; assumes open questions are closed in the first week |
These are rough ranges to be replaced once each developer provides ticket estimates and the holiday calendar is confirmed.
Open questions and blockers
# | Item | Needed from | Affects |
|---|---|---|---|
1 | Can we run a short hotfix sprint first, covering only the major requirements, and take the rest in a later sprint? With Diwali and other festivals falling in late October and November, a smaller first sprint may be more realistic. Candidate scope: TPT (603, 604, 620), Contact Tracing (602, 618, 619, 600), Inventory (623, once specified), Login attempts (599), Dashboard (606), and the critical bugs 576, 502, 449, 557 plus the 509 and 412 pair. Roughly 4 weeks of development (to about late November) and 1 week of QA, with the remaining tickets moved to a follow-up sprint. | Rupesh / Shivani / Mithun / Syed | Entire release plan |
2 | Inventory "additional fields" – no description or field list in the ticket | Shivani / Madhava | STOP-623 |
3 | TPT outcome clarifications (5 questions) | Shivani / Vanshika | STOP-604 |
4 | TPT regimen mapping, "250–500 words" rule, default instruction text, Follow-up gating (4 questions) | Shivani | STOP-620 |
5 | Does the "Surveillance Officer" role exist in the app? What else can it access? | Shivani / Madhava | STOP-619 |
6 | Household option: same Members screen or new form? | Shivani | STOP-618 |
7 | Eligible population definition, filter rule and relation to STOP-500 breakdown | Shivani / Vanshika | STOP-606 |
8 | Lockout message after the 5th wrong attempt; show attempts for unknown usernames? | Shivani / Engineering | STOP-599 |
9 | Village master PIN code data source; list of villages with no PIN | Product / Data team | STOP-509, STOP-412 |
10 | Hindi translation of NPY / DOTS helper text | Product | STOP-504 |
11 | 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 |
12 | 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 |
13 | Ticket-level estimates from each developer and QA | Each team member | Bandwidth view and duration |
14 | Leave and public-holiday calendar for 23-Oct to end of December | Rupesh | All dates |
15 | Can QA capacity be increased (extra tester, BSA-led UAT on option-list and copy tickets, developers self-testing small UI tickets)? | Rupesh / Mithun | QA timeline |
Risks
QA capacity is almost double what two testers can cover in the sprint window. Mitigations are in open question 15.
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 over-allocated; any slippage in ABDM (136) or the TPT stream lands on the critical path.
STOP-623 has no requirement, so its size and owner load are unknown.
Festival period in late October and November will reduce availability across the team.
Review and sign-off
Name | Role | Sign-off |
|---|---|---|
Rupesh | Delivery Manager | |
Shivani | Product Manager | |
Madhava | BSA | |
Vanshika | BSA | |
Mithun | Engineering | |
Syed | Senior Manager |