LCH-04 — Pilot improvements — server & back-office
Prioritised fixes and adjustments from the pilot retrospective; decision log updated.
| Field | Details |
|---|---|
| Task code | LCH-04 |
| Phase | P3 — Generalisation (after the 3 months) |
| Product scope | V1 |
| Status | Planned |
| Start | Thu 14 Jan 2027 |
| Due | Tue 19 Jan 2027 |
| Responsible | Anis — Full-stack developer |
| Co-responsible | — |
| Effort | 3 person-day(s) planned · 8 from scratch · size M |
| Area · app | Launch · shared |
| Depends on | LCH-03 |
| Unblocks | LCH-05 |
| Milestones | — |
Summary
Prioritised fixes and adjustments from the pilot retrospective; decision log updated.
Description
The pilot (LCH-03) produces a prioritised list of fixes and adjustments; this task delivers the server and back-office part before generalisation (OPS-04, OPS-06). Typical items are ergonomics of the confirmation queue and order detail, tuning of settings closed in PRJ-03 (GPS tolerance, minimum amounts, return window, assisted-order expiry), report and KPI adjustments requested by direction, performance fixes found under real load, notification wording, and data corrections from the initial import. Each change is classified as a setting change or a code change, recorded in the decision log, tested and released to production. Out of scope: new V2 features and mobile changes (Imad's pilot improvements).
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Turn the pilot report into a prioritised backlog with HOCO (must before generalisation / later) | Anis |
| 2 | Settings adjustments with before/after values recorded in the decision log | Anis |
| 3 | Back-office ergonomics fixes (confirmation queue, order detail, CRM validation, tour planner) from pilot feedback | Anis |
| 4 | Server fixes and performance improvements found under real load (queries, indexes, job timings) | Anis |
| 5 | Report and KPI adjustments requested by direction | Anis |
| 6 | Notification template wording and rule adjustments | Anis |
| 7 | UI adjustments review for changed back-office screens | Akram |
| 8 | Release to production with changelog and regression run | Anis |
Deliverables
- Prioritised pilot backlog (GitHub milestone LCH-04)
- Production release with changelog
- Updated decision register and settings values
Acceptance criteria
- Every item marked must-before-generalisation is released to production (OPS-06)
- Every changed setting has an entry in the decision log and in the activity log
- The regression suite passes on the released version
- HOCO confirms the release closes the pilot findings
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| OPS-04 | Maintenance: warranty period, corrective/preventive/evolutive maintenance, support SLAs and priorities, monitoring and security updates | V1 |
| OPS-06 | Pilot with a limited group of delegates and resellers, then progressive generalisation | V1 |
Test measures
- Regression suite (server tests and Playwright) before release
- Targeted re-tests of each fixed pilot finding with the reporter
Risks
- Scope creep from pilot wishes — anything not blocking generalisation goes to the V2 backlog with HOCO's agreement
KPI
- Delivered by Tue 19 Jan 2027 within 3 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.
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.
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.