MSF for Agile Software Development Visual Studio 2005 Team System logo

Activity:

Review Objectives

Participating Roles

Responsible:

Project Manager

Consult:

Business Analyst

Overview

Entry Criteria

    Dependencies:

    • The scenario list is up-to-date and prioritized.
    • The quality of service requirement list is up-to-date and prioritized.

    Sub-Activities

    1

    Set Minimum Acceptance Level

    • Evaluate the market or user expectations for the product. Consider competitors in the market, previous systems, or business needs.
    • Review scenarios and quality of service requirements against the market or user expectations to create a minimal acceptance level.
    • Mark each scenario or quality of service requirement in the lists against this minimal acceptance level.

    2

    Report Current Level

    • Run the current minimum acceptance level report to determine the progress of the development effort.

    Exit Criteria

    The minimum acceptance level is defined.

    Progress toward the minimum acceptance level is reported.

    © 2005 Microsoft Corporation. All rights reserved.

    Build 100.2