Skip to content

M10-01 Production Deployment / Go-Live Readiness

Milestone: M10 — Deployment / Go-Live for Release v1.0 General Use; Handover / Project Closure SOW Reference: Deliverables D5/D6 Requirement Clarity: ⚠️ Blocking — sequencing ambiguity. Appendix 2 lists M10 as "Deployment / go-live for release v1.0 General Use." But the SOW's own "End User Beta Programme and Final Acceptance" section says Final Acceptance only happens after a further 21-day prep period plus the full 9-week Beta Programme plus regression testing. Get written agreement from Curo on whether "go-live" and "Final Acceptance" refer to the same event or two distinct milestones. Dev Status: ❌ Not started

Overview

Deploy the production/general-availability release (v1.0) and close out the project.

Tasks

  • Resolve the go-live/Final-Acceptance sequencing ambiguity with Curo in writing
  • Confirm production AWS environment (owned/paid for by Curo/JV per Appendix 6, distinct from the dev/UAT environments NeuralRays hosts)
  • Execute production deployment
  • Confirm go-live checklist against Appendix 3's Final Acceptance criteria

Dependencies

  • Every prior milestone (M1-M9) reaching acceptance.
  • M10-05 Beta Programme — Final Acceptance formally depends on this completing.

Acceptance Criteria

  • Successful completion of the (up to) 21-day prep period and 9-week Beta Programme
  • Remediation of all agreed Critical/High-Priority defects
  • Successful completion of all agreed regression testing
  • Written confirmation by Curo that Acceptance Criteria have been satisfied (per SOW, "End User Beta Programme and Final Acceptance")

Existing Reference Material

  • SOW §8, Appendix 2 (Milestones table), "End User Beta Programme and Final Acceptance" section

Blockers & Risks

  • Blocking: the go-live-vs-Final-Acceptance sequencing ambiguity needs a clear, written definition from Curo before this milestone can be assessed as complete.