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

Project Portal
| See Also How To: Create a Scenario List in Excel Brainstorm Quality of Service Requirements |
| ### Next Steps Prioritize Scenario List |
| Activity: Brainstorm Scenarios
Business Analyst
|  |  |  | Create a Scenario |  |
|  | Participating Roles Responsible: Business Analyst
### Overview A scenario list is a set of scenario entries. Scenario entries are used to identify the scope of the application. A scenario entry consists of the name of the scenario and details on why the scenario is unique. When the spreadsheet is synchronized, the entries become work items. To brainstorm and add scenarios to a scenario list, analyze the application’s goals and how it is used by each of the personas. An initial scenario list is created during the first iteration. Reevaluate and modify the scenario list as the business requirements change or as new scenarios are discovered. # Entry Criteria Dependencies: Personas Defined: The personas are published on the project portal. # Sub-Activities
1 | Determine the System Goals | Open the scenario list in the requirements folder of Team Explorer. The scenario list is linked to the project. Import any scenarios that were created directly through Team Explorer. Determine the goals of the system by selecting a single persona and explore the ways that the persona would use the system. Write the goal as a top level scenario entry on the scenario list.
2 | Identify Scenarios | Select a goal and examine the various ways the persona can achieve or fail to achieve the goal. Pick a descriptive name for the way that the persona attempted to reach the goal. Add a scenario entry with that name to the scenario list. Make sure each scenario assists in meeting the vision identified in the vision statement. If the vision has changed, update the vision statement. If the purpose of the scenario is not obvious from the name, rename it, or add a description in the description field of the scenario list. This description is often the differentiating factors that separate this scenario from the others. Assign the scenarios to a business analyst. Publish the work items in the scenario list to the work item database. Publish the scenario list to the project portal.
# Exit Criteria
| The scenario list is updated with functionality needed to satisfy the project vision.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |