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 | 28 (8 Closed, 20 open or in progress) |
Proposed release window | Mon 26-Oct to Fri 6-Nov-2026 (10 working days); Sat 7-Nov kept as buffer. Diwali is around Sun 8-Nov. |
Last synced with Jira | 12-Oct-2026 (see "Changes since last sync" below) |
Page status | DRAFT for review – proposed owners, allocation and dates are not confirmed |
PRD reference | TBMJA PRD (v186) |
Changes since last sync (Jira fix version 2.4)
Jira total went from 30 to 28 tickets.
Change | Tickets | What was done on this page |
|---|---|---|
Removed from fix version 2.4 | STOP-623 (Inventory module – additional improvements) and STOP-491 (ID generator soft launch) | Moved to the "Removed from 2.4" table. There is now no Inventory ticket in 2.4, which is one of the release priorities (see open question 2). |
Status changed | STOP-600 (Confirmed TB follow-up): Todo to In Development (Deepak) | Updated in the ticket table. |
Assignee changed in Jira | STOP-606 (Dashboard): Rupesh to Deepak | Deepak now holds all of Contact Tracing plus the Dashboard in Jira (5 open tickets); the proposed splits below keep his load reasonable. |
Earlier changes (previous syncs): 21 tickets left the release (9 in the sync before this one: STOP-163, 164, 252, 433, 502, 523, 556, 557, 580; 5 before that: STOP-136, 182, 386, 509, 524; 7 before that: STOP-144, 165, 171, 243, 408, 581, 583). STOP-506, 564 and 628 were closed, STOP-404 moved to Pending QA, STOP-603 to In Development, and Contact Tracing moved to Deepak in Jira.
Team input applied to the proposal
Puneet Sharma is a mobile developer and part of the delivery team. He keeps STOP-414 and STOP-599.
Mobile owners follow Jira: Contact Tracing with Deepak; TPT with Ashutosh.
TPT backend goes to a Backend developer:Chetan owns the TPT backend work for STOP-603, 604 and 620, with Vanitha supporting on APIs.
To fit the 2-week window, three splits are proposed against Jira: STOP-620 (largest TPT ticket) to Rohit; STOP-618 (largest Contact Tracing ticket) to Ankit; STOP-606 (Dashboard) to Puneet. All can be reversed if you prefer to keep the Jira assignee.
Release priorities
Priority focus for this release, in order:
TPT module improvements – STOP-603, 604, 620
Contact Tracing module improvements – STOP-602, 618, 619 (plus the related Confirmed TB follow-up change STOP-600)
Inventory module – additional fields – STOP-623 has left 2.4; BRD is a draft (see below)
Nikshay enrollment and test addition – BRD is a draft; no Jira tickets yet
Microplanning – no requirements or tickets yet
Wrong-password attempts counter on login – STOP-599
Dashboard change – STOP-606
Everything else – registration and location capture, referrals and counselling, bug fixes (sections F to H below)
Release window plan: 26-Oct to 7-Nov-2026
What exists for the new priorities
Area | What was found | Gap |
|---|---|---|
Inventory | AMRIT - Inventory Management BRD, v0.1 Draft, Pranoti Monde, updated 6-Oct. Covers Admin Portal changes only: Item Master changes, new Device Master, Device Inventory, Device AMC/Warranty and Device-to-Camp/Store mapping. | Camp-laptop sync and backend APIs are named in the purpose but not detailed. Not approved. STOP-623 (which had no description) has now left 2.4, so there is no ticket tracking this in the release. |
Nikshay | Nikshay Enrollment and Test Addition Flow BRD, v1.0 Draft, Ganesh Shirpure, 7-Oct. 15 requirements: three new MMU tabs (Generate Ni-kshay ID, Add/Update Test Results, Transfer Out), X-ray and NAAT result push, validations, sync status, admin configuration. | Not approved. Several points are marked "to confirm". The programme team still has to fill the configuration tables (PPSA ID, device PHIs, village mapping). No Jira tickets except STOP-284 (Nikshay ID POC, Highest, no fix version). Earlier Nikshay work (ID generator app, API contract) from 2.2 can be reused. |
Microplanning | Nothing found for TB in Jira or Confluence (only unrelated FLW micro birth plan items). | No BRD and no UAT tickets logged. |
Tracks in the window
Track | Goal in the window | Scope |
|---|---|---|
A. Build and ship | Priority build | TPT (603, 604, 620), Contact Tracing (600, 602, 618, 619), login attempts (599), location capture in development (414), critical bugs (576, 449), items already in QA (404, 552, 553, 593), small UI items (504, 607) |
B. Inventory | Readiness only until a ticket exists | Admin Portal masters from the BRD (Item Master changes, Device Master, Device Inventory) are a possible phase 1. A new or re-linked Jira ticket with an approved scope is needed first. Camp sync and mobile come later. Suggested owner: Sehjot (Backend/Admin Portal). |
C. Nikshay | Get ready, then build a thin slice | BRD sign-off, programme configuration data, API check (STOP-284). If approved by 28-Oct, start Tab 1 (Generate Ni-kshay ID), likely with Rohit, who did the earlier Nikshay integration. Full scope is a later release. |
D. Microplanning | Discovery and UAT capture | BSAs and Product log UAT findings and requirements as Jira tickets by 30-Oct so they can be estimated. Goes into a later release. |
Commit, stretch and next release
Tier | Tickets |
|---|---|
Commit (26-Oct to 6-Nov) | TPT: 603, 604, 620. Contact Tracing: 600, 602, 618, 619. Login: 599. Bugs: 576, 449. In development: 414. Already in QA or dev complete: 404, 552, 553, 593. Small UI: 504, 607. |
Stretch | 606 (Dashboard, needs clarifications), 528 (Liquid Culture referral), Inventory phase 1 (only if the BRD scope is signed off by 28-Oct and a ticket exists) |
Next release | 412 (blocked: depends on village master data in STOP-509, which left 2.4), Nikshay build beyond Tab 1, Microplanning, and the 23 tickets removed from 2.4 |
Gates and dates
Date | Gate | Owner |
|---|---|---|
By Fri 23-Oct | Open questions answered: TPT (604: 5 questions, 620: 4 questions), Surveillance Officer role (619), lockout rule (599), Household screen (618) | Shivani / Vanshika / Madhava |
By Fri 23-Oct | Confirm 603 hand-over and the TPT and Contact Tracing owner splits | Mithun / Rupesh |
By Fri 23-Oct | Confirm where STOP-623 (Inventory) moved and whether a ticket with an approved scope will exist | Shivani / Rupesh |
Mon 26-Oct | Kickoff, scope frozen, owners confirmed, each developer and QA gives ticket estimates on day 1 | Rupesh |
Wed 28-Oct | Inventory and Nikshay scope signed off with estimates, otherwise moved to the next release | Shivani / Mithun |
Fri 30-Oct | Microplanning UAT findings logged as tickets | Madhava / Vanshika |
Wed 4-Nov | Code freeze, regression starts | Mithun / QA |
Fri 6-Nov | UAT sign-off and release candidate build (target) | Rupesh / Shivani |
Sat 7-Nov | Buffer; no release planned on the Diwali weekend | – |
Risk to the date: if the TPT questions are not closed before 26-Oct, or if QA cannot keep pace, the realistic release candidate moves out by about 1–2 weeks, to roughly 13–20 Nov (TBD). Festival days in the week of 9-Nov will reduce availability.
Team and roles
Role | People |
|---|---|
Mobile developers | Rohit, Deepak, Ankit, Ashutosh, Puneet |
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 |
How to read the ticket tables
Current Jira assignee shows who the ticket is assigned to in Jira today. Proposed dev owner(s) shows who should own it based on the roles above, the kind of work and the 2-week window. Jira has not been changed by this page.
Tickets currently held by Syed (not a delivery developer) have been re-proposed to the right developer.
No effort estimates are included because the team has not estimated individual tickets yet. The allocation and load below are based on ticket counts and kind of work and are deliberately approximate.
Sneha is assumed to own pure UI/layout/copy changes; mobile developers own app logic.
Public holidays and planned leave are not yet deducted (Diwali around 8-Nov-2026; to be confirmed against the company holiday calendar).
Scope by theme
A. P0 – TPT module (Mobile and Backend)
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
TPT follow-up: remove "Adherence to Medicines", rename ADR to "Side effects" | Highest | In Development | Ashutosh | Ashutosh (Mobile), Chetan (Backend), Vanitha (API support) | Deepshika | Already in development under Ashutosh. 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 | Ashutosh | Ashutosh (Mobile), Chetan (Backend), Vanitha (API support) | 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 | Ashutosh | Rohit (Mobile), Chetan (Backend), Vanitha (API support) | Deepshika | Largest TPT ticket; split to Rohit to fit the window (Jira has it with Ashutosh). 4 open questions (regimen month mapping, 250–500 words rule, default instruction text, follow-up gating). |
B. P0 – Contact Tracing module (Deepak and Ankit)
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Add "Household" option, view/edit/update after submit, "Any other Significant Information" (500 words) | Highest | Todo/Open | Deepak | Ankit (Mobile), Vishwa (API) | Brijesh | Largest Contact Tracing ticket; split to Ankit to fit the window. 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 | Deepak | Deepak (Mobile), Vishwa (API) | Brijesh | Jira assignee matches. 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 | Deepak | Deepak (Mobile) | Brijesh | Jira assignee matches. 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 | In Development | Deepak | Deepak (Mobile), Vishwa (API) | Deepshika | Jira assignee matches; development has started. Keep labels consistent with 603. |
C. P0 – Inventory module (no open ticket in 2.4)
STOP-623 (Additional Improvements in Inventory Modules, Highest) has been removed from 2.4. A draft BRD exists (v0.1, Admin Portal only, see "What exists" above) but it is not approved and nothing in the release tracks it. Possible phase 1 (Admin Portal masters), if approved: Sehjot (Backend/Admin Portal), with a mobile developer named once the scope is signed off, QA Brijesh. See open question 2.
D. Login: wrong-password attempts
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Wrong-password error should show remaining attempts (max 5) | High | Todo/Open | Puneet Sharma | Puneet (Mobile), Vanitha (API) | Deepshika | No change on the mobile side. 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. Dashboard
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Screening Coverage Summary: "Total Eligible Population for TB Screening" with demographic breakdown | Low | Todo/Open | Deepak | Puneet (Mobile), Vishwa (API) | Deepshika | Stretch for this window. Jira now has it with Deepak, who already holds all of Contact Tracing, so it is proposed to Puneet. 3 open clarifications (definition of eligible population, filter rule, replace or sit alongside STOP-500 breakdown). |
F. Registration and location capture
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Pincode and Residential Area captured once per village (supersedes GPS approach STOP-308) | Highest | Todo/Open | Sehjot | Rohit (Mobile), Sehjot (API) | Deepshika | Blocked: depends on village master PIN data (STOP-509), which left 2.4. Not in the window commit; next release unless the data source is confirmed (open question 9). | |
Auto-select "Elderly" (60+) and "Urban Slum" in Key Population / Risk Factors | Medium | Pending QA | Deepak | Dev complete (Deepak) | Brijesh | Development done. Urban Slum rule needs Residential Area from 412, so full verification may wait for 412. | |
Location capture changes (Digipin only, progress bar, edit location) | High | In Development | Puneet Sharma | Puneet (Mobile), Sehjot (API) | Brijesh | No change; stays with Puneet. |
G. Referrals, counselling and TrueNat
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | 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 | No change. Regression from 2.3.25; fix early. | |
Beneficiary not moving to Liquid Culture referral card | High | Todo/Open | Ankit | Ankit (Mobile) | Brijesh | No change. Stretch for this window. | |
NPY and DOTS helper text in Counselling Section C | Medium | Analysis | Sehjot | Sneha (UI) | Brijesh | Copy/helper text is a UI task, not backend. Hindi translation must be provided by Product before release. | |
TrueNat: close test order when test not conducted | Low | Pending QA | Brijesh | Dev complete | Brijesh | ||
TrueNat: auto-close open orders at EoD | Low | Pending QA | Brijesh | Dev complete | Brijesh |
H. Bugs and stability
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Android Wi-Fi captive-portal check disconnects on networks without internet validation | Highest | Todo/Open | Syed | Rohit (Mobile) | Deepshika | Android-level bug, so a mobile developer. Needs device/network setup for testing. | |
OK / Cancel buttons overlap in Chief Complaint popup | High | Todo/Open | Ankit | Sneha (UI) | Brijesh | Layout-only fix, moved to Sneha. | |
Default UAT URL for Connect Camp Hub in UAT build | High | Pending QA | Brijesh | Dev complete | Brijesh |
I. Closed in 2.4
Ticket | Summary | Last Jira assignee | Note |
|---|---|---|---|
PIN code and address via GPS | Agraj Parashar | Closed; superseded by STOP-412 (GPS unworkable offline). | |
Search bars in ADR (treatment follow-up, TPT follow-up) and Key population / risk factors | Shivani | Closed | |
Duplicate work orders / duplicate names on TrueNat | Sehjot | Closed | |
Optimise beneficiary photo size to prevent sync failures | Rohit | Closed | |
Add "Clinical Assessment and Diagnosis" referral queue | Shivani | Closed | |
Local environment setup on Deepsikha's and Pratiksha's laptops | Rupesh | Closed | |
House ownership radio button (Rented / Owned) | Ashutosh | Closed | |
TB Screening form takes excessively long to load | Ashutosh | Closed |
J. Removed from 2.4
These tickets are no longer in the Jira fix version 2.4. Please confirm the release they moved to.
Ticket | Summary | Last known Jira assignee | Removed in |
|---|---|---|---|
Additional Improvements in Inventory Modules (release priority) | Rupesh | Latest sync | |
Soft launch ID generator on 2 camp laptops | Syed | Latest sync | |
"Add HoF member" alert; HoF icon on card (was Pending QA) | Rohit | Previous sync | |
Anthropometry screen changes | Agraj Parashar | Previous sync | |
Performance testing of STOP_TB (reopened) | Sehjot | Previous sync | |
Examine button state reflects complete form submission | Ashutosh | Previous sync | |
Card counts (All HH / All Beneficiary / Non-Household) fluctuating | Ashutosh | Previous sync | |
Incremental beneficiary sync for large datasets | Rohit | Previous sync | |
Wrong toast count for registered family members; inconsistent colour | Ashutosh | Previous sync | |
District, Block and Village names blank for 222 records | Vishwa | Previous sync | |
Push production builds via MDM (Intune); sunset Play Store releases | Agraj Parashar | Previous sync | |
ABDM M2 Phase 1 – General OPD flow | Rohit | Earlier sync | |
"Yes" button not clickable for ABHA card download | Deepshika | Earlier sync | |
Unable to create ABHA on Play Store build | Deepshika | Earlier sync | |
Populate village master with PIN codes | Puneet Sharma | Earlier sync | |
ABHA screen UI breaks on tablet; consent text layout | Rupesh | Earlier sync | |
Handling locked-door cases in HH enumeration | Puneet Sharma | Earlier sync | |
Mobile number checkbox in HH registration | Ashutosh | Earlier sync | |
Village name as default address | Ankit | Earlier sync | |
Create ABHA using Face authentication | Rohit | Earlier sync | |
Auto population of mobile number from HH registration | Rohit | Earlier sync | |
Update "Type of House" options | Rupesh | Earlier sync | |
Update "Primary source of fuel used for cooking" options | Rupesh | Earlier sync |
Proposed allocation and load summary (approximate, TBD)
One view of the complete allocation for the 26-Oct to 6-Nov window (10 working days). "Tickets" counts every open ticket a person is involved in (where two people share a ticket, it counts for both, so the column adds up to more than the 20 open tickets). Closed and removed tickets are excluded. "Load" is relative to what one person can reasonably deliver in 10 working days after normal overheads (meetings, reviews, bug-fixing, support), counting only the commit and stretch scope above. It is not based on ticket-level estimates, which the team has not provided yet.
Person | Role | No. of tickets | Tickets | Kind of work | Approx. load in the window |
|---|---|---|---|---|---|
Ashutosh | Mobile | 2 | STOP-603, 604 | TPT follow-up forms (medium to large, blocked by open questions) | Medium (~75%); spare capacity can take STOP-528 or 576 |
Rohit | Mobile | 3 | STOP-620, 449, 412 | Largest TPT ticket, an Android-level bug; 412 is blocked | Full to over (~110%); would be higher if 412 is unblocked |
Deepak | Mobile | 4 | STOP-600, 602, 619, 404 (Pending QA) | Contact Tracing follow-up changes (small to medium). In Jira he holds 5 open tickets (600, 602, 606, 618, 619), which would be well over capacity if 618 and 606 are not moved. | Full (~95%) with the proposed splits |
Ankit | Mobile | 3 | STOP-618, 576, 528 | Largest Contact Tracing ticket, Highest-priority screening bug, referral bug (stretch) | Over (~110–130%) |
Puneet | Mobile | 3 | STOP-414, 599, 606 | Location capture (in development), login change, dashboard (stretch) | Full (~95–115%) |
Chetan | Backend (TPT owner) | 3 | STOP-603, 604, 620 | TPT backend for all three TPT tickets | Medium (~55–65%); headroom for Nikshay or Inventory API work |
Vanitha | API | 4 | STOP-599, 603, 604, 620 | Login attempt count, API support on TPT | Low (~35–40%) |
Vishwa | Backend | 4 | STOP-600, 602, 618, 606 | Contact Tracing API changes, dashboard queries | Medium (~55–65%) |
Sehjot | Backend / Admin Portal | 2 | STOP-412, 414 | Location API (412 blocked) | Low (~20–30%); headroom for Inventory Admin Portal and Nikshay API once scoped |
Sneha | UI | 2 | STOP-504, 607 | Small copy and layout fixes | Low (~25–30%); can also design TPT and Contact Tracing screens, and Inventory admin screens |
Deepshika | QA | 8 | STOP-412, 449, 599, 600, 603, 604, 606, 620 | TPT forms, login, Contact Tracing follow-up, Android bug | Over-allocated (~170–200%) with regression |
Brijesh | QA | 12 | STOP-404, 414, 504, 528, 552, 553, 576, 593, 602, 607, 618, 619 | Contact Tracing, location capture, referrals, TrueNat, small verifications | Over-allocated (~190–220%) with regression |
Key observation: with Inventory out of the release, Sehjot and Chetan have real headroom, which can be used for Inventory or Nikshay once those are scoped. Mobile developers are roughly full for the 2-week window, and QA is far above what two testers can verify in 10 working days. QA is the bottleneck. To protect 6-Nov, use rolling QA from day 1, developer self-testing on small items, and BSA-led UAT (Madhava, Vanshika).
Tickets moving away from their current Jira assignee
Current Jira assignee | Open tickets held today | Moving to |
|---|---|---|
Syed (Senior Manager) | 1 | STOP-449 to Rohit |
Deepak (all of Contact Tracing plus Dashboard) | 5 | STOP-618 to Ankit; STOP-606 to Puneet; he keeps 600, 602 and 619 |
Developers, moved to match the kind of work or to fit the window | 4 | STOP-620 (Ashutosh to Rohit); STOP-504 (Sehjot to Sneha); STOP-607 (Ankit to Sneha); STOP-412 (Sehjot to Rohit for the app side, Sehjot keeps API) |
TPT backend (Chetan, Vanitha) | 3 | STOP-603, 604, 620 keep their mobile owners and gain a Backend owner |
STOP-600, 602 and 619 (Deepak) and STOP-603, 604 (Ashutosh) match Jira. STOP-414 and 599 stay with Puneet.
Open questions and blockers
# | Item | Needed from | Affects |
|---|---|---|---|
1 | Confirm the 26-Oct to 6-Nov window and the commit / stretch / next-release split above. Accept that Inventory, Nikshay and Microplanning are readiness tracks in this window, not full builds. | Rupesh / Shivani / Mithun / Syed | Entire release plan |
2 | Inventory: STOP-623 left 2.4. Which release or ticket now tracks it? If Inventory is to be worked in this window, a Jira ticket with an approved scope is needed. Approve the draft BRD (v0.1, Admin Portal only) and decide phase 1; camp sync and mobile parts are not yet specified. | Shivani / Pranoti Monde / Madhava / Rupesh | Track B |
3 | Nikshay: review and approve the draft BRD (v1.0), close the "to confirm" points, get the programme team to fill the configuration tables (PPSA ID, device PHIs, village mapping), and create Jira tickets from the 15 requirements. | Shivani / Ganesh Shirpure / Programme team | Track C, STOP-284 |
4 | Microplanning: no BRD or tickets found. Is it already built and awaiting UAT, or not yet specified? Log UAT findings as Jira tickets by 30-Oct. | Shivani / Madhava / Vanshika | Track D |
5 | TPT outcome clarifications (5 questions) | Shivani / Vanshika | STOP-604 |
6 | TPT regimen mapping, "250–500 words" rule, default instruction text, Follow-up gating (4 questions) | Shivani | STOP-620 |
7 | Does the "Surveillance Officer" role exist in the app? What else can it access? | Shivani / Madhava | STOP-619 |
8 | Household option: same Members screen or new form? Eligible population definition for the dashboard (3 questions)? Lockout message after the 5th wrong attempt, and show attempts for unknown usernames? | Shivani / Vanshika / Engineering | STOP-618, 606, 599 |
9 | STOP-509 (village master PIN codes) has left 2.4, but STOP-412 depends on it. Which release does 509 go to, and is 412 deliverable? | Product / Data team / Rupesh | STOP-412, 404 |
10 | Hindi translation of NPY / DOTS helper text | Product | STOP-504 |
11 | Ticket-level estimates from each developer and QA, on day 1 of the window | Each team member | Allocation and dates |
12 | Update Jira assignees to match this page once the proposal is agreed | Rupesh | All |
13 | Leave and public-holiday calendar for 26-Oct to end of November, including the Diwali week | Rupesh | All dates |
14 | Can QA capacity be increased (extra tester, BSA-led UAT, developers self-testing small UI tickets)? | Rupesh / Mithun | QA timeline |
15 | Confirm the TPT split: Ashutosh (603, 604) and Rohit (620) on mobile, Chetan on backend, Vanitha supporting. STOP-603 is already In Development under Ashutosh. Also confirm the Contact Tracing split: Deepak (600, 602, 619) and Ankit (618), with the Dashboard (606) to Puneet. | Mithun / Rupesh | STOP-603, 604, 620, 618, 606 |
16 | Which release did the 23 removed tickets move to? In particular the Highest/High items STOP-623, 502, 557, 523, 580, 252 and the whole ABHA/ABDM block. Is any of it meant to be pulled back? | Shivani / Rupesh | Scope and allocation |
Risks
QA capacity is far above what two testers can cover in 10 working days. Mitigations are in open question 14.
TPT and Contact Tracing are blocked by unresolved PRD questions. Highest-priority tickets (604, 619, 620) still have open clarifications; if they are not closed before 26-Oct, the date slips.
Inventory has no ticket in 2.4 and only a draft BRD. Nikshay has only a draft BRD and no tickets, and depends on the programme team providing configuration data. Microplanning has no requirements at all. None of them can be committed in the window.
Deepak is overloaded in Jira (all Contact Tracing plus the Dashboard). The splits to Ankit and Puneet must be confirmed, otherwise Contact Tracing slips.
STOP-412 depends on STOP-509, which has left 2.4 (open question 9).
Large tickets in the commit scope (STOP-618, 620, 414) are already split or in development; any slippage lands on the 6-Nov date.
Scope is still moving (23 tickets removed and 8 closed across the last four syncs), so allocation and dates may change again.
Festival period: Diwali around 8-Nov. A release candidate that slips past 6-Nov is likely to land around 13–20 Nov.
Review and sign-off
Name | Role | Sign-off |
|---|---|---|
Rupesh | Delivery Manager | |
Shivani | Product Manager | |
Madhava | BSA | |
Vanshika | BSA | |
Mithun | Engineering | |
Syed | Senior Manager |