Skip to main content

0001 — Confirm Team Owner sequencing exception ahead of Export

Delivery / Program Management — decision record (ADR-style).

Superseded by export-customer-data/delivery/decisions/0002.

Context​

export-customer-data/delivery/decisions/0001 moved Export Customer Data with Layout to roadmap rank P3 and Team Owner Field & Team Permission to P4 (2026-07-10), giving Export first claim on their shared Ghozi (BE) / Alfi (Mobile) capacity. That ADR's own Consequences section left one question open: "unless Team Owner's hard 2026-08-31 date forces an explicit sequencing exception" — i.e. the rank change was provisional on confirming whether the 08-31 revenue commitment could tolerate queuing behind Export.

commitment_date: 2026-08-31 / commitment_type: revenue was already recorded on the Team Owner initiative README before this decision — that date was never in question. What was open was whether it forces a queuing exception. Sprint 1 (2026-07-07 → 07-21) ran Ghozi, Alfi, and Hendry's queues Team-Owner-ahead-of-Export anyway, pending that confirmation (logged as an unresolved Deviation in cdp/delivery/sprints/2026-07-07-sprint-01.md). Sprint 2's plan (authored 2026-07-16) reverted those three queues back to Export-ahead-of-Team-Owner to match the un-excepted roadmap rank, since the confirmation still hadn't landed.

Decision​

The DRI confirms the 2026-08-31 hard date does force a sequencing exception: Team Owner Field & Team Permission gets first claim on shared Ghozi (BE), Alfi (Mobile), and Hendry (QA) capacity ahead of Export Customer Data with Layout, for as long as Team Owner's build is active.

This is a queuing exception, not a portfolio re-rank — the roadmap ## Priority table keeps Export at P3 and Team Owner at P4 (ADR export-customer-data/decisions/0001 stands unchanged). Only the shared-capacity execution order for Ghozi/Alfi/Hendry flips; Jovi's Export FE work (not shared with Team Owner) and every other queue are unaffected.

Consequences​

  • cdp/delivery/sprints/2026-07-21-sprint-02.md (Sprint 2): Ghozi's, Alfi's, and Hendry's queues run Team Owner ahead of Export again; the sprint's ## Deviations from roadmap priority section is updated to record this as a confirmed, ADR-backed standing exception rather than a pending DRI question.
  • cdp/delivery/sprints/2026-07-07-sprint-01.md (Sprint 1): its queue order (Team-Owner-first for all three) needs no change — it already ran this way. Its Deviations bullet is updated to note the confirmation landed here, retroactively validating that order.
  • No effort, staffing, QA-lane, or roadmap rank fields change as part of this decision. Forecast dates in cdp/delivery/roadmap.md ## Portfolio progress & forecast and the readiness.html schedule model are unaffected — the readiness render already reflects Team-Owner-first execution from how Sprint 1 actually ran (npm run lint:readiness reports no CDP schedule drift on this exception at decision time).
  • This exception persists as long as Team Owner's 08-31 commitment is live; if a future sprint needs a different order, log it fresh rather than assuming this ADR still applies once Team Owner ships or the commitment date changes.