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

Project Portal
| Create a Scenario Business Analyst
|  | Participating Roles Responsible: Business Analyst User Experience Architect
### Overview Scenarios capture the functional goals of the system. To find these goals, examine the unique needs for each persona of the system. These goals can be initially listed and later written as scenarios. For each of these goals, also consider the scenarios that may result from unsuccessful or non-optimal attempts to reach the goal. Scenarios are created through brainstorming, lifestyle snapshots, or exploratory testing and added to the scenario list. Scenarios are prioritized and written when they are scheduled for an upcoming iteration. Scenario creation is complete when all of the scenarios scheduled for delivery in an iteration or architectural prototypes are written. # Entry Criteria Scenario List The scenario list may be empty, or have some initial scenarios identified. Personas The personas describe fictional users and provide understanding of product interaction in scenarios. Test Approach The test approach provides test goals and resource information such as potentially reusable test data. Lifestyle Snapshot The lifestyle snapshot describes personal information about each persona in a prototypical day. When: Iteration begins. # Activities
1 | Brainstorm Scenarios | Optional Determine Scenario Goals. Determine Scenarios.
2 | Prioritize Scenarios | Scenario Impact Analysis. Split or Reprioritize Scenarios. Determine an Overall Priority. Outline High Priority Scenarios. Select Scenarios for Iteration.
3 | Write Scenarios | Choose Appropriate Persona. Write Scenario. Split Scenario.
4 | Storyboard Scenarios | Consider Scenarios. Generate Screenshots. Create Screen Flow Diagram.
5 | Validate Scenarios | Validate Scenarios Against User Domain. Validate Scenarios Against Project.
6 | Write User Acceptance Tests | Identify Preconditions. Write Steps.
# Exit Criteria
| Prioritized list of scenarios.
| Scenarios are validated and written with enough detail to enable implementation.
| User acceptance tests are written.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |