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 | 44 (5 Closed, 39 open or in progress) |
Proposed sprint start | Fri 23-Oct-2026 (first full working week starts Mon 26-Oct) |
Last synced with Jira | 09-Oct-2026 (see "Changes since last sync" below) |
Page status | DRAFT for review – proposed owners, allocation and duration are not confirmed |
PRD reference | TBMJA PRD (v186) |
Changes since last sync (Jira fix version 2.4)
Change | Tickets | What was done on this page |
|---|---|---|
Removed from fix version 2.4 (Jira total went from 50 to 44) | STOP-144 (locked-door cases), 165 (mobile number checkbox), 171 (village as default address), 243 (ABHA face authentication), 408 (auto-populate mobile number), 581 (Type of House options), 583 (cooking fuel options) | Moved to the "Removed from 2.4" table. Please confirm which release they moved to. |
Added to fix version 2.4 | STOP-628 – TB Screening Form takes excessively long to load (Highest, Analysis, Ashutosh) | Added to section I and to the allocation. Needs triage; size unknown. |
Status changed | STOP-351 (search bars) is now Closed | Moved to the Closed table. |
Assignee changed in Jira | STOP-603, 604, 620 (TPT) now with Ashutosh; STOP-606 (Dashboard) now with Rupesh | See the team input below for the proposed owners. |
Team input applied to the proposal
Puneet Sharma is a mobile developer and is now part of the delivery team. His Jira tickets STOP-414 and STOP-599 stay with him, and he picks up STOP-606. STOP-509 (village master PIN data) is data/backend work, so it moves to Vishwa.
The TPT module goes to a Backend developer. STOP-603, 604 and 620 are proposed to Chetan (lowest current load), with Vanitha supporting on APIs. This replaces the earlier Ashutosh assignment in Jira.
Ashutosh picks up Contact Tracing: STOP-602, 618, 619 and 600, in addition to his two bug investigations (STOP-502, 628). Ankit is released from Contact Tracing and keeps the referral, anthropometry and UI bug items.
Release 2.4 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
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 J below)
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 and the kind of work (mobile app logic, API/backend, UI/layout/copy, DevOps, data). Jira has not been changed by this page.
Tickets currently held by Rupesh or Syed (not delivery developers), by Agraj Parashar (not in the delivery team list), or by nobody 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 duration 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 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 (Backend developer owned)
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 | Todo/Open | Ashutosh | Chetan (Backend), Vanitha (API support) | 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 | Ashutosh | 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 | Chetan (Backend), Vanitha (API support) | Deepshika | 4 open questions (regimen month mapping, 250–500 words rule, default instruction text, follow-up gating). |
B. P0 – Contact Tracing module (Ashutosh owned)
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 | Rupesh | Ashutosh (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 | Ashutosh (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 | Ashutosh (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 | Ashutosh (Mobile), Vishwa (API) | Deepshika | Related change to TPT; keep labels consistent with 603 (Chetan). |
C. P0 – Inventory module
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Additional Improvements in Inventory Modules (additional fields) | Highest | Todo/Open | Rupesh | Deepak (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 | 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. P0 – 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 | Rupesh | Puneet (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 | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Populate village master with PIN codes | Medium | Ready for Development | Puneet Sharma | Vishwa (API/data) | Deepshika | Blocks STOP-412. Start first. Data/backend work, so moved from Puneet (mobile) to Vishwa. 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. Work is mostly app-side, so mobile leads. | |
Auto-select "Elderly" (60+) and "Urban Slum" in Key Population / Risk Factors | Medium | In Development | Deepak | Deepak (Mobile) | Brijesh | No change. 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 Sharma | Puneet (Mobile), Sehjot (API) | Brijesh | No change on the mobile side; stays with Puneet. | |
Anthropometry screen changes | High | Todo/Open | Agraj Parashar | 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 | Moved to Ankit so 164 and 433 (same Examine screens) sit with one developer, and to free Ashutosh for Contact Tracing. | |
District, Block and Village names blank for 222 records | Highest | Todo/Open | Vishwa | Vishwa (API/data) | Deepshika | No change. Data fix plus root-cause check so it does not recur. |
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. | |
Add "Clinical Assessment and Diagnosis" referral queue | Medium | Todo/Open | Deepak | Deepak (Mobile) | Brijesh | No change. | |
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. ABHA / ABDM
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | 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. Vanitha added for the API side. Rohit to confirm how much is already done. | |
Unable to create ABHA on Play Store build | High | Analysis | Deepshika (QA) | Vanitha (API), Rohit (Mobile) | Deepshika | Needs developer investigation; currently sitting with QA. | |
"Yes" button not clickable for ABHA card download | High | In QA | Deepshika | Dev complete | Deepshika | ||
ABHA screen UI breaks on tablet; consent text layout | Medium | Todo/Open | Rupesh | Sneha (UI) | Brijesh |
I. Bugs, stability and sync
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
NEW – TB Screening form takes excessively long to load and stays in a loading state | Highest | Analysis | Ashutosh | Ashutosh (Mobile), Sehjot (API, performance support) | Deepshika | Added to 2.4 since the last sync. Needs triage; check whether related to 502 (card counts) and 252 (performance testing). Size unknown. | |
Card counts (All HH / All Beneficiary / Non-Household) fluctuating | Highest | Analysis | Ashutosh | Ashutosh (Mobile) | Deepshika | No change. | |
Android Wi-Fi captive-portal check disconnects on networks without internet validation | Highest | Todo/Open | Syed | Deepak (Mobile) | Brijesh | Android-level bug, so a mobile developer. Needs device/network setup for testing. | |
Incremental beneficiary sync for large datasets | High | Todo/Open | Rohit | Rohit (Mobile), Chetan (API) | Deepshika | Chetan added for the backend side. High regression risk; test with more than 500 beneficiaries. | |
Wrong toast count for registered family members; inconsistent purple colour | High | Todo/Open | Agraj Parashar | Ankit (Mobile), Sneha (UI) | Brijesh | Count logic to Ankit, colour to Sneha. | |
OK / Cancel buttons overlap in Chief Complaint popup | Low | Todo/Open | Ankit | Sneha (UI) | Brijesh | Layout-only fix, moved to Sneha. | |
"Add HoF member" alert; HoF icon on card | High | Pending QA | Rohit | Dev complete | Brijesh | ||
Default UAT URL for Connect Camp Hub in UAT build | Medium | Pending QA | Brijesh | Dev complete | Brijesh |
J. Platform, DevOps and performance
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Performance testing of STOP_TB (reopened) | High | Reopened | Sehjot | Sehjot (API) | Deepshika | No change. | |
Push production builds via MDM (Intune); sunset Play Store releases | High | Todo/Open | Agraj Parashar | Chetan (DevOps) | Brijesh | Pipeline work, so a backend/DevOps developer. 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) | – | Stays with Rupesh. Prerequisite for QA handover. |
K. 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 | Newly Closed since last sync. | |
Duplicate work orders / duplicate names on TrueNat | Sehjot | Closed | |
Optimise beneficiary photo size to prevent sync failures | Rohit | Closed | |
House ownership radio button (Rented / Owned) | Ashutosh | Closed |
L. Removed from 2.4 since last sync
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 |
|---|---|---|
Handling locked-door cases in HH enumeration | Puneet Sharma | |
Mobile number checkbox in HH registration | Ashutosh | |
Village name as default address | Ankit | |
Create ABHA using Face authentication | Rohit | |
Auto population of mobile number from HH registration | Rohit | |
Update "Type of House" options | Rupesh | |
Update "Primary source of fuel used for cooking" options | Rupesh |
Proposed allocation and load summary (approximate, TBD)
One view of the complete allocation for a sprint starting 23-Oct-2026. "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 38 unique open tickets being allocated). The five Closed tickets and the removed tickets are excluded. "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). It is not based on ticket-level estimates.
Person | Role | No. of tickets | Tickets | Kind of work | Approx. load |
|---|---|---|---|---|---|
Rohit | Mobile | 4 | STOP-136, 412, 523, 386 | Two large, high-risk items (ABDM OPD flow, incremental sync), one medium (village-level capture), one investigation | Full (~95–105%) |
Ashutosh | Mobile | 6 | STOP-602, 618, 619, 600, 628, 502 | Contact Tracing (one medium-large, rest small to medium), plus two Highest-priority bugs under analysis (form load time, card counts) | Full (~100–110%); may rise if the two bugs are deep |
Deepak | Mobile | 4 | STOP-404, 449, 506, 623 | Auto-select rules, a device-level bug, referral queue, Inventory (scope unknown) | Medium (~65–75%); may rise if Inventory is large |
Puneet | Mobile | 3 | STOP-414, 599, 606 | Location capture (large, in development), login change (small), dashboard (needs clarifications) | Medium (~70–80%) |
Ankit | Mobile | 5 | STOP-576, 528, 164, 433, 556 | Referral and screening bug fixes, anthropometry and Examine button, toast count | Medium (~60–70%); has headroom |
Chetan | Backend (TPT owner) / DevOps | 6 | STOP-603, 604, 620, 523, 580, 491 | TPT module (medium to large, blocked by open questions), incremental sync API, MDM pipeline, ID generator rollout | Medium-high (~75–85%) |
Vanitha | API | 6 | STOP-136, 599, 386, 603, 604, 620 | ABDM APIs (large), login attempt count, ABHA investigation, API support on TPT | 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%); headroom for overflow |
Sehjot | Backend | 5 | STOP-412, 623, 252, 414, 628 | Village-level fields, inventory API, performance work, location API, form-load investigation support | Medium (~45–50%) |
Sneha | UI | 5 | STOP-524, 504, 607, 164, 556 | Small layout, copy and colour changes | Low (~25–30%); can also support screen designs for TPT and Contact Tracing |
Deepshika | QA | 16 | STOP-136, 182, 252, 386, 412, 502, 509, 523, 557, 599, 600, 603, 604, 606, 620, 628 | Fewer but heavier tickets: ABDM, sync, village-level capture, TPT forms, performance | Over-allocated (~170–190%) with regression |
Brijesh | QA | 22 | STOP-163, 164, 404, 414, 433, 449, 491, 504, 506, 524, 528, 552, 553, 556, 576, 580, 593, 602, 607, 618, 619, 623 | Many small form, UI and bug verifications plus Contact Tracing and Inventory | Over-allocated (~140–160%) with regression |
Rupesh | Delivery Manager | 1 | STOP-564 | Non-dev environment setup | Not a delivery load |
Key observation: with Puneet in the mobile team and TPT with a backend developer, developer load is now balanced, and Ankit, Deepak and Puneet have some headroom. QA remains well above what two people can test in the same period and is still the bottleneck, so spare mobile capacity is best used for developer self-testing and for QA hand-over preparation.
Tickets moving away from their current Jira assignee
Current Jira assignee | Open tickets held today | Moving to |
|---|---|---|
Rupesh (Delivery Manager) | 7 | 6 move to developers (STOP-524 to Sneha; 600, 602, 618 to Ashutosh; 606 to Puneet; 623 to Deepak); STOP-564 stays |
Puneet Sharma (Mobile) | 3 | STOP-414 and 599 stay with him; STOP-509 moves to Vishwa (data work) |
Agraj Parashar | 3 | STOP-164 and 556 to Ankit (with Sneha), STOP-580 to Chetan |
Syed (Senior Manager) | 2 | STOP-449 to Deepak, STOP-491 to Chetan |
Unassigned | 1 | STOP-619 to Ashutosh |
Developers, moved on team input or to match the kind of work | 7 | STOP-603, 604, 620 (Ashutosh to Chetan, TPT to a Backend developer); STOP-433 (Ashutosh to Ankit); STOP-504 (Sehjot to Sneha); STOP-607 (Ankit to Sneha); STOP-412 (Sehjot to Rohit for the app side, Sehjot keeps API) |
Approximate sprint duration (TBD – not confirmed)
Item | Approximate (TBD) | Basis |
|---|---|---|
Sprint start | Fri 23-Oct-2026 | Proposed |
Development phase | ~4–5 weeks, i.e. to roughly late November | Seven tickets left the release, five mobile developers, TPT with a Backend developer; festival days around Diwali (~8-Nov) |
Priority items (TPT, Contact Tracing, Inventory, Login, Dashboard) dev complete | ~3–4 weeks, i.e. mid to late November | TPT is blocked by open clarifications; Contact Tracing with Ashutosh is the longest mobile path; Inventory depends on a missing spec |
QA, regression and UAT | Runs alongside development, with a tail of ~2–3 weeks after code freeze | QA load is still above capacity in the same window |
Complete 2.4 build after QA | Mid December 2026 (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, 628, 449, 557 plus the 509 and 412 pair. Roughly 3–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 Agraj Parashar (assigned in Jira but not in the delivery team list) | Rupesh / Mithun | 164, 556, 580 |
12 | Update Jira assignees to match this page once the proposal is agreed (TPT currently with Ashutosh in Jira) | Rupesh | All |
13 | Ticket-level estimates from each developer and QA | Each team member | Allocation 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, developers self-testing small UI tickets)? | Rupesh / Mithun | QA timeline |
16 | Which release did the 7 removed tickets (144, 165, 171, 243, 408, 581, 583) move to, and is STOP-628 confirmed as in scope for 2.4? | Shivani / Rupesh | Scope and allocation |
17 | TPT is proposed to Chetan (lowest backend load) with Vanitha supporting. Confirm Chetan, or choose Sehjot / Vishwa, and confirm whether any app-side screen change in TPT needs a mobile developer to pair. | Mithun / Rupesh | STOP-603, 604, 620 |
Risks
QA capacity is above 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) still have open clarifications.
TPT owned by a Backend developer: if the TPT changes include screen or form changes in the app, they may need mobile support (open question 17).
Ashutosh carries Contact Tracing plus two Highest-priority bugs (502, 628); if the bugs are deep, Contact Tracing slips. Ankit has headroom to help.
Sequencing dependencies: 509 → 412 → 404; 603 + 604 + 600 to be built together (Chetan and Ashutosh must align on wording).
STOP-623 has no requirement, so its size and Deepak's load are unknown.
Scope is still moving (7 tickets removed and 1 added in the last sync), so allocation and dates may change again.
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 |