Home / Documentation / Work Breakdown Structure

Work Breakdown Structure (WBS)

KODA Multi-Tenant Beauty & Wellness Platform

Document Version: 1.0
Date: October 31, 2025
Prepared By: Project Management Office
Status: Draft

Table of Contents

1. Executive Summary

Project Scope Summary

The KODA project delivers a comprehensive multi-tenant beauty and wellness platform through 7 interconnected applications across 3 major phases:

6,364
Total Hours
8.4
Months Duration
81,555
JOD Budget
3
Major Phases

WBS Hierarchy

KODA Project (Level 0)
├── Phase 1: Core Launch (Level 1)
│   ├── Infrastructure & Setup (Level 2)
│   ├── Design System (Level 2)
│   ├── Backend Development (Level 2)
│   ├── Mobile Apps Development (Level 2)
│   ├── Web Development (Level 2)
│   └── Quality Assurance (Level 2)
├── Phase 2: Enhanced Features (Level 1)
│   ├── Loyalty System (Level 2)
│   ├── Passport Network (Level 2)
│   └── Packages System (Level 2)
└── Phase 3: AI & Advanced (Level 1)
    ├── KODA AI Engine (Level 2)
    ├── Social Media Integration (Level 2)
    └── WebSocket System (Level 2)

2. Project Phases Overview

Phase Summary

Phase Duration Deliverables Hours % of Total Target
Phase 1 4 months Mobile App, Team App, Website, CORE Admin, Backend API 4,736 74% Month 5
Phase 2 2 months Loyalty, Passport, Packages, Enhanced CORE 788 12% Month 7
Phase 3 2.4 months AI Engine, Social Media, Voice, WebSocket 840 13% Month 9
Total 8.4 months 7 Applications 6,364 100% -

3. Phase 1: Core Launch

Phase 1 Overview

Objective: Launch customer-facing app, staff operations app, website, and essential admin panel

Duration: 4 months (Weeks 1-20) Effort: 4,736 hours Team: All teams

Phase 1 Milestones

ID Milestone Target Dependencies Success Criteria
M1 Infrastructure & Setup Week 2 None Dev/staging/prod environments operational
M2 Design System Complete Week 4 M1 All UI/UX designs approved and documented
M3 Auth & Multi-tenant Backend Week 6 M1 Core authentication APIs tested
M6 Backend APIs Complete Week 14 M3 All Phase 1 endpoints ready
M8 Customer App Beta Week 16 M4, M6 Full customer app in beta
M12 Phase 1 Launch Week 22 M8, M9, M10, M11 All apps in production

Phase 1 Deliverables by Application

1. KODA Mobile App (Customer)

470 hours

Platform: Flutter (iOS & Android)

Key Features:

  • Authentication & User Management
  • Service Browsing & Booking
  • Golden Opportunities
  • Payment Processing
  • Profile Management
  • Notifications

Acceptance Criteria:

  • Published on App Store & Google Play
  • Core booking flow functional
  • Payment gateway integrated
  • 99.9% crash-free rate

2. KODA Team App (Staff Operations)

474 hours

Platform: Flutter (iOS & Android)

Key Features:

  • Staff Authentication
  • Customer Check-in/Check-out
  • Session Management
  • Mobile POS
  • Schedule Viewing
  • Real-time Updates

3. KODA Website (Public)

322 hours

Platform: ReactJS

Key Features:

  • Marketing Pages
  • Service Catalog
  • Basic Booking
  • Contact Forms
  • SEO Optimized

Acceptance Criteria:

  • Lighthouse score >90
  • Mobile responsive
  • Accessibility compliant

4. KODA CORE (Admin Panel)

900 hours

Platform: ReactJS

Key Features:

  • Comprehensive CRM (360° customer view)
  • Reservations Calendar
  • Point of Sale (POS)
  • Basic HR Module
  • Essential Reports (5 reports)
  • Settings Management

5. KODA Backend API

1,880 hours

Platform: Laravel (PHP)

Key Features:

  • Multi-tenant Architecture
  • RESTful APIs (all applications)
  • Authentication & Authorization
  • Payment Gateway Integration
  • Database Management
  • Activity Logging

Acceptance Criteria:

  • All Phase 1 endpoints documented
  • API response time <200ms (p95)
  • 100% test coverage on critical paths
  • Security audit passed

Phase 1 Work Packages Summary

Work Package Owner Hours Key Tasks
WP1.1 DevOps 80 Infrastructure setup, CI/CD
WP1.2 UI/UX 200 Design system, all app designs
WP1.3 Backend 1,880 Multi-tenant, APIs, integrations
WP1.4 Flutter 944 Mobile App + Team App
WP1.5 ReactJS 1,332 Website + KODA CORE
WP1.6 QA 300 Testing, security, UAT
Total 4,736 -

4. Phase 2: Enhanced Features

Phase 2 Overview

Objective: Add loyalty program, passport partner network, packages system, and enhanced admin features

Duration: 2 months (Weeks 21-28) Effort: 788 hours Team: Backend, Flutter, ReactJS, QA

Phase 2 Deliverables

1. Loyalty System

164 hours

Components:

  • Backend APIs (80h)
  • Mobile App Features (84h)

Features:

  • 3-tier system (Insider, Ambassador, Royal)
  • Points earning & redemption
  • Tier progression

2. Passport Partner Network

122 hours

Components:

  • Backend APIs (60h)
  • Mobile App Features (62h)

Features:

  • Partner management
  • QR-based benefit activation
  • Usage tracking

3. Packages System

152 hours

Components:

  • Backend APIs (100h)
  • Mobile App Features (52h)

Features:

  • Package purchase
  • Session tracking
  • Package freezing

4. Enhanced KODA CORE

200 hours

New Modules:

  • Complete HR (payroll, advances)
  • Advanced Reports (20+ reports)
  • Asset Management
  • Sales Appointments

5. Phase 3: AI & Advanced

Phase 3 Overview

Objective: Launch AI engine with social media integration, voice capabilities, and real-time notifications

Duration: 2.4 months (Weeks 29-38) Effort: 840 hours Team: Backend (AI), DevOps, Integration, QA

Phase 3 Deliverables

1. KODA AI Engine

560 hours
AI Foundation (200h)
  • Google AI Studio integration
  • Knowledge base system
  • AI report generation
Social Media (200h)
  • WhatsApp Business API
  • Instagram/Facebook integration
  • Auto-response system
Voice (160h)
  • SIP voice calls
  • Natural language understanding
  • Intent detection

2. KODA WS (WebSocket)

140 hours

Features:

  • EMQX configuration
  • Topic architecture
  • Publisher service
  • Client SDKs (Flutter, JavaScript)
  • Real-time notifications

6. Resource Allocation

Total Hours by Team

Team Phase 1 Phase 2 Phase 3 Total Hours % of Total
Backend 1,880 240 560 2,680 42%
Flutter 944 198 0 1,142 18%
ReactJS 1,332 200 0 1,532 24%
UI/UX 200 0 0 200 3%
DevOps 80 0 60 140 2%
QA 300 150 120 570 9%
Integration 0 0 100 100 2%
Total 4,736 788 840 6,364 100%

Team Composition

Role Level Count Total Months
Project Manager Senior 1 8.4
Backend Lead Senior 1 8.4
Backend Developer Mid-level 1 8.4
Flutter Developer Senior 1 5.7
Frontend Lead (ReactJS) Senior 1 4.8
Frontend Developer Mid-level 1 4.8
UI/UX Designer Senior 1 1.5
DevOps Engineer Part-time 1 8.4
QA Engineer Mid-level 1 3.1
Total Team 9 -

7. Dependencies & Critical Path

Critical Path

The longest chain of dependent tasks determining minimum project duration:

M1 (Infrastructure)
→
M2 (Design)
→
M3 (Auth Backend)
→
M6 (Backend APIs)
→
M8 (Customer App)
→
M12 (Phase 1 Launch)

Critical Path Duration: 48 weeks (~11 months) if sequential

Actual Duration: 36 weeks (8.4 months) through parallelization

Parallelization Strategy

How we compress 48 weeks to 36 weeks:

Week 1-4: Setup Phase

  • Infrastructure (DevOps)
  • Design System (UI/UX)
  • Backend Architecture (Backend)

Parallel work: 3 teams simultaneously

Week 5-14: Core Development

  • Backend APIs (2 developers)
  • Mobile Apps (Flutter)
  • Website (ReactJS)
  • KODA CORE shell (ReactJS)

Parallel work: 5-6 teams/developers

Week 15-20: Integration & Testing

  • Backend final integration
  • App testing & beta
  • Data migration
  • QA intensive testing

Parallel work: All teams coordinating

Week 21-32: Phase 2

  • Backend enhancements (2 developers)
  • Mobile app updates (Flutter)
  • KODA CORE enhancements (ReactJS)

Parallel work: 3 teams

Key Dependencies

Technical Dependencies

  • Mobile apps depend on Backend APIs
  • KODA CORE depends on Backend APIs
  • Phase 2 depends on Phase 1 completion
  • Phase 3 AI depends on Phase 2 data

Resource Dependencies

  • Flutter developer shared between Mobile & Team apps
  • ReactJS team shared between Website & KODA CORE
  • Backend team shared across all modules
  • QA starts heavy testing in Week 15

External Dependencies

  • Cloud infrastructure approval (Week 1)
  • Payment gateway integration approval (Week 4)
  • App Store approval process (Week 18)
  • Google AI Studio API access (Week 33)
  • WhatsApp Business API approval (Week 35)

8. Assumptions & Constraints

Assumptions

Resource Assumptions

  • All team members available as scheduled
  • No key team member turnover during project
  • Team members have required skill levels
  • Part-time DevOps available throughout (6 hours/week)

Technical Assumptions

  • Cloud infrastructure approved and accessible (Week 1)
  • Existing payment gateway compatible
  • Legacy data is accessible and exportable
  • No major API changes from third-party providers

Business Assumptions

  • Phase 1 requirements are stable
  • Stakeholders available for reviews/approvals
  • UAT participants available when needed
  • No major regulatory changes during project

Constraints

Time Constraints

  • Fixed Phase 1 launch: Month 5 (Week 22)
  • Limited design time: 1.5 months (UI/UX)
  • Compressed testing windows
  • Holiday periods may affect availability

Resource Constraints

  • Single Flutter developer for both mobile apps
  • Part-time DevOps engineer (24 hours/month)
  • QA engineer only 3.1 months (later phases)
  • Limited UI/UX time for revisions

Budget Constraints

  • Fixed development budget: 81,555 JOD
  • No budget for additional team members
  • Infrastructure costs managed separately

Quality Constraints

  • Must achieve 99.9% uptime SLA
  • API response time <200ms (p95)
  • Zero critical security vulnerabilities at launch
  • App store rating target >4.5 stars

Approval & Sign-Off

Role Name Signature Date
Project Manager [Name] _________________ ____/____/2025
Technical Lead [Name] _________________ ____/____/2025
Product Owner [Name] _________________ ____/____/2025
Executive Sponsor [Name] _________________ ____/____/2025

Change Control

Once approved, changes to the WBS structure require:

  1. Formal change request
  2. Impact analysis (scope, time, cost)
  3. Change Control Board review
  4. Executive Sponsor approval

Document End

This Work Breakdown Structure (WBS) provides a PM-focused view of the KODA project structure. For technical details, task-level breakdowns, and implementation specifications, refer to the detailed WBS document.