KODA Project - Project Schedule & Timeline
Detailed Scheduling Document
Table of Contents
Document Control
| Field | Details |
|---|---|
| Project Name | KODA Multi-Tenant Beauty & Wellness Platform |
| Document Version | 1.0 |
| Date | October 31, 2025 |
| Prepared By | Project Management Office |
| Status | Draft |
| Baseline Date | November 1, 2025 |
| Project Start | November 1, 2025 |
| Project End | July 15, 2026 |
| Total Duration | 8.4 months (36 weeks) |
Executive Summary
Schedule Overview
| Metric | Value |
|---|---|
| Total Duration | 8.4 months (36 weeks) |
| Total Working Days | ~180 days |
| Total Development Hours | 6,364 hours |
| Number of Phases | 3 |
| Number of Milestones | 22 major milestones |
| Team Size | 9 members |
| Start Date | November 1, 2025 |
| Phase 1 Completion | March 31, 2026 |
| Phase 2 Completion | May 31, 2026 |
| Phase 3 Completion | July 15, 2026 |
Phase Summary
| Phase | Start Date | End Date | Duration | Milestones | Deliverables |
|---|---|---|---|---|---|
| Phase 1 | Nov 1, 2025 | Mar 31, 2026 | 20 weeks | M1-M12 | 7 applications |
| Phase 2 | Apr 1, 2026 | May 31, 2026 | 8 weeks | M13-M17 | Enhanced features |
| Phase 3 | Jun 1, 2026 | Jul 15, 2026 | 6.4 weeks | M18-M22 | AI & advanced |
Schedule Management Approach
Scheduling Methodology
Approach: Agile-Hybrid with Phase-based delivery
Key Principles
- Fixed Phases: Phase dates are fixed, features may flex
- Milestone-Driven: Progress tracked via milestone completion
- Parallel Execution: Teams work simultaneously on non-dependent tasks
- Sprint-Based: 2-week sprints within each phase
- Critical Path Management: Focus on longest dependent task chain
Schedule Development Process
- Work Breakdown: Decompose project into tasks (WBS)
- Sequencing: Identify dependencies and relationships
- Duration Estimation: Estimate task durations (hours → days → weeks)
- Resource Assignment: Allocate team members to tasks
- Schedule Optimization: Compress through parallelization
- Baseline Approval: Freeze baseline schedule
- Monitoring: Track progress weekly
- Updates: Revise schedule as needed (with change control)
Schedule Assumptions
- Work Week: 5 days/week (Monday-Friday)
- Work Day: 8 hours/day
- Team Availability: 100% allocation (except part-time DevOps)
- Holidays: Jordan public holidays observed
- No Major Delays: No extended team absences
- Stakeholder Availability: Timely reviews and approvals
Schedule Constraints
- Fixed Deadline: Phase 1 must launch by Month 5
- Resource Constraints: Limited team size
- Dependencies: Some tasks cannot start until others complete
- External Dependencies: Third-party approvals (App Store, APIs)
Master Schedule
High-Level Timeline
Note: The following Gantt chart visualization represents the master schedule for all three phases of the KODA project.
Master Schedule Table
| Activity | Start Date | End Date | Duration | Predecessors | Team |
|---|---|---|---|---|---|
| Project Initiation | Nov 1, 2025 | Nov 8, 2025 | 1 week | - | PM, All |
| Phase 1: Core Launch | Nov 1, 2025 | Mar 31, 2026 | 20 weeks | - | All Teams |
| Phase 2: Enhanced | Apr 1, 2026 | May 31, 2026 | 8 weeks | Phase 1 | Backend, Flutter, ReactJS, QA |
| Phase 3: AI & Advanced | Jun 1, 2026 | Jul 15, 2026 | 6.4 weeks | Phase 2 | Backend, DevOps, QA |
| Project Closure | Jul 15, 2026 | Jul 31, 2026 | 2 weeks | Phase 3 | PM, All |
Phase 1 Schedule
Phase 1 Overview
Phase 1 Sprint Schedule
Sprint Duration: 2 weeks
Total Sprints: 10 sprints
| Sprint | Start Date | End Date | Focus | Teams |
|---|---|---|---|---|
| Sprint 1 | Nov 1, 2025 | Nov 15, 2025 | Infrastructure, Design Start, Backend Setup | DevOps, UI/UX, Backend |
| Sprint 2 | Nov 16, 2025 | Nov 29, 2025 | Design Complete, Auth Backend, Mobile Start | UI/UX, Backend, Flutter |
| Sprint 3 | Nov 30, 2025 | Dec 13, 2025 | Backend APIs, Mobile Auth, Website Start | Backend, Flutter, ReactJS |
| Sprint 4 | Dec 14, 2025 | Dec 27, 2025 | Backend Continue, Mobile Alpha, CORE Start | Backend, Flutter, ReactJS |
| Sprint 5 | Dec 28, 2025 | Jan 10, 2026 | Backend APIs, Mobile Continue, Website Beta | Backend, Flutter, ReactJS |
| Sprint 6 | Jan 11, 2026 | Jan 24, 2026 | Backend Complete, Mobile Features, CORE Dev | Backend, Flutter, ReactJS |
| Sprint 7 | Jan 25, 2026 | Feb 7, 2026 | Backend Final, Mobile Beta Prep, CORE Continue | Backend, Flutter, ReactJS |
| Sprint 8 | Feb 8, 2026 | Feb 21, 2026 | Mobile/Team Beta, CORE Continue, QA Start | Flutter, ReactJS, QA |
| Sprint 9 | Feb 22, 2026 | Mar 7, 2026 | CORE Beta, Migration, System Testing | ReactJS, Backend, QA |
| Sprint 10 | Mar 8, 2026 | Mar 21, 2026 | UAT, Final Testing, Go-Live Prep | All Teams |
| Launch | Mar 22, 2026 | Mar 31, 2026 | Production Deployment | All Teams |
Phase 2 Schedule
Phase 2 Overview
Phase 2 Sprint Schedule
Sprint Duration: 2 weeks
Total Sprints: 4 sprints
| Sprint | Start Date | End Date | Focus | Teams |
|---|---|---|---|---|
| Sprint 11 | Apr 1, 2026 | Apr 14, 2026 | Backend: Loyalty, Passport, Packages Start | Backend |
| Sprint 12 | Apr 15, 2026 | Apr 28, 2026 | Backend Complete, Mobile Features Start | Backend, Flutter |
| Sprint 13 | Apr 29, 2026 | May 12, 2026 | Mobile Features, CORE Enhancements | Flutter, ReactJS |
| Sprint 14 | May 13, 2026 | May 26, 2026 | Testing, CORE Complete | ReactJS, QA |
| Launch | May 27, 2026 | May 31, 2026 | Phase 2 Deployment | All Teams |
Phase 3 Schedule
Phase 3 Overview
Phase 3 Sprint Schedule
Sprint Duration: 2 weeks
Total Sprints: 3+ sprints
| Sprint | Start Date | End Date | Focus | Teams |
|---|---|---|---|---|
| Sprint 15 | Jun 1, 2026 | Jun 14, 2026 | AI Foundation, WebSocket Start | Backend, DevOps |
| Sprint 16 | Jun 15, 2026 | Jun 28, 2026 | AI Foundation Complete, Social/Voice Start | Backend |
| Sprint 17 | Jun 29, 2026 | Jul 12, 2026 | Integration, Testing | Backend, QA |
| Launch | Jul 13, 2026 | Jul 15, 2026 | Phase 3 Deployment | All Teams |
Milestone Schedule
Complete Milestone List
| ID | Milestone Name | Target Date | Phase | Critical? | Deliverables |
|---|---|---|---|---|---|
| M1 | Infrastructure Ready | Nov 15, 2025 | 1 | Yes | Dev/staging/prod environments |
| M2 | Design Complete | Nov 25, 2025 | 1 | Yes | All UI/UX designs approved |
| M3 | Auth & Multi-tenant Backend | Dec 2, 2025 | 1 | Yes | Core auth APIs tested |
| M4 | Mobile App Alpha | Dec 23, 2025 | 1 | No | Basic customer app |
| M5 | Staff App Alpha | Dec 23, 2025 | 1 | No | Basic staff operations |
| M6 | Backend APIs Complete | Feb 10, 2026 | 1 | Yes | All Phase 1 endpoints |
| M7 | Website Beta Launch | Jan 13, 2026 | 1 | No | Public website live |
| M8 | Customer App Beta | Feb 24, 2026 | 1 | Yes | Full customer app |
| M9 | Staff App Beta | Feb 24, 2026 | 1 | Yes | Full staff app |
| M10 | KODA CORE Beta | Mar 17, 2026 | 1 | Yes | Admin panel operational |
| M11 | Data Migration Complete | Mar 24, 2026 | 1 | Yes | 55k+ records validated |
| M12 | Phase 1 Launch | Mar 31, 2026 | 1 | Yes | All apps in production |
| M13 | Loyalty Backend | Apr 22, 2026 | 2 | Yes | Points & tiers working |
| M14 | Passport Backend | Apr 22, 2026 | 2 | Yes | Partner mgmt ready |
| M15 | Mobile Apps Updated | May 6, 2026 | 2 | Yes | Loyalty & Passport in apps |
| M16 | KODA CORE Enhanced | May 13, 2026 | 2 | Yes | Full CRM features |
| M17 | Phase 2 Launch | May 31, 2026 | 2 | Yes | Enhanced features live |
| M18 | AI Foundation | Jun 22, 2026 | 3 | Yes | AI reports working |
| M19 | Social Media Integration | Jul 6, 2026 | 3 | Yes | WhatsApp/Instagram/FB bots |
| M20 | Voice Integration | Jul 6, 2026 | 3 | Yes | SIP voice AI |
| M21 | WebSocket Complete | Jun 22, 2026 | 3 | No | Real-time notifications |
| M22 | Phase 3 Launch | Jul 15, 2026 | 3 | Yes | Full AI capabilities |
Critical Milestones (On Critical Path)
The following 11 milestones are on the critical path and cannot be delayed without affecting project end date:
- M1: Infrastructure Ready
- M2: Design Complete
- M3: Auth & Multi-tenant Backend
- M6: Backend APIs Complete
- M8: Customer App Beta
- M10: KODA CORE Beta
- M11: Data Migration Complete
- M12: Phase 1 Launch
- M13: Loyalty Backend
- M18: AI Foundation
- M22: Phase 3 Launch
Resource Schedule
Team Member Schedule
| Team Member | Start Date | End Date | Duration | Allocation | Total Hours |
|---|---|---|---|---|---|
| Project Manager | Nov 1, 2025 | Jul 31, 2026 | 8.4 months | 100% | 1,344h |
| Backend Lead | Nov 1, 2025 | Jul 15, 2026 | 8.4 months | 100% | 1,608h |
| Backend Developer | Nov 1, 2025 | Jul 15, 2026 | 8.4 months | 100% | 1,072h |
| Flutter Developer | Nov 18, 2025 | May 6, 2026 | 5.7 months | 100% | 1,142h |
| Frontend Lead | Nov 18, 2025 | May 13, 2026 | 4.8 months | 100% | 547h |
| Frontend Developer | Nov 18, 2025 | May 13, 2026 | 4.8 months | 100% | 365h |
| UI/UX Designer | Nov 4, 2025 | Dec 20, 2025 | 1.5 months | 100% | 200h |
| DevOps Engineer | Nov 1, 2025 | Jul 15, 2026 | 8.4 months | Part-time | 140h |
| QA Engineer | Jan 13, 2026 | Jul 15, 2026 | 3.1 months | 100% | 570h |
Resource Loading Chart
Month: Nov Dec Jan Feb Mar Apr May Jun Jul
PM ████████████████████████████████████████████████████
Backend Lead ████████████████████████████████████████████████████
Backend Dev ████████████████████████████████████████████████████
Flutter ░░░░░████████████████████████████████░░░░░░░░░░░░░░
Frontend Lead ░░░░░████████████████████████████░░░░░░░░░░░░░░░░░░
Frontend Dev ░░░░░████████████████████████████░░░░░░░░░░░░░░░░░░
UI/UX ░██████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
DevOps ████████████████████████████████████████████████████
QA ░░░░░░░░░░██████████████████████████████████████████
Schedule Baseline
Baseline Dates
The following baseline will be frozen upon approval:
| Baseline Element | Baseline Date | Current Forecast | Variance |
|---|---|---|---|
| Project Start | Nov 1, 2025 | Nov 1, 2025 | 0 days |
| Phase 1 Start | Nov 1, 2025 | Nov 1, 2025 | 0 days |
| Phase 1 End | Mar 31, 2026 | Mar 31, 2026 | 0 days |
| Phase 2 End | May 31, 2026 | May 31, 2026 | 0 days |
| Phase 3 End | Jul 15, 2026 | Jul 15, 2026 | 0 days |
| Project End | Jul 31, 2026 | Jul 31, 2026 | 0 days |
Baseline Change Control
Changes to baseline dates require:
- Formal change request submitted
- Impact analysis (cost, scope, resources)
- Change Control Board review
- Executive Sponsor approval
- Baseline re-approval and redistribution
Schedule Monitoring & Control
Progress Tracking
Frequency: Weekly
Method: Milestone tracking + Sprint burndown
Tools: Project management software + Status reports
Tracking Metrics
- Milestone Completion: On-time vs. delayed
- Sprint Velocity: Story points completed per sprint
- Schedule Variance (SV): Earned Value - Planned Value
- Schedule Performance Index (SPI): EV / PV
Status Reporting
Weekly Status
- Milestones achieved this week
- Milestones planned for next week
- Schedule variances (if any)
- Risks to schedule
- Corrective actions
Monthly Status
- Phase progress (% complete)
- Milestone completion rate
- Schedule performance trends
- Forecast to completion
Schedule Risk Management
Identified Schedule Risks
| Risk | Mitigation |
|---|---|
| Single Flutter Developer Bottleneck risk |
Prioritize tasks, consider support developer |
| Third-Party Approvals App Store delays |
Early submission, compliance review |
| Data Migration Complexity underestimated |
Early testing, parallel migration |
| Scope Creep Requirements changes |
Change control process |
| Team Availability Sick leave, holidays |
Buffer in estimates |
Recovery Actions
If schedule slips:
- Fast Tracking: Overlap dependent activities (accept risk)
- Crashing: Add resources to critical path activities
- Descoping: Move non-critical features to future phases
- Overtime: Temporary increase in work hours (limited use)
Approval & Sign-Off
Schedule Baseline Approval
| Role | Name | Signature | Date |
|---|---|---|---|
| Project Manager | [Name] | _________________ | ____/____/2025 |
| Technical Lead | [Name] | _________________ | ____/____/2025 |
| Product Owner | [Name] | _________________ | ____/____/2025 |
| Executive Sponsor | [Name] | _________________ | ____/____/2025 |
Schedule Change Log
| Change # | Date | Description | Impact | Approved By | New Baseline |
|---|---|---|---|---|---|
| No changes recorded | |||||