Skip to content

Work Breakdown & Estimate (Iteration 1)

Executive Summary

This WBS outlines the 540-hour (68-day) implementation effort for Iteration 1, mapped directly to the 19 use cases identified in the Use Case Master Index.


Technical Effort Breakdown

Category Component / Use Cases Description Effort (Dev Days)
Mobile (Flutter) Student & Coordinator (STU-001–006, FCM-201) Health logging, video hub, offline sync, profile, notification UI. 22
Admin Console School Admin (ADM-101–106) CMS for videos/curriculum, M&E dashboards, student enrollment, meal/inventory tracking. 15
Backend API Core Logic & WHO Engine (SEC-301, ING-501–502) Auth integration, WHO growth standards logic, data ingestion pipelines. 12
Security & DPDP Compliance Layer (SEC-302) PII anonymization logic, RLS (Row Level Security) implementation. 5
Cloud & DevOps Baseline Infrastructure (PLT-401–402) Provider-agnostic setup, CI/CD, basic scaling (not multi-region DR). 8
QA & Launch Verification Cross-device UAT, bug fixing, app store submission. 6
Total Effort 68 Dev Days (~540 Hours) 68

10-Week Sprint Alignment

Milestone Use Cases Dev Days
Kickoff / Setup SEC-301, SEC-302, ING-501 10
Core Design Lock STU-001, FCM-201 12
MVP Build STU-002, 003, 005, 006, ADM-101 18
M&E / Reporting ADM-102–106, ING-502 20
Final QA & Deploy STU-004, PLT-401, PLT-402 8

Implementation Visualization

gantt title Iteration 1 Development Schedule dateFormat YYYY-MM-DD section Foundation Auth & Compliance (10d) :active, des1, 2026-03-01, 10d section Mobile & CMS Core Student Features (12d) :des2, after des1, 12d Learning & Goals (18d) :des3, after des2, 18d section M&E & Admin Reporting & Aggregator (20d):des4, after des3, 20d section Deployment QA & Store Launch (8d) :des5, after des4, 8d

For the detailed technical execution strategy and rollout plan, refer to the Delivery Roadmap.