Execution Plan
Goal
Ship a production-ready V1 in 14 working weeks (≈ 3.5 months), with V1.1 follow-ons in an additional 6 weeks.
Outcomes by the End of V1
- All three codebases deployed: API (
server/), Web (ui/), Mobile (app/). - 100% of the functional requirements in sections 3.1 – 3.16 live.
- Pest + Vitest + Flutter test suites green in CI.
- One pilot organization with 2 units, 100 employees, on the system for 2 weeks.
- Payroll export endpoint integrated with one partner.
Team Shape
| Role | Count | Responsibility |
|---|---|---|
| Tech Lead (full-stack) | 1 | Architecture, reviews, sprint planning. |
| Backend Engineer (Laravel) | 2 | API, policies, services, Filament. |
| Frontend Engineer (React) | 1 | Web UI. |
| Mobile Engineer (Flutter) | 1 | Mobile app. |
| QA / SDET | 1 | Test plans, automation, pilot support. |
| Product / PM | 0.5 | Requirements, pilot facilitation. |
| DevOps | 0.5 | Docker/Traefik/CI/CD, observability, production hardening. |
Working Agreements
- 2-week sprints, Mondays start.
- Every PR must ship with tests and API docs updates where applicable.
- A feature is "done" when it's merged, documented, tested, deployed to staging, and product has signed off.
Cross-Cutting Rails
Four rails are established in week 1 and enforced from day one:
- Auth + RBAC scaffolding — Sanctum, spatie, scopes, policies stubbed for every resource.
- CI pipeline — lint + typecheck + tests + migrations for each repo.
- Observability — structured logs, request IDs, basic Pulse/Horizon dashboards.
- Audit backbone —
audit_logstable +Auditabletrait used by every domain write.
Everything built afterwards benefits from these rails for free.