Skip to main content

Centralized SSO Token — Status 2026-07-01

Delivery / Program Management — periodic status report.

Summary​

Still at-risk, but the shape of the risk changed twice today. The 2026-06-30 self-topup reconciliation freed 12.5 md off Syafrizal M.'s forward lane, moving this initiative's projected FE finish from ~W12.2 to ~W9.7 — inside the ~W10.3 finish-by its Lane B QA E2E gate needs to land in Q3 (superseding the 2026-06-30 status report's overflow finding). Later the same day, the EM decided to resequence Syafrizal M.'s queue: Qontak One Team FE (1.5 md) and Sales Invoice + Jurnal FE (2 md) now both run ahead of this initiative, to unblock both of those smaller items rather than leave them stuck behind the 37-day SSO build. That pushes this initiative's FE start back ~3.5 md, moving the projected finish to ~W10.6 — past the ~W10.3 threshold again. Net: the Q3 fit for this initiative's Lane B E2E gate is at risk once more, now driven by an internal queueing decision in addition to the pre-existing external-contract gate.

Lowlights & blockers​

  • 🔴 QA E2E gate at risk of overflowing Q3 again (queue-driven). Lane B (qa_lane: B, no automation substitute). With Qontak One Team FE (1.5) + Sales Invoice + Jurnal FE (2) now ahead of this initiative's FE in Syafrizal M.'s serial queue, the integrated build is projected to complete ~W10.6 (was ~W9.7 before the resequencing), so the 13.5-day E2E would run ~W10.6 → ~W14.0 — roughly a week into Q4.
  • 🔴 FE at exactly 1.00, zero headroom (unchanged). Syafrizal M.'s 37 FE days on this initiative remain the largest single line item in his load (roadmap Capacity summary / Program-level risks). The resequencing did not change his total load — only the order — so the "2nd FE / move SSO FE off Syafrizal M." decision is unchanged as the only lever that recovers this gate's Q3 fit.
  • 🔴 Upstream SDK / Session Manager contracts (unchanged). @mekari/sdk package + CDN (SB-1), Session Manager + Kong /sm/* routing (SB-2), current_company sync endpoint — all owned by SSO/Account (BE); this gate is independent of and additive to the queueing risk above.

Risk & dependency changes​

  • NEW — internal queue resequencing reopens the QA-E2E-vs-window clash. The 2026-06-30 reconciliation had closed the gap identified in the prior status report (~W12.2 → ~W9.7, inside the ~W10.3 finish-by). Today's queue decision (made to unblock Qontak One Team and Sales Invoice + Jurnal) reopens it by pushing the finish to ~W10.6. Recorded here per the delivery doctrine's "persist a notable priority/timeline clash into the dated status report"; mirrored into timeline.md ## Dependencies & gates and the centralized-sso-token README forecast_basis.
  • The underlying trade-off (delay SSO vs. leave Qontak One Team / Sales Invoice + Jurnal unschedulable) was made without a delivery/decisions/ ADR — if the EM wants the rationale formally recorded (e.g. if SSO's Q3 fit becomes unrecoverable and a reprioritization is needed), open one at that point.

Metrics​

  • Progress: 0 / 58.5 man-days (0%)
  • Throughput this period: 0 (pre-execution)
  • Forecast: p50 TBD · p85 TBD — pending the upstream SDK/Session-Manager contracts and the FE-staffing decision. Current sequencing puts QA-complete ~W14.0 (Q4); not Q3-deliverable as staffed, unless a 2nd FE is added or this FE moves off Syafrizal M.

Next period​

  • Resolve the FE assignment (2nd FE or move SSO FE off Syafrizal M.) against the ~W10.3 FE-finish-by date — now the only lever that recovers Q3 fit for the Lane B E2E gate.
  • Chase SSO/Account on the SDK package + Session Manager staging endpoint (unchanged, independent gate).
  • If the FE-staffing decision does not land in time, open a reprioritization ADR accepting the Q4 finish rather than let it slip silently.