Cruits Housing — Release Roadmap¶
GitHub: https://github.com/WAconsult/cruits-housing-ba/blob/main/01-scoping/planning-artifacts/roadmap.md
Draft for sponsor review. Duration estimates based on confirmed team composition and Iteration 1 actuals (2 weeks).
Team¶
| Role | Scope |
|---|---|
| BA | Writes specs one iteration ahead — always preparing the next |
| BE | Housing BE (Django / DRF / Celery / PostgreSQL) |
| FE | Provider Admin + Cruits App UI |
| FS | Flex capacity; focus on integration boundaries (Cruits ↔ Housing BE ↔ GoMeddo) |
| QA | Acceptance + regression within each iteration (shift-left) |
Iterations¶
| # | Iteration | Goal — Definition of Done | Stories | Duration |
|---|---|---|---|---|
| IT-1 | Foundation & Browse | Provider creates listings with pricing; Worker opens Housing section, browses list and detail view | 1.1, 1.2, 1.3, 1.4, 1.6, 1.8, 1.10, 2.2a, 2.4 | 2 weeks |
| IT-2 | Discovery & Reservation | Context handshake from Cruits app; proximity search + filters; Worker creates reservation; hold window enforced automatically | 2.1, 2.2b, 2.3, 1.7, 3.1, 3.2, 3.5 (basic), 3.6 | 3 weeks |
| IT-3 | Full Booking Flow | Complete state machine RESERVED → BOOKED; provider and payer confirmation; pre-BOOKED and BOOKED cancellations; WGV legal compliance | 3.3, 3.4, 3.5 (full), 3.7, 3.8, 3.9, 5.1, 6.1 | 3 weeks |
| IT-4 | Document Signing | DocuSign integration (per-booking and framework modes); signed PDF storage; payment terms configuration | 4.1, 4.2, 4.3, 4.4, 1.9 | 2 weeks |
| IT-5 | GoMeddo Integration | Live inventory sync from Workinn via GoMeddo API; booking flow wired into Cruits App; GDPR consent | 8.1–8.5, 7.1, 7.2, 1.5 | 3 weeks |
| IT-6 | Operations & Settlements | Provider and Payer operational dashboards; settlements view; Ghost Alarm; invoice generation; in-app messaging | 5.2, 5.3, 6.2, 6.3, 6.4, 9.1, 9.2 | 2 weeks |
| IT-7 | Release Hardening | Load testing; security review; production deploy; nice-to-have features (bookmarks, map, house rules) | 2.5, 2.7, 1.11, bugfix | 2 weeks |
Total: 17 weeks
Team Roadmap¶
CRUITS HOUSING — TEAM ROADMAP (17 weeks · 5 people)
══════════════════════════════════════════════════════════════════════════════
│ IT-1 │ IT-2 │ IT-3 │ IT-4 │ IT-5 │ IT-6 │ IT-7 │
TRACK │ Wk 1-2 │ Wk 3-5 │ Wk 6-8 │ Wk 9-10│ Wk 11-13 │Wk14-15 │Wk16-17 │
─────────┼────────┼─────────────┼─────────────┼────────┼──────────┼────────┼────────┤
BA │ ↗IT-2 │ ↗ IT-3 │ ↗ IT-4 │ ↗ IT-5 │ ↗ IT-6 │ ↗IT-7 │ ✓ │
─────────┼────────┼─────────────┼─────────────┼────────┼──────────┼────────┼────────┤
BE │ ██████ │ ███████████ │ ███████████ │ ██████ │ █████████│ ██████ │ ██████ │
FE │ ██████ │ ███████████ │ ███████████ │ ██████ │ ── ─ ─ ─ │ ██████ │ ██████ │
FS │ ██████ │ ███████████ │ ███████████ │ ██████ │ █████████│ ██████ │ ██████ │
QA │ ██████ │ ███████████ │ ███████████ │ ██████ │ █████████│ ██████ │ ██████ │
─────────┼────────┼─────────────┼─────────────┼────────┼──────────┼────────┼────────┤
↑ │ Browse │ Reserve │ Full B/F │DocuSign│ GoMeddo │ Ops │🚀 MVP │
══════════════════════════════════════════════════════════════════════════════
BA ↗ = BA writes specs for the next iteration in parallel with ongoing dev
FE IT-5 = Minimal load; GoMeddo integration is API/BE layer only
FS = Flex resource; reinforces BE or FE wherever the bottleneck is
Key Milestones¶
| Milestone | After | Description |
|---|---|---|
| Browse | IT-1 · Wk 2 | Provider Admin live; Worker can browse all inventory |
| First Booking | IT-2 · Wk 5 | First working end-to-end user journey: Worker reserves a unit |
| Full Flow | IT-3 · Wk 8 | Complete booking state machine; all actors can act on bookings |
| Signed Contracts | IT-4 · Wk 10 | DocuSign flow operational; contracts stored |
| Live Inventory | IT-5 · Wk 13 | Real Workinn inventory via GoMeddo; Cruits app fully integrated |
| Operational | IT-6 · Wk 15 | Provider and Payer have full operational visibility |
| 🚀 MVP Launch | IT-7 · Wk 17 | Production-ready; security and load tested |
Risks & Assumptions¶
| # | Risk | Mitigation | Affects |
|---|---|---|---|
| R-1 | GoMeddo API quality / sandbox delay | Obtain sandbox before IT-5 starts (Wk 11); FS builds mock adapter in IT-1 | IT-5 |
| R-2 | ADR-001 (SSO vs JWT) unresolved | Decision must be made before Wk 3; minimal-effort option preferred | IT-2 |
| R-3 | ADR-002 (Notification provider) unresolved | Decision before Wk 6; Twilio as default candidate | IT-3 |
| R-4 | Booking state machine complexity | Most complex iteration (IT-3); FS allocated fully to BE side | IT-3 |
Low-risk items: - DocuSign (IT-4): Same account already used in Cruits; team has existing integration experience. - FE load in IT-5: GoMeddo integration is API/BE layer; FE capacity available as buffer for IT-4 or IT-6.
Scope Boundaries¶
In MVP (all 7 iterations): - NL market only - Beds and private rooms - English UI - Cruits-placed workers only - Workinn / GoMeddo as launch provider
Post-MVP (not in roadmap): - Listing ratings & reviews (Story 2.6) - Pre-booking inquiry / messaging (Story 2.8) - Standalone housing discovery outside Cruits app - Financial penalties on cancellation - Multi-language UI - Self-registration for any actor type
Generated: 2026-05-31 · Based on PRD v1 and Backlog v1 (9 epics, 40 stories)