Bi-weekly steering committee review covering Sprint 7 of 12. Build and data-migration tracks are on schedule; one amber risk on legacy data integrity is being actively managed ahead of the go-live gate.
The Atlas CRM migration remains on schedule for the August 14 go-live. Sprint 7 closed all committed stories, the production data-migration rehearsal completed its second dry run, and user-acceptance testing began with the sales pilot group. The program is 58% complete and tracking 4 points ahead of the planned burndown.
One amber risk persists: a subset of legacy opportunity records carries inconsistent currency formatting that fails validation on import (RISK-04, detailed in §03). A remediation script is in test and a contingency manual-cleanup path is staffed; neither currently threatens the go-live date. No items are red. The committee is asked to confirm the go-live criteria and approve the cutover-weekend resourcing plan.
(1) Confirm the seven go-live readiness criteria in §02. (2) Approve cutover-weekend on-call resourcing (Aug 14–16). (3) Accept RISK-04 amber rating with the documented remediation plan.
Three of seven criteria are green, two in progress, and two not yet due. The critical path runs through UAT sign-off and defect closure — both inside the current plan window. No criterion is at risk of slipping the go-live gate at this time.
The go-live date is gated by three sequential dependencies: complete RISK-04 data remediation (Jun 06) → full UAT sign-off across all three pilot groups (Jun 26) → rollback rehearsal and cutover-runbook v1.3 (S11). Each predecessor carries float; the binding constraint remains UAT sign-off, which the team protects with the staggered pilot rollout shown above.
Four active risks are tracked. RISK-04 is the single amber item and is detailed below with full ownership, timeline, and escalation path; the remaining three are green and require monitoring only.
Impact: ~6% of opportunity records (≈4,100 of 68,000) fail the currency-validation rule on import. Likelihood: high without remediation. Plan: the cleanup script targets completion by Jun 06 with a reconciliation pass; if it is not validated 100% by Jul 10, the data lead escalates to the steering committee and the staffed manual-cleanup contingency activates. Neither path currently threatens the Aug 14 go-live.
Total tracked risks fell from 8 (S4) to 4 (S7); reds cleared in S5.
Risks are reviewed weekly by the PMO and reported to the steering committee each fortnight. Any item rated red, or amber for two consecutive sprints, is escalated with a recovery plan. RISK-04 is the only item currently outside green and is on its first amber sprint; it returns to green on validated remediation.
Sprint 8 focuses on closing the two open high-severity defects, completing RISK-04 remediation testing, and expanding UAT to the second pilot group. The team enters the sprint with healthy velocity and no blockers.
The program is positioned to hold its Aug 14 go-live. Provided UAT sign-off lands on plan and RISK-04 closes by early June, the remaining readiness criteria fall well inside their windows. Confidence in the date is high.
Distribution: Steering Committee, Sales Operations, IT Leadership. Next report: Sprint 8 close, May 29, 2026. Appendix (defect log, full migration reconciliation, integration uptime) available in the program workspace.