Testing, Deployment, and Implementation Lifecycle
What the exam tests
This domain tests the implementation lifecycle: requirements, configuration in sandbox, testing, deployment, and post-go-live support. Expect questions on environment strategy, test coverage, and cutover readiness.
Core rules and concepts
- Use a phased lifecycle: discover, design, configure in sandbox, test, train, deploy, hypercare. Each phase needs exit criteria.
- Test levels: unit or configuration tests, integration tests, UAT with business users, regression, and security or negative tests.
- Deployment promotes tested configuration, not ad hoc changes. Freeze configuration before cutover and keep a rollback plan.
- Data cutover needs a rehearsal: extract, transform, load, reconcile, and validate in a staging environment.
- Hypercare should have defined duration, triage path, and success metrics.
Worked example
A service organization is ready to deploy a new case type. Configure and unit-test in sandbox, run integration tests with the email channel, conduct UAT with agents using real scenarios, then freeze and promote. Rehearse the data cutover and reconcile open cases. The reasoning: each test level catches a different defect class; the freeze prevents last-minute drift; reconciliation proves the migration.
Traps
- Testing only as an administrator; agents hit permission and data-scope issues.
- Skipping regression after a small change.
- No cutover freeze or rollback plan.
- Declaring go-live without hypercare criteria.