Skip to main content

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

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​

Still at risk for the web track pending CRM's 2026-07-04 decisions, but no longer fully idle: a web RFC + task breakdown landed (2026-06-30), and Task 1 (permission gate + TicketEmbedPanel scaffold) is unblocked and can ship behind an OFF flag without waiting on CRM. Update, same day: Mobile effort is now confirmed by Alfi at 10 days (12 SP ≈ 2 man-weeks) — and that confirmation is what tips Alfi over capacity across his 4 CDP initiatives (load 1.46, 11 days over). This initiative's Mobile track is technically unblocked but now faces a real capacity constraint, not just a scheduling one.

Highlights​

  • Web RFC + task breakdown added; rfc-reviewer R1: 8.0/10, verdict HOLD (partial-proceed) — Task 1 (FE 1.5 / QA 0.5 = 2.0d) proceeds today; Tasks 2–3 (FE 1.5 / QA 1.0 = 2.5d) blocked.
  • Anchor and both child PRDs remain drafted.
  • Web FE/QA (3 / 1.5) confirmed by Jovi; Mobile confirmed by Alfi at 10 days (was TBD).

Lowlights & blockers​

  • Web Tasks 2–3 remain blocked on AOQ-1 (CRM commits CDP-reusable embed), AOQ-2/OQ-2 (Qontak One iframe auth), and the postMessage contract freeze (OQ-contract) — all CRM-owned, due 2026-07-04.
  • New: Mobile capacity blocker (🔴, internal). Alfi's 3 other CDP mobile assignments (Mention User P1, Team Owner Field P3, Export Customer Data P6) already sum to 25 days against his 24 effective days available — before this initiative's 10 days are even added. There is no room in Q3 for this initiative's Mobile track under the priority + hard-date sequencing policy without deferral or added capacity. Conditional-BE (OQ-6) and Design man-days remain pending.

Risk & dependency changes​

  • Escalated (timeline-mapper, 2026-07-01): confirming this initiative's last unknown Mobile figure converted a "tips Alfi past 1.0" caveat into a firm, 11-day cross-initiative capacity shortfall. Tracked on cdp/delivery/roadmap.md ## Program-level risks and cdp/delivery/capacity.md ## Over/under-commitment. Internally, Jovi can start web Task 1 immediately rather than sit idle while CRM's 07-04 decision is pending — the web track's own sequencing is unaffected by the Mobile capacity issue.

Metrics​

Baseline reading (t0) — 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 still pending.
  • Throughput this period: 0 (baseline).
  • Forecast: TBD (derived once full effort is finalized, CRM's 07-04 decision lands, and Alfi's Mobile capacity conflict is resolved).

Next period​

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