Delivery Plan
The end-to-end plan from foundation to scale — phases, generated tasks, milestones and the test strategy, every task traced to a requirement.
This is the end-to-end delivery view of the whole system: six phases from foundation to scale, every phase broken into tasks, and every task generated from — and linked to — one functional requirement. Nothing here is maintained by hand: the phase pages and milestones are produced by bun scripts/generate-plan.ts from the living documentation, so the plan can never drift from the requirements.
How it fits together
- A task implements exactly one functional requirement and inherits its MoSCoW priority. Its phase comes from the requirement's business trace: FR → BR → the BRD's phase column.
- Covered by links the user flows and system workflows that exercise the task — the same attribution as the coverage page.
- Tasks carry no invented estimates. Size a phase by its task count and priority mix (shown on each page and in milestones); the definition of done, not a date, closes a phase.
The phases
P1 — Foundation
Accounts, applications and approval, tenancy.
P2 — Single-vehicle pilot
Trip creation, booking, EGP payments.
P3 — Operational depth
Multi-vehicle, programs, moderator app, check-in.
P4 — Marketplace supply
Drivers, photographers, deals, media.
P5 — Monetization and Gulf
Plans, gates, coupons, accounting, SAR and AED.
P6 — Family and scale
Tracking, parents, analytics, public API.
Milestones
The phase ladder with gates and decisions to close.
Test Strategy
How acceptance criteria become the test pyramid.
Reading a phase page
Each phase page opens with its theme and definition of done (verbatim from BRD section 3.3), followed by the cross-cutting platform tasks, then one epic per module with its task table, and finally the decisions to close — the open decisions cited by that phase's requirements, which should be settled before the phase starts, not during it.