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

Project Portal
| ### Next Steps Write User Acceptance Tests |
| Validate Scenarios ( 3 : RD : 3 : 3.5 ) User Experience Architect
Activity: Validate Scenarios
User Experience Architect
Subject Matter Expert
Business Analyst
|  |  |  | Planning |  |
|  | Participating Roles Responsible: User Experience Architect Subject Matter Expert Business Analyst Accountable: Product Manager
### Overview After scenarios are written, they must be validated to ensure that they adequately describe all user interactions with the product. The subject matter expert, business analyst, and user experience architect perform the review. The subject matter expert provides expertise on the user domain. The scenarios are also validated to ensure they can be implemented in the project without any confusion or problems. If any problems are spotted, the scenarios must be fixed so that they are valid at the conclusion of this activity. # Entry Criteria Scenarios The scenarios are prioritized and written. When: Scenarios are written. # Sub-Activities
1 | Validate Scenarios Against User Domain | The subject matter expert, business analyst, and user experience architect review each scenario in the context of the user domain to validate that all scenarios adequately represent the user problem to be solved. If a scenario is not valid, it is revised so that it is valid. Review each scenario for the following characteristics. Each scenario is written in the context of what task users need to perform, their background knowledge, and how users expect to interact with the product. Each scenario outlines a problem, and is not obscured by proposed solutions to the problem. All relevant user interactions with the product are identified.
2 | Validate Scenarios Against Project | The subject matter expert, business analyst, and user experience architect review each scenario in the context of the project to validate that all scenarios can be implemented successfully. If a scenario is not valid, it is revised so that it is valid. Review each scenario for the following characteristics: Each scenario can be implemented with the available techniques, tools, resources, and within cost and schedule. There is a single interpretation for each scenario, and the meaning is easily understood. No scenario conflicts with another scenario. Each scenario is testable.
# Exit Criteria
| The scenarios are validated for the user domain and for implementation in the project.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |