HOCO B2B
Team tasksAnis

LCH-03 — Pilot (2 weeks) — support, daily triage, hotfixes (Anis)

Two calendar weeks with a limited group of delegates and resellers in production: daily KPI and defect review, server and back-office hotfixes.

FieldDetails
Task codeLCH-03
PhaseP2 — Acceptance, go-live & pilot
Product scopeV1
StatusPlanned
StartWed 30 Dec 2026
DueThu 14 Jan 2027
ResponsibleAnis — Full-stack developer
Co-responsible—
Effort10 person-day(s) planned · 10 from scratch · size L
Area · appLaunch · shared
Depends onLCH-02
UnblocksLCH-04
MilestonesPilot go / no-go

Summary

Two calendar weeks with a limited group of delegates and resellers in production: daily KPI and defect review, server and back-office hotfixes.

Description

The cahier plans a pilot with a limited group of delegates and resellers before generalisation (§14; OPS-06, ANA-04). For two calendar weeks in production, Anis runs daily operations for the server and back-office: a daily review of pilot KPIs (adoption, share of orders via app and web, confirmation queue age, visits done, sync conflicts, push and SSE delivery, crash-free sessions from Imad's apps), daily defect triage, hotfixes through hotfix/… branches, and direct support to HOCO's staff. The pilot ends with a report and a retrospective that feed the improvements of LCH-04. Out of scope: mobile hotfixes (Imad's pilot task) and new features.

Subtasks

#SubtaskOwner
1Pilot dashboard of KPIs (ANA-04) and operational metrics (queue age, sync conflicts, dead jobs, SSE connections)Anis
2Daily 15-minute review with HOCO: KPIs, incidents, feedbackAnis
3Daily defect triage with severity and target fix dateAnis
4Server and back-office hotfixes via hotfix branches with regression tests and production deploysAnis
5Monitoring watch: errors, slow queries, queue depth, backupsAnis
6Decision log updates for rule changes requested in the pilot (settings vs code)Anis
7Pilot report and retrospective with HOCO, Imad and AkramAnis

Deliverables

  • Pilot KPI dashboard and daily review notes
  • Hotfix releases with changelog
  • Pilot report and prioritised improvement backlog for LCH-04

Acceptance criteria

  • Daily reviews held on every working day of the pilot (OPS-06)
  • Every blocking incident is fixed or worked around within one working day
  • KPIs of ANA-04 are reported for the full pilot period
  • The pilot report lists the improvements with priority and owner

Requirements covered

RequirementTitleRelease
OPS-06Pilot with a limited group of delegates and resellers, then progressive generalisationV1
ANA-04Success KPIs tracked: adoption, field conversion, digitalisation share, tour performance, loyalty, operational qualityV1

Test measures

  • Regression suite on every hotfix before deploy
  • Weekly backup restore spot check

Risks

  • Pilot users fall back to phone/WhatsApp ordering — back-office phone orders (BO-40) count as digital entries, and the KPI tracks the channel mix

KPI

  • 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.

On this page