Skip to main content

26Q3 Adhoc Requests — Status 2026-07-13

Delivery / Program Management — periodic status report. Records two escalated sprint-resync findings (F-7, F-9) so they get an owner + a decision rather than a fifth re-description.

Escalated risk (sprint-resync F-7 — forecast-at-risk)​

  • 🔴 A2 (BIF-8751, "Listen to Change Owner Webhook") — the sprint's single deterministic firm CLOSE — is still not actionable on the board. Not in sprint 21367, no assignee, To Do. Unchanged across the 2026-07-08, -10, and -13 pulls; now harder because the owner's ranked queue filled this sprint (Lite Seats P7 + Audit Logs P15 tasks filed 2026-07-13).
  • Owner: Satya (Vinsensius Widhismara) + TPM.
  • Decision needed: either assign + pull A2 into the sprint (and clear enough of Satya's queue to make room), or downgrade the "A2 closes firmly" forecast in the sprint plan's Deviations §"26Q3 Adhoc bucket". The firm CLOSE cannot stand while A2 is unowned and out-of-sprint.

Escalated risk (sprint-resync F-9 — bucket-tracker-drift)​

  • 🔴 Epic BIF-8695's in-sprint children do not match the README ## Stories A-id tracker. In-sprint children on 2026-07-13: {BIF-7775, 8236, 8467, 8585, 8593, 8682, 8717, 8784} — only BIF-8682 (A9) is a tracked A-id. The other seven are Epic children absent from the tracker. Verified by hand: lint:delivery (CHECK GROUP J) has no Jira access, so its clean run does not clear this — it only confirms the tracker is well-formed, not that it matches the board.
  • Owner: Addo Hernando (bucket DRI).
  • Decision needed: classify each of the seven untracked children in or out of the bucket. In-bucket → append a tracker row (next A<n>, with its Class of Service) per the bucket-growth procedure; out-of-bucket → confirm they are correctly parented elsewhere. Then re-run npm run lint:delivery CHECK GROUP J.