Skip to main content

CDP Sprint 1 (2026-Q3) — Jira reconciliation, pass 2 (2026-07-09)

Jira reconciliation — recheck (2026-07-09, pass 2)​

Second pass the same day, triggered by a roadmap reprioritization rather than sprint elapsed time. Sprint 21382 still holds 50 issues — no board composition change since the prior pull.

Status of the 2026-07-09 (pass 1) findings:

  1. coverage-gap (sprint-scope drift) — STILL OPEN: re-checked every listed key (TF-3399/3400/3401, TF-3312–3316, TF-3271/3272/3273/3279, TF-3426/3427/3428) by key in (…) — all still exist, correctly scoped to their Epics, still absent from sprint 21382.
  2. roster-mismatch (Azani zero board presence) — STILL OPEN: project = TF AND assignee ~ "Azani" returns zero issues project-wide, unchanged.
  3. off-plan-load (TF-3477 "26Q3 CDP Adhoc") — STILL OPEN, unchanged: same 5 tasks (TF-3478, TF-3479, TF-3483, TF-3484, TF-3486) still in-sprint, still undocumented in the repo.
  4. Data-quality (TF-3459 duplicate of TF-3464) — STILL OPEN: TF-3459 confirmed still Won't Fix/Done, epic-less; TF-3464 confirmed still In Progress under Julio Jeffer Maliangkay, still unsprinted.
  5. coverage-gap (Export Customer Data P6 BE) — STILL OPEN: TF-3181 in this sprint still has only FE (Giovanni) and QA (Hendry) tickets, zero BE.
  6. coverage-gap (CEBE P8 RFC-authoring task) — STILL OPEN: no TF-3302 issue of any kind in sprint 21382.
  7. status-progress (P3 task-breakdown not mirrored to repo) — STILL OPEN: cdp/team-owner-field-and-team-permission/rfcs/ still holds only the RFC + its review, no *.task-breakdown.md.
  8. status-progress (TF-3464 in-progress but unsprinted) — STILL OPEN, reconfirmed above.

New finding from this pass (repo-side, not a Jira pull):

  1. SPRINT_PRIORITY_DRIFT (per lint-delivery.mjs): the CDP roadmap ## Priority table was reprioritized on 2026-07-07 — Customer Segmentation → P1, Mention User in CDP Notes → P2 (previously the reverse) — per decisions/0001-reprioritize-segmentation-ahead-of-mention-user.md, itself decided during this same sprint's planning. This sprint doc's sprint_goal, ## Initiative index, and every per-engineer queue still carried the pre-reorder ranks despite opening the same day the decision was made. Fixed in this pass: every P1/P2 label relabeled to match the roadmap, and Hendry's QA queue reordered (Customer Segmentation now precedes Mention User in CDP Notes) — the only queue where both initiatives co-occur. No other engineer's queue order changed: Berlianto/Jovi/Alfi work only Mention User, Julio Jeffer/Azani work only Customer Segmentation among these two. initiative-timeline-mapper (2026-07-09) already established the reorder carries no forecast/capacity impact — Hendry sits at load 0.60, and the two initiatives share no BE/FE/Mobile staff.

This pass does not fix: none of the 8 carried-forward Jira findings (sprint-scope drift, the Azani staffing gap, the TF-3477 adhoc bucket, the TF-3459 duplicate, the two coverage gaps, the missing task-breakdown file, or the unsprinted in-progress ticket) — those still need the PM/TPM/DRI calls and Jira edits from the pass-1 worklist above, unchanged by this pass. This pass touched only this sprint doc's own priority labels/ordering; no Jira write was made.