Legacy Migration CRM Activity Logs → CDP — Status 2026-07-01
Delivery / Program Management — periodic status report.
health:carries the delivery-health status (backlog / on-track / at-risk / off-track / paused / completed); the doc-lifecyclestatus:stays in the linter enum (active).
Summary
Still at risk against the 2026-08-04 revenue commitment, now on two fronts: the CRM/Platform Stage-0 access gates from the prior report remain open, and the initiative's effort is now fully sized (24.5 CDP-side man-days) against a BE owner — Jeffer (Julio Jeffer) — who is also the sole BE for Customer Segmentation (P2, hard date 2026-07-21). Per the roadmap sequencing policy his queue must serve P2 first, but P2's BE effort is completely unsized, so P5's schedulability against 08-04 cannot yet be confirmed.
Highlights
- Task breakdown expanded from 7 to 9 chunks (2026-07-01): added
SyncWatermarkResolver(Task 8, low-risk) andAssociationLogEnricher(Task 9, highest-risk new task — depends on OQ-13 match-key collision-safety, unit-testable against fixtures today). - Effort is now breakdown-sourced: BE 17 / FE 1 / QA 6.5 = 24.5 days (medium confidence), pending
formal Jeffer/DRI sign-off. DATA Team's own days remain
TBD. - All 9 chunks remain writable and unit-testable now; the migration run is still what's gated.
Lowlights & blockers
- CRM read-only DSN (🔴, run blocker) — owner: CRM Squad + Platform; unchanged from 2026-06-30.
- Extraction query plan (🔴, Stage-0 no-go) — owner: CRM DBA; unchanged from 2026-06-30.
- Edge confirmations (🟡) — USMAN deactivated-user behavior (OQ-9); Figma badge/status frames (OQ-10); Deal join-model class names + id-sets (OQ-12); unchanged from 2026-06-30.
- New: shared BE owner unresolved (🟡, internal) — Jeffer (Julio Jeffer) is also Customer Segmentation's sole BE; P2's BE effort is unsized, so his P2→P5 queue cannot be verified against 08-04. Owner: DRI / Julio Jeffer; ask: size Customer Segmentation BE this week.
- New: review coverage gap (🟡) — the RFC review (R2, 2026-06-18) predates the 9-chunk
expansion (
last_updated: 2026-06-30); Task 9 in particular is unreviewed net-new scope.
Risk & dependency changes
- Escalated (timeline-mapper, 2026-07-01): the shared-BE-owner conflict between P2 and P5 is
structurally the same failure mode already recorded for P4 (a hard date put at risk by a
resource/dependency clash) — tracked here and on
cdp/delivery/roadmap.md## Program-level risks. No date has been missed yet; this is a scheduling risk, not a confirmed slip. - Update, same day: Julio Jeffer confirmed both BE figures directly — Customer Segmentation
(P2) at 4 days (0 done in Q2 + 4 buffer bugfixing) and this initiative's BE at 17 days (matching
the task-breakdown). Combined 21 days against his 52 effective days (
load 0.40) — the shared-BE-owner risk above is resolved on capacity/sequencing; P2's small remaining scope clears well ahead of P5 in his queue. The CRM Stage-0 DSN/query-plan gate remains the sole open blocker against 08-04.
Metrics
Baseline reading (t0) — the dated sequence of these reports is the burnup trend.
- Progress: 0 / 24.5 CDP-side man-days (0%) — DATA Team days still pending, so the true total effort denominator is not yet final.
- Throughput this period: 0 (baseline).
- Forecast: withheld — see Risk & dependency changes above.
Next period
Size Customer Segmentation's BE effort so Jeffer's P2→P5 queue can be tested against 08-04.Done same day — Jeffer-confirmed at 4 days; sequencing clears.- Secure CRM/Platform commitments + dates for the read-only DSN and the extraction query-plan gate.
- Consider an R3 delta review of the RFC covering Tasks 8-9 before treating them as PROCEED.