M10-05 End User Beta Programme Execution & Final Acceptance¶

Milestone: M10 — Deployment / Go-Live and Handover SOW Reference: SOW "End User Beta Programme and Final Acceptance" section Requirement Clarity: ✅ Clear Dev Status: ⚪ Not started — depends on the Feature Complete Release existing first

Overview¶

Following delivery of a Feature Complete Release, Curo has a preparation period to complete deployment, beta-user onboarding, and supporting documentation. After that, the End User Beta Programme runs with a limited group of nominated REC member Staffing Companies validating the solution under real conditions.

Tasks¶

Confirm the Feature Complete Release definition and date with Curo
Support the preparation period per SOW terms
Provide reasonable support throughout the Beta Programme
Investigate and rectify any Critical or High-Priority Defects found during Beta

Dependencies¶

Every feature milestone (M2-M9) needs to be substantially complete before the Feature Complete Release can happen.
M10-01 go-live readiness — Final Acceptance timing is directly tied to this.
M10-06 regression testing — runs after each remedial release during Beta.

Acceptance Criteria¶

Successful completion of the preparation period and Beta Programme
Remediation of all agreed Critical and High-Priority Defects (per SOW, "End User Beta Programme and Final Acceptance")

Existing Reference Material¶

SOW, "End User Beta Programme and Final Acceptance" section

Blockers & Risks¶

None beyond the general dependency on prior milestones being complete.