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

Project Portal
| See Also Brainstorm Quality of Service Requirements |
| ### Next Steps Prioritize Scenarios |
| Brainstorm Scenarios ( 2 : REQM : 1 : 1.1 ) ( 3 : RD : 1 : 1.1 ) ( 3 : RD : 1 : 1.2 ) ( 3 : TS : 1 : 1.2 ) Business Analyst
Activity: Brainstorm Scenarios
Business Analyst
User Experience Architect
|  |  |  | Planning |  |
|  | Participating Roles Responsible: Business Analyst User Experience Architect
### Overview To brainstorm and add scenarios to the scenario list, the user experience architect and business analyst analyze the product’s goals and how it is used by each of the personas. Scenario entries are added to the scenario list for each goal. Then each scenario entry is further defined by adding a description. An initial scenario list is created during the first iteration. The scenario list is revisited and modified as business requirements change or as new scenarios are discovered. # Entry Criteria Personas The personas are defined. Scenario List The scenario list may be empty, or have some initial scenarios identified. When: Iteration starts. # Sub-Activities
1 | Determine Scenario Goals | Open the scenarios list. Be sure the list is up-to-date. If any new scenarios have been created since the last time the list was opened, be sure to import them into the list. Both the user experience architect and business analyst brainstorm the scenarios. Determine the goals of the product by selecting a single persona and explore the ways the persona would use the product. Write the goal as a top level scenario entry on the scenario list.
2 | Determine Scenarios | Both the user experience architect and business analyst continue brainstorming to determine the scenarios. Select a goal and examine the various ways the persona can achieve or fail to achieve the goal. Choose a scenario name that is descriptive of how the persona attempts to reach the goal. Add a scenario entry with this name to the scenario list. If the purpose of the scenario is not obvious from the name, rename it or add a description of the purpose in the description field of the scenario list. The purpose is often the differentiating factor that separates one scenario from another. Add each scenario to the scenarios list and assign each to a business analyst. Publish the scenarios list to the work item database and then save the list spreadsheet on the project portal.
# Exit Criteria
| The scenario list describes all fundamental user interactions with the product.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |