1

Perform Impact Analysis

• For each quality of service requirement:
• Determine the approximate size <TBD: Size in what units?>
• Determine the approximate complexity <TBD: in what units>
• Determine the approximate regression effect. <TBD: On previously implemented features?>
• Update the Impact Assessment field with the results of these approximations.

2

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.

3

Determine Priority

• Examine the quality of service requirements list and for each requirement, determine if it is in the Surprise, Required, or Obvious categories of the Kano model. Use the lifestyle snapshot to help determine which category a requirement is in. Assign priority as follows:
• Must Have. If the quality of service requirements are in the Surprise category, set the priority to Must Have. The Surprise category requirements are the most desirable for a product.
• Should Have. If the quality of service requirements are in the Required category, set the priority to Should Have. The Required category requirements are important to users.
• Could Have. If the quality of service requirements are in the Obvious category, set the priority to low. The Obvious category requirements do not improve or hinder customer satisfaction.
• Won't Have. For any quality of service requirements deemed unlikely to be implemented, set the priority to Won't Have, and close the requirement. Set the Reason to Abandoned, or Out of Scope.
• If the quality of service requirement might be implemented in a future release, close it as deferred.
• Publish the changes to the work item database and save the quality of service requirements list on the project portal.

4

Select Requirements for Iteration

• According to priority, select a set of quality of service requirements to implement in the next iteration.
• Consider the impact analyses for each quality of service requirement. Be sure the requirements represent a reasonable workload for the next iteration.
• For each quality of service requirement selected for the next iteration, update its Planned Iteration field to reflect the next iteration.

Prioritized list of quality of service requirements.