Timeline
The three-month plan — phases, milestones, the week-by-week plan and every task on the calendar, computed from the plan.
V1 takes three months, from design to deployment: from Sunday 18 October 2026 to mid-January 2027. The plan is built to that frame, and the milestones table checks the go-live and the pilot start against it. Generalisation and V2 follow after the three months.
Every date on this page is computed from content/plan/tasks.json by the scheduler. It uses Sunday–Thursday weeks with Algerian public holidays removed, walks each person's tasks in order, and only starts a task once its dependencies are done. Change the plan and the dates move — see the planning method.
Phases
The cahier's ten-phase roadmap (§14) maps onto five delivery phases:
| Phase | Cahier phases | What it delivers |
|---|---|---|
| P0 — Foundations | 1 Cadrage · 2 UX/UI · 3 Architecture | Validated rules and decisions, the complete design (21 working days), the service catalogue, the database schema, the API contract v1 and the mobile foundations |
| P1 — V1 build & integration | 4 Back-office V1 · 5 App revendeur V1 · 6 App délégué V1 · 7 Intégration | Server modules, back-office, reseller web, both Flutter apps, staging integration, field test, store readiness. Akram works on document templates, store assets, training material, V2 designs, design QA and the functional test campaign. |
| P2 — Acceptance, go-live & pilot | 8 Tests · 9 Pilote | End-to-end tests, the client's acceptance (PV de recette), production go-live, training, then a two-week pilot with a limited group of delegates and resellers |
| P3 — Generalisation | 10 Généralisation | After the three months: pilot improvements, progressive opening by zone, public store release, iOS if HOCO decides |
| P4 — V2 evolutions | §14.2 | Loyalty, packs, detailed credit, per-reseller price agreements, carrier and WhatsApp Business integrations, tour optimisation, advanced analytics |
119 open tasks · 173.75 d of planned effort (434.25 d from scratch) · plan ends 22 Feb 2027
| Phase | Effort | Start | End |
|---|---|---|---|
| P0 — Foundations (cadrage, UX/UI, architecture & contract) | 36.25 d | 18 Oct 2026 | 16 Nov 2026 |
| P1 — V1 build & integration | 73 d | 08 Nov 2026 | 27 Dec 2026 |
| P2 — Acceptance, go-live & pilot | 27.5 d | 23 Dec 2026 | 14 Jan 2027 |
| P3 — Generalisation (after the 3 months) | 10.5 d | 14 Jan 2027 | 24 Jan 2027 |
| P4 — V2 evolutions | 26.5 d | 21 Jan 2027 | 22 Feb 2027 |
Milestones
3-month frame: design → development → deployment — deadline 17 Jan 2027.
| Date | Milestone | Target | Reached when these tasks end |
|---|---|---|---|
| 18 Oct 2026 | Cadrage validated — validation sheet signed | — | PRJ-03 |
| 18 Oct 2026 | API contract v1 published (OpenAPI + mock server) | — | SRV-03 |
| 19 Oct 2026 | Server V1 feature-complete | — | SRV-26, SRV-40 |
| 21 Oct 2026 | Design system v1 ready (tokens + components) | — | DES-04 |
| 22 Oct 2026 | Screen inventory frozen | — | DES-05 |
| 29 Oct 2026 | Reseller app designs ready for client review | — | DES-10 |
| 05 Nov 2026 | Delegate app designs ready for client review | — | DES-14 |
| 08 Nov 2026 | Mobile foundations ready | — | MOB-11 |
| 12 Nov 2026 | Back-office designs ready for client review | — | DES-19 |
| 16 Nov 2026 | Design handoff complete | — | DES-21 |
| 03 Dec 2026 | Back-office and reseller web V1 feature-complete | — | DSH-12, WEB-05, WEB-06 |
| 15 Dec 2026 | Mobile apps V1 feature-complete | — | MDA-12 |
| 22 Dec 2026 | Staging integration complete | — | MOB-14, SRV-28 |
| 28 Dec 2026 | Acceptance report (PV de recette) signed | — | QA-02 |
| 29 Dec 2026 | Production go-live | on time — 17 Jan 2027 | LCH-01 |
| 30 Dec 2026 | Pilot starts | on time — 17 Jan 2027 | LCH-02 |
| 14 Jan 2027 | Pilot go / no-go | — | LCH-03, LCH-03B |
| 21 Jan 2027 | Generalisation complete | — | LCH-05 |
| 22 Feb 2027 | V2 delivered | — | SRV-38, DSH-21, MDA-20, WEB-20, DQA-12 |
Phases per person
18 Oct 2026 → 22 Feb 2027
Oct 2026Nov 2026Dec 2026Jan 2027Feb 202718/1025/101/118/1115/1122/1129/116/1213/1220/1227/123/110/117/124/131/17/214/221/2
Milestones
Anis — Full-stack developer
Imad — Mobile developer (Flutter)
Akram — UI/UX designer
AnisImadAkramV2 scopePublic holiday◆ Milestone (hover for name)
Week by week
| Week | Anis | Imad | Akram |
|---|---|---|---|
| Sun 18 Oct → Thu 22 Oct | PRJ-03 Cadrage workshop with HOCO — rules, V1/V2 split, open decisionsOPS-02 CI/CD & environments — staging, pre-production, production | MOB-01 Flutter monorepo — workspace, two apps, flavors, CIMOB-02 Core package — HTTP client, interceptors, errors, storage, loggingMOB-07 Localisation & formattingMOB-04 Flutter design system — tokens, theme, components | DES-01 Day 1 — Kickoff, reference audit & Claude Design setupDES-02 Day 2 — Foundations & design tokensDES-03 Day 3 — Mobile component libraryDES-04 Day 4 — Web & back-office components and page templatesDES-05 Day 5 — Screen inventory validation, user flows & wireframes |
| Sun 25 Oct → Thu 29 Oct | — buffer — | MOB-04 Flutter design system — tokens, theme, componentsMOB-03 API client from the OpenAPI contract + mock server workflowMOB-05 Navigation, app shells & system statesMOB-06 Authentication flows (both apps)MOB-08 Push notifications foundationMOB-09 Offline foundation for the delegate app (local DB + outbox sync) | DES-06 Day 6 — Reseller app: onboarding & accountDES-07 Day 7 — Reseller app: home, search & catalogDES-08 Day 8 — Reseller app: product, cart & checkoutDES-09 Day 9 — Reseller app: orders & financeDES-10 Day 10 — Reseller app: promotions, notifications, account, support |
| Sun 01 Nov → Thu 05 Nov | — buffer — | MOB-09 Offline foundation for the delegate app (local DB + outbox sync)MOB-10 Location, maps & consent foundationMOB-11 Media capture & uploads | DES-11 Day 11 — Delegate app: access, home, profileDES-12 Day 12 — Delegate app: tour programme, map & POS sheetDES-13 Day 13 — Delegate app: visit, report, prospects, follow-upsDES-14 Day 14 — Delegate app: sign-up, invitation, first order, closing |
| Sun 08 Nov → Thu 12 Nov | DSH-01 Back-office foundation — shell, auth, navigation, data patternsDSH-03 Back-office CRM pagesDSH-04 Back-office catalog & pricing pages | MOB-11 Media capture & uploadsMRA-01 Reseller app — homeMRA-02 Reseller app — catalog, search, scanner, filtersMRA-03 Reseller app — product detail & favoritesMRA-04 Reseller app — cart, checkout & confirmation | DES-15 Day 15 — Back-office: shell, access & dashboardsDES-16 Day 16 — Back-office: CRMDES-17 Day 17 — Back-office: catalog, pricing & stockDES-18 Day 18 — Back-office: orders, delivery & financeDES-19 Day 19 — Back-office: field ops, promotions, support, reports, admin |
| Sun 15 Nov → Thu 19 Nov | DSH-04 Back-office catalog & pricing pagesDSH-05 Back-office stock pagesDSH-06 Back-office orders & delivery pagesDSH-08 Back-office field operations pagesDSH-13 Back-office returns & after-sales pages | MRA-04 Reseller app — cart, checkout & confirmationMRA-05 Reseller app — orders, tracking & assisted-order confirmationMRA-06 Reseller app — promotions & daily offersMRA-07 Reseller app — account, store, finance & settingsMRA-08 Reseller app — notifications & support | DES-20 Day 20 — Reseller web: responsive layoutsDES-21 Day 21 — Prototypes, design QA & handoffDES-22 Client feedback round & design revisionsDES-23 Smart notifications design — Notification Centre, action buttons, promotion tabs, flash-sale countdownDQA-09 Document templates — invoice, delivery note, picking list, receipt |
| Sun 22 Nov → Thu 26 Nov | DSH-13 Back-office returns & after-sales pagesDSH-07 Back-office finance pages (V1)DSH-09 Back-office promotions & banners pagesDSH-10 Back-office support, announcements & notification settingsDSH-14 Back-office — commercial push, new catalogue, flash-sale fields, complementary products & smart-notification settingsDSH-02 Back-office dashboardsDSH-11 Back-office reports & export centreDSH-12 Back-office administration pages | MRA-08 Reseller app — notifications & supportMRA-09 Reseller app — invitation attributionMRA-10 Reseller app — returns & live order updatesMRA-11 Reseller app — Notification Centre, action buttons, group preferences, promotion tabs & flash-sale countdownMDA-01 Delegate app — home, profile, zone, objectives | DQA-09 Document templates — invoice, delivery note, picking list, receiptDQA-10 Notification & message copy — push, SMS, email, WhatsApp textsDQA-01 Store assets — icons, splash, screenshots, feature graphicsDQA-06 Training materials — reseller guide, delegate field guide, admin referenceDQA-07 Field kit — invitation QR flyer & stickerDES-30 V2 designs — loyalty, packs, returns, credit, analytics |
| Sun 29 Nov → Thu 03 Dec | DSH-12 Back-office administration pagesWEB-01 Reseller web — foundation & account flowsWEB-02 Reseller web — home, catalog, product, favoritesWEB-03 Reseller web — cart & checkoutWEB-04 Reseller web — orders & financeWEB-05 Reseller web — promotions, notifications, account, supportWEB-06 Reseller web — Notification Centre, action buttons, group preferences, promotion tabs & flash-sale countdown | MDA-02 Delegate app — tour programme & calendarMDA-03 Delegate app — map, navigation & arrival check-inMDA-04 Delegate app — point-of-sale sheet & prospects listMDA-05 Delegate app — visit flow | DES-30 V2 designs — loyalty, packs, returns, credit, analytics |
| Sun 06 Dec → Thu 10 Dec | — buffer — | MDA-05 Delegate app — visit flowMDA-06 Delegate app — visit report & follow-upsMDA-07 Delegate app — new reseller (offline) & editMDA-08 Delegate app — invitation (QR, share, tracking)MDA-09 Delegate app — first-order assistance & orders | DES-30 V2 designs — loyalty, packs, returns, credit, analyticsDQA-02 Design QA — reseller app build |
| Sun 13 Dec → Thu 17 Dec | — buffer — | MDA-10 Delegate app — tour closing, reports & performanceMDA-11 Delegate app — messages, settings & sync centreMDA-12 Delegate app — location sampling during toursMOB-12 Staging integration — real API, edge states, performanceMOB-13 Field test with a delegate — GPS, weak network, offline | DQA-03 Design QA — delegate app buildDQA-04 Design QA — back-officeDQA-05 Design QA — reseller web |
| Sun 20 Dec → Thu 24 Dec | QA-01 End-to-end integration testing on stagingQA-02 Client acceptance (recette) on pre-production & PV | MOB-13 Field test with a delegate — GPS, weak network, offlineMOB-14 Store readiness — Play Console tracks, data safety, location declarationMOB-15 Mobile test automation & hardeningMOB-17 Design QA fixes & accessibility pass (both apps) | QA-03 Functional test campaign — scripted scenarios on staging |
| Sun 27 Dec → Thu 31 Dec | QA-02 Client acceptance (recette) on pre-production & PVLCH-01 Production go-live — deploy, import data, monitoringLCH-02 Training — administrators, managers and pilot delegatesLCH-03 Pilot (2 weeks) — support, daily triage, hotfixes (Anis) | MOB-17 Design QA fixes & accessibility pass (both apps)LCH-03B Pilot (2 weeks) — mobile support & hotfixes (Imad) | DQA-08 Pilot UX observation & feedback synthesis |
| Sun 03 Jan → Thu 07 Jan | LCH-03 Pilot (2 weeks) — support, daily triage, hotfixes (Anis) | LCH-03B Pilot (2 weeks) — mobile support & hotfixes (Imad) | DQA-08 Pilot UX observation & feedback synthesis |
| Sun 10 Jan → Thu 14 Jan | LCH-03 Pilot (2 weeks) — support, daily triage, hotfixes (Anis)LCH-04 Pilot improvements — server & back-office | LCH-03B Pilot (2 weeks) — mobile support & hotfixes (Imad) | — buffer — |
| Sun 17 Jan → Thu 21 Jan | LCH-04 Pilot improvements — server & back-officeLCH-05 Generalisation roll-out — waves by zone, public store releaseSRV-29 V2 API contract — loyalty, packs, credit, returns | MOB-18 Pilot improvements — mobileMOB-16 iOS build & App Store release (on client decision) | — buffer — |
The critical path
Anis's lane is the longest. The server, the back-office and the reseller web all run through it, so it sets the go-live date. The other two lanes are planned so they never wait on him for long:
- The contract unblocks mobile. Imad generates his Dart client from the OpenAPI document as soon as SRV-03 lands and works against the mock server. Real integration happens in MOB-12 once the server modules exist.
- The design unblocks screens. Each Flutter feature task depends on its design day, and the back-office foundation waits for the back-office shell design.
- Testing never waits for the end. Akram tests every build as it lands (design QA, then the scripted functional campaign), so the client acceptance starts from a clean staging environment.
- Buffers are visible, not hidden. Imad has a buffer at the end of December after store readiness, and Akram between design-QA rounds. That is the first capacity to spend if something slips.
Calendar facts
| Fact | Effect on the plan |
|---|---|
| Working week Sunday–Thursday | Friday and Saturday never hold work |
| 1 Nov 2026 — Anniversary of the Revolution | Removed from every lane |
| 12 Jan 2027 — Yennayer | Removed — it falls in the pilot |
| End-of-year period | Normal working days in Algeria; plan the client acceptance sessions with HOCO early so their availability is not a surprise |
| Ramadan ≈ 8 Feb 2027 | Starts after the V1 deployment and the pilot |
Every task
17 Oct 2026 → 18 Feb 2027
Oct 2026Nov 2026Dec 2026Jan 2027Feb 202711/1018/1025/101/118/1115/1122/1129/116/1213/1220/1227/123/110/117/124/131/17/214/2
Milestones
P0 — Foundations (cadrage, UX/UI, architecture & contract)
SRV-06RBAC & data scopes
P1 — V1 build & integration
SRV-11Catalog module
SRV-12Pricing engine
SRV-13Inventory module
SRV-10Geography & zones module
SRV-15Cart & checkout rules
SRV-39Smart notifications — contract & schema (groups, actions, flash sales, complementary products)
DSH-03Back-office CRM pages
DSH-05Back-office stock pages
DSH-02Back-office dashboards
P2 — Acceptance, go-live & pilot
P3 — Generalisation (after the 3 months)
AnisV2 scopePublic holiday◆ Milestone (hover for name)
If dates slip
Three months leaves no slack in Anis's lane, so a slip is handled the same week, never at the end. The plan does not invent capacity. These are the real levers, in the order we would use them:
- Spend the visible buffers. Imad's late-December buffer (test automation and the accessibility pass can move), and Akram's gaps between design-QA rounds.
- Move non-essential V1 scope after go-live, with HOCO's agreement. Candidates: some back-office reports, the import wizard (data can be imported by script for the pilot), the stock inventory sessions, and announcements.
- Shorten the pilot to one week and fold the rest into the first generalisation wave.
- Add capacity. A second TypeScript developer on the back-office halves the longest lane.
- Cut scope with HOCO through the change-request process, never silently.