Skip to main content

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

Jira reconciliation — recheck (2026-07-09)​

First resync of this sprint (no prior recheck section exists). Sprint 21382 ("CDP 26Q3 Sprint 1") holds 50 issues as of this pull. Headline: a large share of the plan's "Ready" work exists as real, correctly-scoped Jira tickets that were never added to the sprint, one undocumented adhoc Epic is consuming sprint capacity, and one engineer (Azani) has zero board presence at all.

New findings from the 2026-07-09 pull:

  1. coverage-gap (sprint-scope drift, the largest single issue): the following planned-Ready work has real, correctly-scoped tickets in Jira that are not in sprint 21382 (confirmed via key in (...) AND sprint = 21382 returning empty for every key below):
    • P2 Customer Segmentation FE (Azani #1, 3d): TF-3399, TF-3400, TF-3401 — exact scope match, unassigned, unsprinted.
    • P3 Team Owner FE (Azani #2, 10d): TF-3312–3316 (+ the TF-3303–3310 web-parity set) — unassigned, unsprinted.
    • P3 Team Owner Mobile (Alfi #2): TF-3271, TF-3272, TF-3273, TF-3279 — correctly assigned to Rizki Alfi Ramdhani, unsprinted.
    • P5 Legacy Migration: CRM Activity Logs BE (Jeffer #2, 17 confirmed days, Tasks 1→9): TF-3464 (Task 1, already In Progress) through TF-3472 (Task 9) — correctly assigned to Julio Jeffer Maliangkay, matching the plan's own task numbering (CALM-S0x). None are sprint-scoped.
    • P7 Create Ticket web track (Jovi #3, Tasks 1-3): TF-3426, TF-3427, TF-3428 — correctly assigned to Giovanni Massimiliano, matching scope. None are sprint-scoped. Net effect: sprint 21382 as filed materially under-represents the plan — only Berlianto's P1/P4 BE work, Ghozi's P3 BE work, Alfi's P1 Mobile work, and Hendry's QA test-writing tasks are actually inside the sprint boundary today.
  2. roster-mismatch (severe): Azani (FE) has zero Jira issues anywhere in project TF right now — not just outside the sprint, unassigned entirely. Her full planned load (Segmentation Task 2.1-2.3 + Team Owner FE chunks, 13 days) has no board representation under her name at all (confirmed by assignee ~ "Azani" returning no CDP-project hits).
  3. off-plan-load: Epic TF-3477 "26Q3 CDP Adhoc" has 5 tasks (TF-3478, TF-3479, TF-3483, TF-3484, TF-3486) sitting inside sprint 21382, consuming real days from Ghozi, Giovanni (Jovi), and Julio Jeffer — none of whom show slack in their plan queues — plus Zhelia Alifa, who is not in the roster at all. This Epic is absent from the sprint doc's Initiative index, the team roadmap Priority table, and the roadmap ## Adhoc / Interrupt lane — and no initiative folder exists for it in the repo. It is currently pure off-plan load with zero Class-of-Service or WIP-limit discipline applied (see CLAUDE.md bucket-initiative doctrine).
  4. Data-quality (orphan duplicate, feeds into finding 1's P5 line): TF-3459 ("Task 1: Schema additions + source const + Mongo indexes (CALM-S02, CALM-S04, CALM-S06-NEG)", no epic link, status Won't Fix/Done) is a near-exact duplicate of the real, active TF-3464 under TF-3182. The duplicate — resolved and epic-less — is the one sitting in sprint 21382; the real in-progress ticket is not. Left as-is, this will misread on any burndown as "P5 Task 1 already handled."
  5. coverage-gap: Export Customer Data with Layout (P6, TF-3181) — Ghozi's planned BE queue item (#2, Tasks 2.1→2.8, 15 confirmed days) has zero tickets under TF-3181 assigned to Ghozi, or to anyone, for the BE half. Only FE (Giovanni) and QA (Hendry) tickets exist under this Epic.
  6. coverage-gap: Customer Event-Based Engine — CEBE (P8, TF-3302) — no ticket exists anywhere for the one task the plan asks of Jeffer this sprint (author the RFC). The 5 existing TF-3302 child Stories (CEBE-CORE-S01-REG, CEBE-MKT-SUP-S01/S02/-NEG) are pre-existing, unassigned PRD Stories, consistent with "no RFC yet" — but the authoring task itself isn't tracked.
  7. status-progress (positive): the P3 (Team Owner Field & Team Permission) task-breakdown the plan's Ghozi brief asked to be generated "early this sprint" has effectively happened — TF-3230 ("Breakdown Task and Generate Plan Task Team Permission", Done, Ghozi) produced 12 granular BE story-tasks (TEAM-S01…S18, TF-3448–3458 + TF-3488) now filed and assigned to Ghozi, alongside a completed FE breakdown (TF-3259, Done, Azani) and Mobile breakdown (TF-3244, Done, Alfi). However, no rfc-team-owner-field-and-team-permission.task-breakdown.md exists in the repo (cdp/team-owner-field-and-team-permission/rfcs/ holds only the RFC + its review) — the breakdown lives in Jira only, not mirrored to the artifact the plan explicitly asked for.
  8. status-progress: TF-3464 (P5 Task 1) is already In Progress per Jira — ahead of the plan's "Ready" framing — but per finding 1/4 it is invisible to the sprint because it isn't sprint-scoped.

This pass does not fix: none of the above tickets have been added to/removed from the sprint, reassigned, or relinked to an Epic — this is an observe-and-record pass. The Azani staffing gap, the TF-3477 adhoc bucket's documentation, and the missing task-breakdown file are PM/TPM/DRI calls per CLAUDE.md doctrine, not something this skill rewrites unilaterally.

Downstream propagation worklist​

#FindingCanonical artifact to reconcileOwning tool / skill
1Sprint-scope drift (5 initiatives' Ready work unsprinted)Add the listed tickets (TF-3399/3400/3401, TF-3312–3316, TF-3271–3273/3279, TF-3464–3472, TF-3426–3428) to sprint 21382 in JiraHand-edit in Jira (board action, not a repo skill) — then re-run sprint-resync to confirm
2Azani zero board presenceAssign TF-3399/3400/3401 (P2) and TF-3312–3316 (P3 FE) to Azani; if she is genuinely unavailable this sprint, flag in this sprint's Deviations section and in capacity.mdHand-edit + sprint-jira-sync (assignment) or a PM/TPM capacity call
3TF-3477 "26Q3 CDP Adhoc" undocumentedDecide: fold into a proper bucket initiative (initiative_type: bucket, README ## Stories tracker, Class of Service, roadmap ## Adhoc / Interrupt lane entry) per CLAUDE.md doctrine, or wind down if one-offPM/TPM decision, then jira-alignment-check / hand-authored bucket README + roadmap edit
4TF-3459 orphan duplicate of TF-3464Confirm TF-3459 stays Won't Fix (no repo artifact — pure Jira hygiene)Hand-edit in Jira (unlink from sprint or leave resolved, no repo action)
5Export Customer Data (P6) BE coverage gapFile Ghozi's Tasks 2.1→2.8 as Jira Tasks under TF-3181, split from the Export task-breakdownsprint-jira-sync (bulk/backfill mode)
6CEBE (P8) RFC-authoring task untrackedFile a lightweight "author CEBE RFC" Task under TF-3302 for Jeffersprint-jira-sync or hand-created in Jira
7P3 task-breakdown not mirrored to repoGenerate cdp/team-owner-field-and-team-permission/rfcs/rfc-team-owner-field-and-team-permission.task-breakdown.md from the now-filed Jira breakdown (BE TEAM-S01…S18 + FE/Mobile chunks)rfc-task-breakdown
8TF-3464 in-progress but unsprintedFeeds cdp/legacy-migration-crm-activity-logs/delivery/status/<date>.md progress_* once P5 build actually starts counting against the sprinthand-edit + lint:delivery once sprinted

Always run npm run lint:delivery (DOCS_ROOT pointed at this repo) after any propagation edit.