Skip to main content

Create Ticket & Auto-Associate from CDP (Cross-Platform) — Status 2026-07-12

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​

Unchanged since 2026-07-01: still at risk. The web track's Task 1 (permission gate + TicketEmbedPanel scaffold, FE 1.5 / QA 0.5 = 2.0d) remains unblocked behind an OFF flag; Tasks 2–3 stay blocked on CRM's decisions. The Mobile track's capacity conflict is still open and unresolved — this timeline-mapper pass (squad mode, 2026-07-12) re-confirms it and records the explicit per-initiative verdict below. No progress logged this period.

Highlights​

  • No change to the web track: Task 1 still ready; Tasks 2–3 still blocked on CRM.
  • Squad-mode timeline-mapper (2026-07-12) re-ran CDP capacity from the reconciled delivery digest — Alfi (Mobile) confirmed over by 11 days (load 1.46), unchanged from 2026-07-01.

Lowlights & blockers​

  • Mobile capacity blocker (🔴, internal) — still open, verdict displaced. Create-Ticket Mobile (P7, 10d) is CDP's lowest-priority Mobile lane and loses the sequencing contest to the three lanes ahead of it (P2/P4/P3) — no Q3 room without deferral or added capacity. Unchanged from 2026-07-01, where the full 25-of-24-day derivation lives.
  • Web Tasks 2–3 remain blocked on the CRM-owned embed/auth/postMessage-contract decisions. Conditional-BE (OQ-6) and Design man-days remain pending.

Risk & dependency changes​

  • Re-affirmed, not newly escalated (timeline-mapper 2026-07-12): the 11-day Mobile shortfall first filed on 2026-07-01 is still live and still needs a leadership decision. Tracked on cdp/delivery/roadmap.md ## Program-level risks and cdp/delivery/capacity.md ## Over/under-commitment. The web Task 1 lane is unaffected by the Mobile conflict and can proceed.

Metrics​

Baseline reading — the dated sequence of these reports is the burnup trend.

  • Progress: 0 / TBD man-days (0%) — web FE/QA (4.5) + Mobile (10) = 14.5 known; BE/Design pending.
  • Throughput this period: 0.
  • Forecast: TBD (derived once full effort is finalized, CRM decisions land, and Alfi's Mobile capacity conflict is resolved).

Next period​

  • Start web Task 1 now; track CRM's commitments for Tasks 2–3.
  • Confirm whether CDP backend work is needed after TICKET_CREATED (OQ-6) once Task 2 lands.
  • Decide (still open): defer this initiative's Mobile track to next quarter, or secure Alfi ~10–11 more raw days of CDP-allocated capacity, before scheduling it alongside his other 3 Mobile lanes.