HOCO B2B
Team tasksAnis

LCH-05 — Generalisation roll-out — waves by zone, public store release

Progressive opening zone by zone after the pilot, remaining delegates trained, apps promoted to the public Play track, maintenance and support procedures handed over.

FieldDetails
Task codeLCH-05
PhaseP3 — Generalisation (after the 3 months)
Product scopeV1
StatusPlanned
StartWed 20 Jan 2027
DueThu 21 Jan 2027
ResponsibleAnis — Full-stack developer
Co-responsibleImad, Akram
Effort1.5 person-day(s) planned · 4 from scratch · size S
Area · appLaunch · shared
Depends onLCH-04, MOB-18
UnblocksSRV-29
MilestonesGeneralisation complete

Summary

Progressive opening zone by zone after the pilot, remaining delegates trained, apps promoted to the public Play track, maintenance and support procedures handed over.

Description

After the pilot improvements, the platform opens progressively to all zones (cahier §14; OPS-03, OPS-04, OPS-06). This task plans and runs the generalisation waves by zone (delegates trained, resellers imported or invited, capacity watched per wave), promotes both apps from the Play closed track to the public track, launches the reseller web at app.hoco.dz with links from the app, invitations and HOCO's channels, and hands over maintenance and support: SLAs and priorities, corrective/preventive/evolutive maintenance process, monitoring and security updates (OPS-04). Out of scope: V2 features (P4).

Subtasks

#SubtaskOwner
1Wave plan by zone with dates, delegates, reseller counts and go criteria per waveAnis
2Training of the remaining delegates and managers per wave (reusing LCH-02 material)Anis
3Import or invitation of the remaining resellers and users per wave; support regions completedAnis
4Promote reseller and delegate apps to the public Play track; store listing reviewImad
5Store listing visuals and launch announcement material for resellersAkram
6Reseller web promotion to all resellers: links from the app and invitation landing, announcementAnis
7Capacity watch per wave (API latency, queue depth, DB size, SSE connections) and scaling actionsAnis
8Maintenance and support handover: SLA and priority grid, defect reporting channel, warranty period, security update routineAnis

Deliverables

  • Wave plan and per-wave go/no-go records
  • Apps on the public Play track; reseller web announced
  • Maintenance and support procedure (SLAs, priorities, contacts) signed by HOCO

Acceptance criteria

  • Every zone is open with trained delegates by the end of the last wave (OPS-06)
  • Both apps are available on the public Play track (OPS-02)
  • The reseller web is live at app.hoco.dz and resellers can sign in with their mobile accounts (RWA-02)
  • The maintenance procedure with SLAs and priorities is accepted by HOCO (OPS-04)

Requirements covered

RequirementTitleRelease
OPS-03Training: administrators and managers, delegates on a full tour scenario, reseller quick guide, admin documentation and support proceduresV1
OPS-04Maintenance: warranty period, corrective/preventive/evolutive maintenance, support SLAs and priorities, monitoring and security updatesV1
OPS-06Pilot with a limited group of delegates and resellers, then progressive generalisationV1

Test measures

  • Per-wave smoke checks and KPI review
  • Load check before the largest wave

Risks

  • A wave surfaces regional issues (connectivity, GPS, carriers) — keep a pause criterion per wave and a buffer between waves

KPI

  • Delivered by Thu 21 Jan 2027 within 1.5 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