Skip to main content

Legacy Migration CRM Activity Logs → CDP — Status 2026-07-13

Delivery / Program Management — periodic status report. health: carries the delivery-health status (backlog / on-track / at-risk / off-track / paused / completed); the doc-lifecycle status: stays in the linter enum (active).

Summary​

First real BE build progress since the 2026-07-01 baseline: Task 1 (schema additions + source const + Mongo indexes, CALM-S02/S04/S06-NEG) is Done and code-corroborated — two merged PRs in contact-service. The Stage-0 CRM DSN/query-plan gate remains the sole blocker on running the migration; build-ahead continues to proceed against it as planned.

Highlights​

  • TF-3464 ("[BE] Task 1: Schema additions + source const + Mongo indexes", Julio Jeffer Maliangkay) — Done, corroborated via sprint:reconcile's code-evidence join: contact-service PR #855 (0f06b173, "TF-3464-be-task-1-schema-additions-source-const-mongo-inde") and PR #858 (d8fe189f, "TF-3464-fix-duplicate-migration-035-renumber-037"). Task 1's BE slice is 1 of its 1.5-day total (BE 1 / QA 0.5); the QA 0.5 is not separately ticketed and stays uncredited until it joins to a specific QA item.
  • Data-quality note (carried, not new): TF-3459 ("Task 1: Schema additions…", no epic link, Won't Fix/Done) is the pre-existing orphan duplicate of TF-3464 flagged since the 2026-07-09 (pass 1) resync — confirmed not counted toward this progress reading (no code trace, resolved as Won't-Fix, not real work).
  • Sprint 21382 now carries TF-3464 in-scope (it was invisible to the sprint per the 2026-07-09/10 passes); the rest of Jeffer's Tasks 2-9 (TF-3465–3472) are still not sprint-scoped — see the 2026-07-13 (pass 5) sprint-resync recheck on the sprint doc.

Lowlights & blockers​

  • CRM read-only DSN (🔴, run blocker) — owner: CRM Squad + Platform; unchanged.
  • Extraction query plan (🔴, Stage-0 no-go) — owner: CRM DBA; unchanged.
  • Edge confirmations (🟡) — USMAN deactivated-user behavior (OQ-9); Figma badge/status frames (OQ-10); Deal join-model class names + id-sets (OQ-12); unchanged.
  • Sprint-scope gap (🟡, carried, now on its 5th open recheck): Tasks 2-9 (TF-3465–3472, 16 of the remaining 16 BE days) exist as real Jira tickets per the 2026-07-09 pull but are still not in sprint 21382 as of this reading — confirm they still exist under TF-3182 before the next pass treats their absence as resolved-by-removal.

Risk & dependency changes​

No change from 2026-07-01 — the shared-BE-owner risk with Customer Segmentation (P1) remains resolved on capacity/sequencing (Jeffer confirmed at load 0.40). The CRM Stage-0 DSN/query-plan gate remains the sole open blocker against the 2026-08-04 (now reconfirmed 2026-09-07 per roadmap) commitment.

Metrics​

  • Progress: 1 / 24.5 CDP-side known man-days (4%) — DATA Team days still pending, so the true total-effort denominator is not yet final. Only the code-corroborated BE slice of Task 1 is credited; Task 1's QA 0.5 days and TF-3459 (Won't-Fix duplicate) are explicitly excluded.
  • Throughput this period: +1 day (from 0 at 2026-07-01).
  • Forecast: withheld — see Risk & dependency changes above.

Next period​

  • Add Tasks 2-9 (TF-3465–3472) to sprint 21382 if they are meant to be worked this sprint, or confirm they were deliberately deferred.
  • Secure CRM/Platform commitments + dates for the read-only DSN and the extraction query-plan gate.