Program Control Tower

3 active programs · interactive · click ☐ to close items · auto-refreshes hourly (wire up your refresh task)
—

Next 24h · Key meetings

  • Tue 10:00Mobile App v3 weekly — beta wrap-up + GA readiness gate; bring accessibility audit disposition
  • Wed 11:30Payment Rails migration sync — compliance review scheduling + cutover sequencing
  • Thu 15:00Card Rewards steering — partner API integration sign-off + comms send-date lock

Cross-program clashes · auto-derived

Rails cutover date ↔ app launch sequencing · Mobile App v3 GA gates on Payment Rails cutover being live. Cutover date still unconfirmed — if it slips past month-end, the app launch date moves with it.
Mobile App v3Payment Rails
Resource clash · Eng Lead on two critical paths · Engineering Lead owns both the Rails integration layer and the App v3 backend. Cannot lead both sprint reviews in the same two-week window — one must be delegated.
Mobile App v3Payment Rails

Mobile App Relaunch (v3)

Beta closed Mon · GA readiness review Thu · compliance sign-off pending · You = TPM
Next 3 for you
  1. Consolidate beta exit criteria with Product Lead and QA Lead — accessibility audit findings need disposition before GA gate
  2. Confirm compliance sign-off timeline with Risk Lead — updated disclosures required before store submission; currently on the critical path
  3. Draft store listing copy and get to Marketing Lead by Wed — 3-week App Store review window starts the clock
Decisions on others
  • Risk Lead — Sign off on updated disclosure language in beta build ·2d
  • Exec Sponsor — Approve GA date given compliance dependency on Rails cutover ·1d
  • Design Lead — Resolve 3 open accessibility audit findings from last week's external review ·3d
Open RAID
R
GA date depends on Payment Rails cutover; cutover date still unconfirmed — any slip past month-end pushes the app launch
Risk Lead / Payments Lead ·6d
R
Accessibility audit found 3 AA violations — store rejection risk if unresolved before submission
Design Lead ·3d
I
Beta opt-out rate 12% vs 5% target — root cause traced to notification volume; fix scoped and in next build
Product Lead ·2d
D
Compliance disclosure update requires legal sign-off — blocks store submission; Risk Lead review pushed from last week
Risk Lead ·4d
R Risk · A Assumption · I Issue · D Dependency
What's hot

Beta closed Monday — notification opt-out issue is scoped and in the next build. Compliance disclosure is the real gating item: Risk Lead review was pushed from last week and is now on the critical path into store submission. Rails dependency still floating; if cutover doesn't confirm this week, the GA date needs to move. Accessibility violations need Design Lead to move fast — three AA findings are a store-rejection risk.

Refs (3) · Source: your shared drive

Payment Rails Migration

Parallel run live 8 days · compliance review not yet scheduled · cutover date unconfirmed · You = Program TPM
Next 3 for you
  1. Lock cutover date with Payments Lead and Eng Lead — parallel run is clean; compliance review is the only remaining gate
  2. Get compliance review scheduled with Risk Lead this week — was deprioritized last sprint, now on critical path for both Rails and App v3
  3. Confirm rollback playbook sign-off with Eng Lead before the cutover window opens
Decisions on others
  • Risk Lead — Schedule and complete compliance review; currently blocking cutover date confirmation ·5d
  • Payments Lead — Confirm processor contract SLAs for the post-cutover period ·2d
  • Eng Lead — Sign off on rollback playbook and cutover runbook ·1d
Open RAID
R
Compliance review not yet scheduled — blocks cutover date confirmation for both Rails and App v3 GA
Risk Lead ·5d
A
Parallel run assumed clean after 8 days with no critical failures — formal sign-off pending before cutover proceeds
Payments Lead ·8d
I
3 edge-case transaction types not yet validated in parallel run — low volume but need explicit closure before cutover
Eng Lead ·2d
D
App v3 GA gates on Rails cutover being complete — sequencing must be confirmed this week or app launch date moves
You ·1d
R Risk · A Assumption · I Issue · D Dependency
What's hot

Parallel run is the good news — 8 days, no critical failures. The blocker is compliance review scheduling: Risk Lead deprioritized it last sprint and it's now on the critical path for two programs simultaneously. Edge-case transaction validation is scoped and assigned; should close before the cutover window. Rollback playbook needs one more sign-off pass from Eng Lead.

Refs (3) · Source: your shared drive

Card Rewards Redesign

New structure approved · partner integration in build · comms plan drafted · You = workstream TPM
Next 3 for you
  1. Review partner API integration test results with Eng Lead — first test run completed Fri, 2 issues logged needing partner fixes
  2. Lock cardholder comms send date with Marketing Lead — must go out 14 days before go-live; Marketing approval needed by Thu
  3. Confirm CS training schedule with Ops Lead — training window opens next week; new redemption flow needs coverage before launch
Decisions on others
  • Marketing Lead — Approve cardholder comms draft and confirm send date (14-day pre-launch window) ·2d
  • Ops Lead — Confirm CS team training schedule for new rewards redemption flow ·1d
  • Partner — Resolve 2 open API integration issues from Fri test run; second test run blocked on fixes ·2d
Open RAID
A
Partner API assumed ready for second test run this week — contingent on partner resolving 2 issues from Fri run first
Partner ·2d
D
Cardholder comms must go 14 days before go-live — Marketing approval is on the critical path; deadline is Thu
Marketing Lead ·2d
R
CS team not yet trained on new redemption flow — risk of incorrect handling at go-live if training schedule slips
Ops Lead ·1d
I
Rewards accrual logic update deployed to staging; QA sign-off expected by Wed
Eng Lead ·1d
R Risk · A Assumption · I Issue · D Dependency
What's hot

Mostly on track. Partner API test run Friday surfaced 2 issues — partner has them, fix expected this week. Comms approval is the scheduling risk: 14-day window before go-live means Marketing Lead must approve by Thursday latest. CS training starts next week and is on track. Accrual logic on staging, QA sign-off expected Wednesday.

Refs (3) · Source: your shared drive
Interactive · click ☐ to close items · click "+ note" to add user context · hover any RAID item for source refs
Aging: ·neutral <3d · ·amber 3–7d · ·red 7d+ · R Risk · A Assumption · I Issue · D Dependency