Purpose
Test validates that the Pigment solution end-to-end supports the customer's business process and is ready for launch.
This stage answers: Does the solution work as expected? Can users complete the required business processes? What issues need to be fixed, retested, or accepted? Is the customer ready to approve the launch? Are support, ownership, and hand-off needs understood?
Use the Stencil agent
Ask the Stencil agent to generate UAT scenarios, organize feedback, identify retest needs and summarize readiness. See the Stencil Agent Guide for an example prompt for this stage.
Key activities, ownership, and customer actions
| Activity | Owner | Purpose | Customer action |
| Confirm UAT scope and plan | Customer Project Owner/Lead | Align testing scope, owners, timeline and process | Confirm UAT owners and testers, and continue the end-user training and change management planning started in Build |
| Prepare UAT scenarios | Customer Business Leads, with Pigment support | Define how users will validate the solution | Own and prepare UAT scope and scenarios |
| Execute UAT | Customer SMEs / End Users | Test business processes in Pigment | Test real business scenarios, not only feature checks |
| Triage issues | Project Lead / Solution Architect | Categorize defects, questions, enhancements and new requests | Provide clear feedback with examples; prioritize defects, enhancements and new requests |
| Resolve and retest | Solution Architect / Solution Modeler / Customer SMEs | Fix issues and confirm outcomes | Confirm retest outcomes |
| Assess launch readiness | Project Lead / Customer Project Owner / CSM | Confirm open items, risks, support needs and readiness | Approve launch readiness |
| Complete Implementation / UAT Sign-Off | Customer Project Owner / Business Leads | Approve solution for launch (see Roles, Ownership and Governance) |
Required outputs and definition of done
| Required output | Done when |
| UAT plan | Scope, owners, timing, scenarios and process are confirmed |
| UAT scenarios | Test scenarios cover agreed use cases and expected outcomes |
| Issue tracker | Defects, enhancements, questions, retest needs and decisions are documented |
| Retest results | Resolved issues have been retested or accepted with clear rationale |
| Launch readiness summary | Open items, risks, support needs and go-live requirements are documented |
| Updated Project Memory | Testing outcomes, known limitations and support considerations are captured |
| Implementation / UAT Sign-Off | Complete (see Roles, Ownership and Governance) |
Recommended practices
- Prepare UAT before Test begins.
- Use real business scenarios, not only feature checks.
- Separate defects from enhancements and new requests.
- Retest fixes before sign-off.
- Treat UAT as confirmation of readiness, not redesign.
Resources
- UAT Plan Template
- Issue Tracker
- End-User Training Guidance
- Functionality / Use Case Sign-Off
- Implementation / UAT Sign-Off Template
- Launch Readiness Checklist
- Go-Live Checklist