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

Project Portal
| ### Next Steps Divide Scenarios into Tasks |
| Activity: Storyboard a Scenario
Business Analyst
|  |  |  | Create a Scenario |  |
|  | Participating Roles Responsible: Business Analyst
### Overview Storyboarding augments scenarios and provides user interface details. It is only used when user interface detail plays an important role in satisfying the external users. Storyboarding can also align projects across organizations. The storyboard can include a variety of graphical elements including screenshots, application mockups, and screen flow diagrams. It might also include a short narrative describing the persona’s path through the system. A visual depiction of the scenario greatly improves comprehension among end users and developers. If storyboards are created for each individual scenario, it is possible to combine them into a high level application overview. # Entry Criteria Dependencies: Scenario is Written: The scenario description is written and attached to the scenario work item. # Sub-Activities
1 | Consider Scenarios | Identify the sections of the scenario that warrant a storyboard. Consider how these sections relate to other scenarios already written. Group sections into a single storyboard where applicable.
2 | Generate Screenshots | Tools that work well for storyboards include Microsoft Visio and Microsoft PowerPoint. Capture the screens that are presented to the persona. Draw out a rough sketch of the user interface called for in the scenario. Collaborate with members of the development team to ensure the user interface is consistent with the user interface metaphor. Organize screenshots into a coherent presentation. Add short text or voice narrative that describes the user interactions.
3 | Create Screen Flow Diagram | Use boxes to represent screens, and arrows to indicate linkage. Save the storyboard and attach the storyboard to the scenario. Save the storyboard to the project portal and link the storyboard to the scenario.
# Exit Criteria
| Storyboard is sufficiently detailed to use as input to the design process.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |