MSF for Agile Software Development Visual Studio 2005 Team System logo

Activity:

Storyboard a Scenario

Participating Roles

Responsible:

Business Analyst

Overview

Entry Criteria

    Dependencies:

    • 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.

    © 2006 Microsoft Corporation. All rights reserved.

    Version 4.1.0