MSF for Agile Software Development Visual Studio 2005 Team System logo

Activity:

Prioritize Quality of Service Requirements List

Participating Roles

Responsible:

Business Analyst

Overview

Entry Criteria

    Dependencies:

    • The iteration length is determined and communicated.
    • The quality of service requirements list is published to the project portal and is up-to-date.

    Sub-Activities

    1

    Determine an Overall Priority

    • Assign an overall priority for each scenario in the list. Record the corresponding numeric value in the rank field in the scenario list.
    • Sort the quality of service requirements list by rank. Place the highest priority quality of service requirements first on the list. Rank the remaining requirements against one another.
    • Close low priority requirements unlikely to be implemented using the proper reason code.
    • If the quality of service requirement might be implemented in a future release, mark it as deferred.
    • Save and publish the list to the project portal.

    2

    Outline High Priority Scenarios

    • Use the scenario template to outline and provide a brief description of the highest priority scenarios. The outline should contain enough detail for developers to provide an estimate.
    • Add notes in the description field outlining complexities surrounding of the quality of service requirements.
    • Save and attach the outlined scenario to the scenario work item.

    3

    Communicate Need for Estimates

    • Send notification to the developers requesting general estimates for the top requirements.
    • Set expectations that the estimates are used to get an overall understanding of how difficult each quality of service requirement is to implement.
    • Assign a due date for returning the estimates. Provide a description for the scenario if any additional details are needed.
    • Notify the project manager to begin iteration planning.

    4

    Split or Reprioritize Requirements

    • Optional
    • If the cost of the quality of service requirement exceeds the iteration budget, determine if the requirement can be split.
    • Split the quality of service requirement into two or more smaller ones if splitting is deemed appropriate.
    • Close out or defer any quality of service requirements deemed too costly.
    • Revisit the priorities based on development estimates and obtain further estimates to identify requirements for the upcoming iteration.

    Exit Criteria

    A prioritized list of quality of service requirements is published to the project portal.

    The highest priority quality of service requirements in the list have completed estimates.

    © 2006 Microsoft Corporation. All rights reserved.

    Version 4.1.0