Skip to main content

CDP H2 2026 Roadmap

Delivery / Program Management — team-level rollup across the team's initiatives.

Rolling roadmap — updated as initiative timelines are confirmed.

Portfolio

InitiativeTarget quarterHealthDRIImplementorsQATimeline
Mention User in CDP Notes2026-Q3At RiskZhelia AlifaBerlianto, Jovi, AlfiHendry (primary), Izzul (backup)timeline
Customer Segmentation2026-Q3At RiskZhelia AlifaJulio Jeffer, Azani, DATA Team (ext)Hendry (primary), Izzul (backup)timeline
Team Owner Field & Team Permission2026-Q3At RiskZhelia AlifaGhozi, Azani, AlfiHendry (primary), Izzul (backup)timeline
Legacy Migration: CRM Notes → CDP2026-Q3At RiskZhelia AlifaBerlianto, DATA Team (ext)Hendry (primary), Izzul (backup)timeline
Legacy Migration: CRM Activity Logs → CDP2026-Q3At RiskZhelia AlifaJeffer, DATA Team (ext), TBD (FE)Hendry (primary), Izzul (backup)timeline
Export Customer Data with Layout2026-Q3BacklogZhelia AlifaGhozi, Jovi, AlfiHendry (primary), Izzul (backup)timeline
Create Ticket & Auto-Associate from CDP (Cross-Platform)2026-Q3At RiskZhelia AlifaJovi, Alfi, TBD (BE, conditional)Hendry (primary), Izzul (backup)timeline
Customer Event-Based Engine (CEBE)2026-Q3BacklogZhelia AlifaJulio Jeffer (BE), DATA Team (ext), TBD (Infra)Hendry (primary), Izzul (backup)timeline
Multi-BSUIDs (CDP × CRM)2026-Q2TBDTBD (Backend)Hendry (primary), Izzul (backup)
PII Encryption — Contact Service2026-Q3Puji Triwibowoberlianto
CDP Contact EnrichmentTBDBacklogZhelia AlifaTBDtimeline
Customer Health ScoreTBDBacklogZhelia AlifaTBD
CDP 26Q3 Engineering Initiatives (bucket)2026-Q3BacklogGhozi, Julio Jeffer, BerliantoGhozi, Julio Jeffer, Berlianto, Jovi, AzaniHendryREADME
26Q3 CDP Adhoc (bucket)2026-Q3On TrackZhelia AlifaGhozi, Julio Jeffer, Jovi, Zhelia Alifa (flagged, A1), Azani, AlfiHendryREADME

Multi-BSUIDs (CDP × CRM) is listed for completeness but its target_quarter: 2026-Q2 is now past and it has no delivery/timeline.md — DRI/PM to decide whether it shipped, slipped to Q3, or closed, then set its health, DRI and timeline (or drop the row if closed). It is intentionally left ranked last (P9) on the Priority table below pending that decision.

Priority

PriorityInitiativeDepends onNote
P1Customer SegmentationCommitment 2026-07-28 (revenue) — scoped in initiative folder; FE/QA sized (4.5), BE effort still TBD
P2Mention User in CDP NotesNotes feature readiness — commitment 2026-08-14 (revenue)
P3Export Customer Data with LayoutFully sized (32.5 md), core unblocked; precedes P4 — decision 0002
P4Team Owner Field & Team Permission08-31 revenue commitment; follows P3 on shared capacity — decision 0002
P5Legacy Migration: CRM Notes → CDPP2 — Mention User in CDP NotesCommitment 2026-09-07 (revenue) — blocked until P2 ships
P6Legacy Migration: CRM Activity Logs → CDPCommitment 2026-09-07 (revenue)
P7Create Ticket & Auto-Associate from CDP (Cross-Platform)
P8Customer Event-Based Engine (CEBE)
P9Multi-BSUIDs (CDP × CRM)⚠️ Past-quarter (2026-Q2), no timeline — pending shipped/slipped/closed decision; drop or re-rank once decided
P10PII Encryption — Contact ServiceRanked last pending a PM priority call; effort sized (BE 10 / QA 3.25 = 13.25), not yet sequenced
P11CDP Contact EnrichmentRanked last pending a PM priority call; target_quarter: TBD (not agreed for 26Q3); effort TBD, Legal (OQ-P1) + BI datamart (OQ-BI) blockers open
P12Customer Health ScoreRanked last pending a PM priority call; target_quarter: TBD (not agreed for 26Q3); status draft, effort unsized, no RFC

Adhoc / Interrupt lane

Bucket (Epic)🔴 Expedite (may preempt)📅 Fixed-Date🟡 Standard (pull-in fill)⚪ IntangibleTracker
CDP 26Q3 Engineering Initiatives (TF-3500)A2, A5, A6, A7, A8A1, A4, A9A3tracker
26Q3 CDP Adhoc (TF-3477)A2, A6A3, A4, A5A1tracker

Per-story class/status and growth are canonical in the bucket tracker; A7 🔴 in flight since 2026-07-21 (Expedite log).

26Q3 CDP Adhoc (TF-3477) stood up 2026-07-14, backfilled from in-flight work; per-story class/status canonical in its tracker. expedite_wip_limit not yet set — PM/TPM to choose CDP's cap.

Sequencing policy

Planning rule for 2026-Q3 delivery:

  1. Sequence development and delivery by priority order, hard commitment dates, and dependencies. A lower-priority initiative may move earlier only when a hard date or dependency requires it, or when doing so does not delay higher-priority / deadline-bound work.
  2. When an engineer is assigned to multiple initiatives, their work queue follows the same rule: priority + hard date + dependency order first.
  3. Engineers should not be idle. If their current top-priority work is blocked or waiting on another role, they should pull the next eligible initiative that does not delay rule 1.
  4. CDP QA defaults to Hendry. Izzul is a backup only when Hendry's timeline clashes or the team needs extra QA support; do not pre-allocate Izzul to CDP unless that clash exists.

Implications from the current staffing:

  • Mention User in CDP Notes (P2) gets first claim on Berlianto, Jovi, and QA capacity.
  • Legacy Migration: CRM Notes → CDP (P5) cannot start until P2 ships; against its 2026-09-07 revenue commitment the P2 dependency (P2 finishes p85 ~2026-08-19) leaves ~2.5 weeks of runway, so the dependency no longer forces a date miss (the net-new Legacy CRM extraction endpoint is now the binding blocker — see Program-level risks).
  • Export Customer Data with Layout (P3) gets first shared-capacity claim over Team Owner (P4) — decision 0002.
  • Team Owner Field & Team Permission (P4) follows P3; 08-31 remains at risk on Launchpad/Mobile gates.
  • Customer Segmentation (P1), Team Owner Field & Team Permission (P4), and both migrations (P5/P6) still need effort inputs before the policy can produce dated portfolio forecasts.
  • QA capacity is assigned to Hendry first; Izzul remains an escalation/backup lane because his capacity is distributed across multiple teams.
  • Azani (FE) queue reordered to policy (Segmentation P1 FE before Team Owner P4 FE) in the 2026-07-01 render — still needs DRI confirmation it matches Azani's real queue, and may push Alfi's Team Owner Mobile start later (see Mobile over-commitment risk). Full analysis: customer-segmentation status 2026-07-01.

Portfolio progress & forecast

Initiative% doneEffort (total man-days)p85 forecastConfidence
Mention User in CDP Notes51%342026-08-19medium
Customer Segmentation47%TBD (BE 4, FE 3, QA 1.5 = 8.5; Data/Design pending)medium
Team Owner Field & Team Permission0%TBD (BE 10, FE 10, Mobile 10, QA 7.5 = 37.5; Design pending)medium
Legacy Migration: CRM Notes → CDP0%
Legacy Migration: CRM Activity Logs → CDP8%TBD (BE 17, FE 1, QA 6.5 = 24.5 CDP-side; DATA Team pending)withheld — CRM Stage-0 DSN/query-plan gatemedium
Export Customer Data with Layout35%32.52026-09-19medium
Create Ticket & Auto-Associate from CDP (Cross-Platform)0%TBD (FE 3, Mobile 10, QA 1.5 = 14.5 known; BE/Design pending)medium
Customer Event-Based Engine (CEBE)0%TBD (BE 15 = 15 known so far; Data/Infra pending)
CDP 26Q3 Engineering Initiatives8% (1 of 12 items done)— (unsized bucket — the per-story tracker in the initiative README is canonical; % done here is the done ÷ total rollup of that tracker's Status column, and grows as items are added)
26Q3 CDP Adhoc33% (2 of 6 items done)— (unsized bucket — the per-story tracker in the initiative README is canonical; % done here is the done ÷ total rollup of that tracker's Status column, and grows as items are added)

Per-initiative effort/forecast confirmations and their derivations are canonical in each initiative's delivery/timeline.md + latest dated status/ (and mirrored on each README); the table above carries the current figures. TBD totals await the remaining per-discipline man-days.

QA Lanes

InitiativeLaneBasisAs of
Mention User in CDP NotesBout-of-reach: Mobile; notification delivery needs manual verification2026-06-29
Customer SegmentationCtransition: CRUD automatable; data-ingestion checks keep a manual gate2026-06-29
Team Owner Field & Team PermissionBsecurity/isolation + migration before/after crosscheck2026-06-29
Legacy Migration: CRM Notes → CDPBmigration: before/after data crosscheck needs manual QA2026-06-29
Legacy Migration: CRM Activity Logs → CDPBmigration: before/after data crosscheck needs manual QA2026-06-29
Export Customer Data with LayoutBout-of-reach: Mobile; email crosschecking/operations2026-06-29
Create Ticket & Auto-Associate from CDP (Cross-Platform)Ctransition: strongest Lane-A candidate; cross-platform incl. Mobile, awaiting E2E2026-06-29
Customer Event-Based Engine (CEBE)BQ3 scope is research/assessment/analysis; real-time downstream2026-06-29
Multi-BSUIDs (CDP × CRM)Bsecurity/isolation: multi-org BSUID scoping2026-06-29
PII Encryption — Contact ServiceBsecurity/isolation: AES-256-GCM PII field-level encryption, Infosec sign-off required2026-07-09
CDP Contact EnrichmentBmoney-critical: token check/deduct/refund via Qontak Billing quota; no test spec yet2026-07-09
Customer Health ScoreBno RFC/test spec yet — entry bar unmet (0% E2E); revisit once scoped2026-07-09
CDP 26Q3 Engineering InitiativesBteam-policy default — engineering items (server/infra migration, EOL upgrades, perf) can carry data-integrity/availability risk reaching paying customers; re-confirm per-story (a pure test-coverage push may warrant a lighter gate)2026-07-10
26Q3 CDP AdhocBmoney-critical: covers a P0 duplicate billing deduction/refund incident fix (A2) — a silent regression reaches paying customers' invoices directly2026-07-14

Lane A: 0 of 14 · Lane C: 2 of 14 · Lane B: 12 of 14 (target 20–50% in Lane A). Lane C (Customer Segmentation, Create Ticket) is the transition lane — QA initiates the full E2E suite and Eng contributes; each graduates to Lane A once the entry bar (100% E2E, spec-mapped) is met. Create Ticket is the strongest Lane-A candidate.

Note: Multi-BSUIDs (CDP × CRM) is now on the Portfolio and Priority (P9) tables above, flagged for a shipped/slipped/closed decision.

Capacity summary

See capacity.md for the full per-implementor table and all load derivations.

  • Binding constraint: Mobile (Alfi) over by 11 days (load 1.46) across 4 initiatives — Create-Ticket (P7) Mobile has no Q3 room; PM/TPM defer-or-expand decision open (Program-level risks below · capacity.md).
  • All other implementors are under capacity: Jeffer 36 d / 0.69, Ghozi 25 d / 0.48, Berlianto 23.5 d / 0.45, Hendry 31 d / 0.60, Jovi 20 d / 0.38, Azani 13 d / 0.25.
  • Data is an external squad (DATA Team), not CDP capacity; CEBE's Infra track is unstaffed.
  • Committed days stay TBD for initiatives whose DRIs haven't confirmed per-discipline man-days.

Cross-initiative dependencies

  • Legacy Migration: CRM Notes → CDP (P5) is blocked by Mention User in CDP Notes (P2) — the migration can only run after the mention feature ships so migrated historical notes render mentions consistently with notes authored post-feature. Tracked in legacy-migration-crm-notes/README.md frontmatter depends_on: [notes-mention-user].

External & cross-squad dependencies

InitiativeBlocking dependencyOwner (squad / vendor)Status
Team Owner Field & Team PermissionTeams-for-user(+descendants) API to the §2.4 contract + team radio in permission UI (CHG-001) + legacy→Launchpad team-name crosswalk; must land before flag-ON GALaunchpad (radio ownership ⚠️ Launchpad vs Admin Portal — confirm)🔴 in-repo chunks build now; all gate GA
Team Owner Field & Team PermissionCDP Mobile module renders Team Owner field + per-note permission flagsMobile Squad🔴
CDP 26Q3 Engineering InitiativesTeam Owner backfill (A9) needs CRM's own Team data migrated into USMAN first — no committed date; tracked as its own bucket item, not inside Team Owner's 08-31 commitmentCRM Squad / Platform-USMAN🔴 no date yet
Legacy Migration: CRM Notes → CDPNet-new org-scoped Person-notes extraction endpoint (does NOT exist today; Decision 10 / OQ-7)Legacy CRM Squad🔴 hard prerequisite for any run
Legacy Migration: CRM Notes → CDPPer-CID coverage ≥99% (OQ-2); bulk-throughput load test (OQ-7); bluemonday/Infosec (OQ-10); CRM bucket access + PII residency (OQ-9); per-caller audit (OQ-11); CSM per-CID consentData Eng / Infosec / CDP Infra / Legacy CRM / Platform / CSM🟡
Legacy Migration: CRM Activity Logs → CDPRead-only Postgres DSN scoped to audits+users (Gate A/OQ-1) + EXPLAIN-ANALYZE query plan & index (Gate B/OQ-2) — Stage-0 no-go until both passCRM Squad + Platform / CRM DBA🔴
Legacy Migration: CRM Activity Logs → CDPUSMAN deactivated-user behavior (OQ-9); Figma badge/status frames (OQ-10); Deal join-model class names + won/done/resolved id-sets (OQ-12)Platform/USMAN / Design / CRM🟡
Export Customer Data with LayoutNo CDP "Customer Data" quota type + no s2s export-history register path today (OQ-17); gates EXP-S08 only (a Should-Have) — core pipeline unblockedBilling/IAG + Chat/Omnichannel🔴
Export Customer Data with LayoutNotification ingest channel REST vs Kafka (OQ-10); OSS quota headroom (OQ-4); optional mobile tap-through routing (OQ-12)One Notification / Alibaba OSS / Mobile🟡
Mention User in CDP NotesWeb Figma frames for the mention typeahead picker + chip (OQ-14) — only build blocker; gates web composer/chip (§4.D chunk 7)Design System🔴
Mention User in CDP NotesInfosec approval of bluemonday allow-list + lock-screen PII egress (OQ-19/REV-14); notification category choice — reuse mention(2) vs CDP-specific (OQ-1)Infosec / Notification Platform🟡
Multi-BSUIDs (CDP × CRM)crm_phones.bsuid column + immutability guard (TF-3154) + CRM-first deploy order (TF-3154 → TF-3156 → TF-3155 → flag)CRM (⚠️ TF is CDP's Jira project but RFC names CRM as owner — confirm)🔴

No timeline yet: Multi-BSUIDs (CDP × CRM) has no delivery/timeline.md. It is now on the Portfolio table above but still off the Priority table (its target_quarter: 2026-Q2 is now past) — scaffold a timeline + decide whether it shipped, slipped to Q3, or closed.

Program-level risks

  • Mention User (P2) — tight vs 2026-08-14: forecast p50 08-10 / p85 08-19 (fits at p50, misses p85 ~5 d); pure BE→FE→QA critical-path length, no blocking dependency. status.
  • Mobile (Alfi) over by 11 days (load 1.46) across 4 initiatives — Create-Ticket (P7) Mobile has no Q3 room; decision needed: defer to next quarter or add ~10–11 raw days. capacity.md.
  • QA (Hendry) late-quarter E2E collision — three Lane-B final-E2E gates (Team Owner 7.5d, both migrations 6.5+4.5d) stack ~18.5 QA-days into the ~13-working-day 08-20→09-07 window on one serial owner; his 0.60 quarter load hides it. Decision needed: authorise Izzul for the window, else the 09-07 gates miss on QA. capacity.md.
  • Export Customer Data (P3) — fully sized (32.5 md), core-unblocked, ahead of Team Owner on shared capacity — decision 0002.
  • Team Owner Field & Team Permission (P4) — at risk vs 2026-08-31: in-repo chunks build now, flag-ON GA gated on Launchpad (teams-for-user endpoint + Team Only radio, not yet committed). status.
  • Legacy Migration: CRM Notes → CDP (P5) — at risk vs 2026-09-07: binding blocker is the Legacy CRM Squad's net-new extraction endpoint (🔴, no upstream date), not the P2 dependency (now clears ~2.5 wks inside 09-07); watch P2 doesn't slip past mid-Aug. status.
  • Legacy Migration: CRM Activity Logs → CDP (P6) — at risk vs 2026-09-07: sole blocker is the CRM-owned Stage-0 DSN/query-plan go/no-go; build sized at 17 BE days (Jeffer-confirmed), Jeffer load clears. status.
  • Customer Segmentation (P1) — at risk vs 2026-07-28: Basic Attributes in progress, BE Jeffer-confirmed (4 d), Data/Design unscoped; Azani FE queue reorder needs DRI confirmation (see Sequencing policy). status.
  • Create Ticket & Auto-Associate (P7) — at risk on two fronts: web Tasks 2-3 gated on overdue 2026-07-04 CRM decisions; Mobile (10 d, Alfi-confirmed) tips Alfi over capacity (see Mobile risk). status.