Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| ### Next Steps Analyze User Acceptance Test Results |
| User Acceptance Testing ( 3 : VAL : 2 : 2.1 ) Tester
Activity: User Acceptance Testing
Tester
User Experience Architect
|  |  |  | Deploy |  |
|  | Participating Roles Responsible: Tester User Experience Architect Accountable: Test Manager Informed: Release Manager
### Overview User acceptance testing validates that the product delivers what the sponsor, business case, vision statement, and ultimate consumer need and want from a product release. User acceptance testing enforces the MSF principle that quality is defined by the customer. The purpose is not to validate that the release candidate conforms to the specification, but to agree that the release delivers what the market needs. Any variation from specification should be recorded and used as feedback for future product definition and planning. # Entry Criteria User Acceptance Tests Tests written to validate the customer requirements. Validation Approach An approach for conducting user acceptance testing according to established guidelines. Release Candidate Build A build which has passed user acceptance test criteria and is now considered a release candidate. # Sub-Activities
1 | Run User Acceptance Tests | Run a series of tests defined for the functionality in release candidate build.
2 | Report Results | Test results including bug reports from failed tests and change requests from exploratory testing activities.
# Exit Criteria
| Test results including bug reports and change requests.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |