Team Allocation
5 engineers, AI-augmented (2× multiplier in Phases 1–2), delivering ~44 effective man-months over 9 months.
Service Ownership Map
Team Members
Tech Lead / Architect
Architecture decisions, Payment ACL design, code reviews, cross-team coordination, AI governance
Senior Backend Engineer
Travel Booking service lead — extraction, business rules migration, supplier integrations
Mid Backend Engineer
Event Management service lead — extraction, scheduling logic, venue management
Fullstack Engineer
Workforce + Communications services — staff allocation, notification system, React frontend modules
Frontend + DevOps Engineer
Reporting CQRS service, React dashboards, CI/CD pipelines, infrastructure automation
Phase Allocation Matrix
| Engineer | Phase 0 M1 | Phase 1 M2–4 | Phase 2 M5–7 | Phase 3 M8–9 |
|---|---|---|---|---|
| D1 | YARP + IaC setup | Architecture oversight | Cross-service integration | Performance tuning |
| D2 | AI toolchain pilot | Travel Booking (lead) | Travel hardening | DR/failover testing |
| D3 | Legacy analysis | Event Mgmt (lead) | Event hardening | Documentation |
| D4 | CI/CD pipeline | React foundations | Workforce + Comms (lead) | UI polish |
| D5 | Bicep/monitoring | CDC pipeline | Reporting + dashboards | Load/security testing |
AI Productivity Multiplier
Phase 0 uses ×1.0 (toolchain setup). Phases 1–2 use ×2.0 (AI-augmented coding with Cursor Pro, Claude Code, CodeRabbit). Phase 3 reverts to ×1.0 (manual security audits, performance tuning). This gives 5 engineers the effective output of ~10 engineers during peak development.