The Scenario
A South African retail chain is rolling out a new ERP system across 5 branches over 10 months. Each branch has different product mixes, staff sizes, and legacy systems. The CTO wants a UAT strategy that ensures each branch is tested without delaying the next.
The Brief
Design the complete UAT strategy covering regression testing, data migration validation, branch-specific testing, and go/no-go criteria.
Deliverables
- A UAT strategy document: scope per phase, test types (functional, regression, data migration, integration)
- A regression testing approach: what to re-test when Branch 3 goes live and Branches 1-2 are already in production
- Data migration validation: how to verify that each branch's historical data migrated correctly
- Go/no-go criteria for each branch with the decision-making authority clearly defined
Submission Guidance
In a phased rollout, Branch 3's UAT must include regression testing for Branches 1-2. Otherwise you fix Branch 3 and break Branch 1. Show this compounding complexity.
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.