LCH-03B — Pilot (2 weeks) — mobile support & hotfixes (Imad)

SummaryCopy Anchor Link

Two calendar weeks on call for pilot users: crash/ANR triage, hotfix releases on the closed track, field visits with delegates when needed.

DescriptionCopy Anchor Link

During the two-week pilot a limited group of delegates and resellers uses the production apps for real work, and mobile issues must be caught and fixed before generalisation (OPS-06). Scope: Imad is on call for the pilot users — crash and ANR triage from Sentry and Play vitals, sync-error follow-up per delegate, hotfix releases on the closed track with a forced update when needed, and field visits with delegates when a problem cannot be reproduced remotely. New features are out of scope; improvements are logged for MOB-18. It needs from Anis the production monitoring (server logs, sync errors per delegate), a daily 15-minute triage slot and AppVersionPolicy changes for forced updates; Akram joins field visits for UX observation when useful. The pilot findings become the MOB-18 backlog and feed LCH-05.

SubtasksCopy Anchor Link

DeliverablesCopy Anchor Link

• Hotfix releases 1.0.x of the affected app(s) on the closed track with release notes
• Pilot log (incidents, root causes, fixes, feedback) shared with Anis and Akram
• Prioritised MOB-18 backlog as GitHub issues labelled pilot

Acceptance criteriaCopy Anchor Link

• Every crash or ANR reported during the pilot is triaged within one working day and either fixed or scheduled with a reason
• Crash-free users stay at or above 99.5 % for both apps over the pilot (target to confirm in the acceptance plan)
• At the end of each pilot day no delegate has unresolved sync errors without an explanation (SYN-05 in production)
• Every hotfix ships through CI and the closed track with notes, never as a side-loaded APK
• The pilot log and the MOB-18 backlog are ready for the pilot retrospective

Requirements coveredCopy Anchor Link

Test measuresCopy Anchor Link

• Full integration_test suites run before each hotfix release
• Smoke test of each hotfix on two pilot devices before promoting it
• Post-pilot review of Sentry release health per version

RisksCopy Anchor Link

• A hotfix introduces a regression in offline sync — sync suites mandatory before release and staged rollout to a few delegates first
• Pilot delegates stay on old versions — minimum version raised through AppVersionPolicy after each critical hotfix

KPICopy Anchor Link

• Delivered by Thu 14 Jan 2027 within 10 person-day(s).
• Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
• Zero open critical defects, permission gaps or data-integrity regressions at sign-off.

---

Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.