AI Project Scoper & Resource Planner
Full Gantt β†—
Drop your RFP, Scope PDF, Word, Excel, or notes hereClick to browse files β€” or
Scenarios

Baseline Plan β€” Plan, Hours, Resources & Onsite Logistics

2026-11-17 β†’ 2026-12-21 Β· 8h/day standard capacity

Total Effort Hours188 hrsRemote 188h Β· Onsite 0h
Resources Needed5 RolesMax daily load: 6.8h/day (cap 8h)
Duration & Schedule24 Working Days2026-11-17 β†’ 2026-12-21 Β· 4 phases
Onsite Days & Logistics0 Onsite Days🍽️ 0d Per Diem Β· πŸš— 0d Car Β· 🏨 0n Hotel Β· ✈️ 0 Flights

Resources, Agile Base Office, Remote vs. Onsite by Phase & Travel

Client Site: Amman, Jordan β€” Roles in the same city default to Local Onsite (0 travel); roles in a different city get Travel Onsite
Resource / RoleAgile Base OfficeTotal HrsRemoteOnsiteOnsite DaysOnsite Presence by PhaseTravel Package (PD Β· Car Β· Hotel Β· Air)Peak / Day
PMProject Manager / Delivery Lead
27.0h27.0h0h0 d
100% Remote (4 phases)
No travel2.8h/d
CRMOdoo CRM Functional Consultant
52.0h52.0h0h0 d
100% Remote (4 phases)
No travel6.8h/d
INTIntegration & DevOps Engineer
Integration & DevOps Engineer (AWS / Meta Cloud API)
61.0h61.0h0h0 d
100% Remote (3 phases)
No travel5.6h/d
QAQA & Test Analyst
QA & SIT/UAT Test Analyst
25.0h25.0h0h0 d
100% Remote (4 phases)
No travel2.7h/d
DEVOdoo Developer
Odoo Developer (build pair & dashboard)
23.0h23.0h0h0 d
100% Remote (3 phases)
No travel2.7h/d
Total (5 roles)πŸ‡―πŸ‡΄ 5 Amman Β· πŸ‡ΈπŸ‡¦ 0 Riyadh188.0h188.0h0.0h0 dβ€”100% Remoteβ€”

Summary by Phase (Hours, Onsite Roles & Days)

4 delivery phases
PhaseWindowTasksTotal HrsOnsite DaysOnsite Roles in PhasePhase Travel Package
P1 Β· P1 Β· Mobilise, AWS Environment & v19 Compatibility Gate2026-11-17 β†’ 2026-11-26456.0h0 dAll Remoteβ€”
P2 Β· P2 Β· CRM Configuration, Tags & PDP Consent2026-11-23 β†’ 2026-12-01332.0h0 dAll Remoteβ€”
P3 Β· P3 Β· WhatsApp Cloud API, Templates & Dashboard2026-11-26 β†’ 2026-12-07353.0h0 dAll Remoteβ€”
P4 Β· P4 Β· Smoke Acceptance, Bilingual Docs & Handover2026-11-17 β†’ 2026-12-20447.0h0 dAll Remoteβ€”

Scope Summary & Sizing Assumptions

Captured during iterative scoping

200-hour Wave 1 pilot for Ψ§Ψ³ΩƒΨ§Ω†Ψ§Ψͺ (Amman): Odoo 20 Community self-hosted on the client's own AWS account (me-south-1, Bahrain) with production + staging, HTTPS and daily backup; 16h v20 compatibility Go/No-Go gate; standard Odoo CRM (leads, opportunities, pipeline, activities, ownership) with project + unit-type as standard tags (no custom code); client's own WhatsApp Cloud API number in one shared conversation view with 2 bilingual templates; ONE sales-funnel dashboard by source and channel; abbreviated bilingual AR/EN guide + one bilingual training session; 8 written smoke-acceptance scenarios with a 30-day defect window and no dedicated hypercare. Delivered 100% remotely by 3 Amman-based roles in parallel, 17 Nov – 10 Dec 2026.

In-Scope Deliverables

  • AWS deployment of Odoo 20 Community in the client-owned account (me-south-1): production + staging, HTTPS/TLS, daily automated backup, Meta webhook reachability β€” 40h
  • 16h v20 compatibility gate: real install on Odoo 20 Community + real WhatsApp send/receive + successful webhook, Go/No-Go before build
  • Standard Odoo CRM configuration (no Studio, no custom code): contacts, leads, opportunities, pipeline stages, activities/reminders, ownership and assignment β€” 24h
  • Project + unit-type interest captured as STANDARD Odoo TAGS on the lead (2-3 active projects) β€” zero extra hours
  • WhatsApp Cloud API from the client's own Meta account + single shared conversation view + exactly 2 bilingual templates (welcome/acknowledgement, appointment confirmation) β€” 48h
  • ONE dashboard: sales funnel by source and channel β€” 12h
  • Abbreviated bilingual AR/EN user guide + quick-reference card + ONE bilingual training session β€” 16h
  • 8 written smoke-acceptance scenarios issued before build + 30-day defect fix window β€” 16h
  • PMO, weekly status and change control inside the ceiling β€” 20h
  • Documented Runbook handover for AWS operations (backup restore, patching calendar, incident escalation) with client taking over daily operations β€” no uptime commitment retained

Key Assumptions & Benchmarks

  • HARD CEILING: 200 effort hours for the pilot; signed package content = 192h, contingency = 8h (one working day)
  • Pilot delivered by 3 roles from Agile's Amman office fully in parallel over 15-18 elapsed working days, closing before 11 Dec 2026, starting 17 Nov 2026
  • Zero onsite days and zero travel: both workshops are remote 4-hour sessions
  • UI bilingual at zero cost (Odoo ships ar and en); AR/EN uplift applies only to the 16h of guide, quick-reference card and training
  • WhatsApp Cloud API for the client's own number needs no App Review and no Business Verification to start β€” phone verification plus display-name review only; portfolio cap 250 unique recipients per rolling 24h against ~130/day current volume
  • Only 2 WhatsApp templates and 1 dashboard are submitted at pilot close; no hypercare beyond the 30-day defect window
  • Wave 2 will be re-estimated in writing after the pilot closes (target mid-April 2027, after Eid al-Fitr) covering Messenger, Instagram, 4 dashboards, 6 templates, website form, migration, full acceptance and hypercare β€” the date is indicative until the estimate is signed
  • Client holds the AWS account, billing and root IAM and operates the environment from the Runbook; Agile retains no uptime or recovery commitment
  • Client enters ~100-150 active customer records before go-live via an Agile-provided template; the gate closes 3 WD before launch with day-for-day slippage
  • Jordan PDP Law No. 24 of 2023 Art. 14/15 cross-border annex for me-south-1 must be signed by the client before go-live