MSF for CMMI Process Improvement Visual Studio Team System logo
workstreams icon

Create a Scenario

Business Analyst

Participating Roles

Responsible:

Business Analyst

User Experience Architect

Overview

Entry Criteria

    When:

    • Iteration begins.

    Dependencies:

    • Scenario List: The scenario list may be empty, or have some initial scenarios identified.
    • Personas: The personas describe fictional users and provide understanding of product interaction in scenarios.
    • Test Approach: The test approach provides test goals and resource information such as potentially reusable test data.
    • Lifestyle Snapshot: The lifestyle snapshot describes personal information about each persona in a prototypical day.

    Activities

    1

    Brainstorm Scenarios

    • Optional
    • Determine Scenario Goals.
    • Determine Scenarios.

    2

    Prioritize Scenarios

    • Scenario Impact Analysis.
    • Split or Reprioritize Scenarios.
    • Determine an Overall Priority.
    • Outline High Priority Scenarios.
    • Select Scenarios for Iteration.

    3

    Write Scenarios

    • Choose Appropriate Persona.
    • Write Scenario.
    • Split Scenario.

    4

    Storyboard Scenarios

    • Consider Scenarios.
    • Generate Screenshots.
    • Create Screen Flow Diagram.

    5

    Validate Scenarios

    • Validate Scenarios Against User Domain.
    • Validate Scenarios Against Project.

    6

    Write User Acceptance Tests

    • Identify Preconditions.
    • Write Steps.

    Exit Criteria

    Prioritized list of scenarios.

    Scenarios are validated and written with enough detail to enable implementation.

    User acceptance tests are written.

    (C) 2005 Microsoft Corporation. All rights reserved.

    MSF for CMMI Process Improvement: Build 050707