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

Project Portal
| ### Next Steps Plan an Iteration |
| Create a Scenario Business Analyst
|  | Participating Roles Responsible: Business Analyst
### 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 prototype are written. # Entry Criteria Dependencies: The vision statement is published to the project portal. # Activities
1 | Brainstorm Scenarios | Determine the system goals. Identify unique scenarios.
2 | Develop Lifestyle Snapshot | Optional Identify a typical system use. Identify technical opportunities.
3 | Prioritize Scenario List | Determine scenario priority. Gather implementation estimates. Reprioritize the scenarios.
4 | Write Scenario | Choose the appropriate persona. Write the scenario. Split the scenario.
5 | Storyboard a Scenario | Optional Determine storyboarding tools. Generate screenshots. Create a screen-flow diagram.
# Exit Criteria
| The scenario list contains entries for the known, significant, and differentiated scenarios.
| Testable descriptions of all of the scenarios are scheduled to be developed or prototyped in the upcoming iteration are reviewed and published.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |