Skip to main content
Sign In |
  Help (new window)

Enterprise MSF Agile (with CobiT)

Go Search
Home
  
Enterprise MSF Agile (with CobiT) > Wiki Pages > Activity - Storyboard a Scenario (Create a Scenario)  

Activity - Storyboard a Scenario (Create a Scenario)

View All Site Content

Recent Changes
Activity Information

Storyboard a Scenario

Create a ScenarioStoryboard a Scenario

Description

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.

Roles

PerformerBusiness Analyst

Attributes

CategoriesMSF Agile Principles - Partner with Customers, Iteration, MSF Agile Principles - Foster open communications, MSF Agile Principles - Establish Clear Accountability, Build, User Experience, MSF Agile Principles - Work Toward a Shared Vision , AI1.1 Def and Maintenance of Business Func and Tech Requirements

Steps

  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.

Inputs and Outputs

WorkProductInputOutputAllowable States
Scenario(none)
Storyboard(none)

Predecessors

TypeNameDependency Type
Write Scenario DescriptionFinish-Start

Successors

TypeNameDependency Type
Divide Scenarios into TasksFinish-Start

Last modified at 1/17/2008 11:18 PM  by Administrator