Integration Project – UET & Go-Live Countdown Notes

Pre-Meeting Banter / Ice-Breakers

Participants exchange lighthearted movie references to loosen the mood:
- “Sausage King of Chicago” (Ferris Bueller’s Day Off) and “Beautiful Mind” cameo cut-scenes.
- Story of a father appearing in the “pie scene” of Revenge of the Nerds.
- Running joke: being “famous-adjacent” rather than actually famous.
Purpose of banter: build rapport and ease into a fast-paced, high-pressure status call.

Paul — senior stakeholder; offers sign-off authority, monitors risk.
Peter — counterpart to Paul; helps monitor progress.
Crystal — product/implementation owner; confirms requirements, agrees risk status.
Jeremy — lead on development side; responsible for integration tasks & dev portal research.
Brian — from Crystal’s team; confirmed requirements, timelines.
Dan — note-taking, email follow-ups; will be PTO on certain dates.
Stefan — external consultant (October for Buildings); prior experience with same integration.
Unnamed Speaker/Facilitator (likely Ryan) — runs the call, sets deadlines, risk status, & next steps.

Morning call (same day) with Jeremy, Crystal & Brian established:
- All functional & technical requirements are now confirmed/locked.
- Team can immediately begin full integration + full development.
- Brian re-confirmed stars/moon “green-lighting” 01 Aug target for UET.
Result: No dependency gaps voiced; dev team has what they need to start coding.

Previous status: Green (on-track, low risk).
New status: Amber (heightened risk) due to:
- Extremely compressed timeline (≈20 business days; holidays & weekends removed).
- Need for parallel execution of dev + QA.
Rationale explained transparently to all stakeholders to reset expectations.

08/01 — Begin UET / UUT (User or Business Unit End-to-End Testing).
08/29 — Latest date for UET sign-off; all integration + dev must be finished before this.
09/15 — Soft Launch / production URLs handed over (could advance if zero custom code).
09/30 — Go-Live (±1 day depending on final test volume).
Total effective dev window ≈ 20\;\text{working days}.

Development & Integration Window
- Starts now → 07/31 (just before UET).
- Includes: API wiring, SSO config, object-ID provisioning, sandbox validation.
User End Testing (UET)
- 08/01–08/29 window. Business testers exercise full workflows.
- Objective: certify that solution meets functional, non-functional & compliance criteria.
Soft Launch / Prod URL Activation
- 09/15 target; earlier if environment remains “standard” (no special customizations).
- Gives the business two weeks to operate in “prod-to-prod” connection before public Go-Live.
Final Go-Live
- 09/30. Cut-over, client-facing operations begin.

Single-Sign-On (SSO) Object IDs
- Only current cost item for DCUB/UES group.
- Required to bridge into Agent Dashboard within Seminal integration.
Dev Portal Research (Jeremy)
- Explore developer portal resources for SDKs, sample code, & prior integrations.
- Leverage Stefan’s historical implementation knowledge.
Contact Coordination
- DC team points of contact to be shared so Jeremy can escalate quickly.
Credit-Card Test Data
- Facilitator’s personal card remains in sandbox; reiterated privacy concern about saying that “out loud.”

Next status call: Next week (exact date TBD) — checkpoint on build progress.
Week of the 16th
- Facilitator OOO (PTO in Florida) on the 16th.
- Paul & Peter will act as “eyes and ears” & own note-taking for that call.
Ownership of DC-hosted calls: DC team will continue to own/web-host; no duplication needed.
Facilitator commits to monitor email & jump in remotely if urgent (Wi-Fi on vacation & spouse’s birthday permitting).

Timeline Compression
- 20-day dev sprint + 29-day UET is aggressive; hence Amber.
- Team willing to work holidays if needed (humorous ask for “coffee & donuts”).
Resource Availability
- Facilitator OOO two separate weeks, but coverage plans in place.
Dependency on Standard Build
- Any late customization could jeopardize early prod URL release → soft launch date slips.
PTO / Personal Constraints
- Facilitator jokes re: sleeping in the dog shack if he works on spouse’s birthday (human factor acknowledged).

[Jeremy] Gather SSO object-ID requirements; poll dev portal; reach out to Stefan — ASAP.
[Paul & Peter] Cover eyes/ears on next DC call; take + circulate minutes — Next Week.
[Facilitator (Ryan?)] Provide follow-up email confirmation before leaving for PTO — Before 16th.
[Dan] Review & respond to facilitator’s email — Immediate.
[Entire Team] Prepare status update for next week’s checkpoint; flag impediments early.

The project is entering its most critical phase; timelines are now the primary risk driver.
Status was deliberately downgraded to convey urgency and pre-empt complacency.
Cross-functional coordination (DC, JP Morgan, external consultant) is vital; communication channels are established.
Personal PTO acknowledged openly to maintain transparency and proper coverage.