Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| See Also Scenario List Prioritize Quality of Service Requirements List |
| Activity: Review Objectives
Business Analyst
Project Manager
|  |  |  | Guide Project |  |
|  | Participating Roles Responsible: Business Analyst Project Manager
### Overview After every iteration, except iteration 0, the product should be stable and worthy of being shipped. Set the minimum acceptance level bar and then measure the scenarios and quality of service requirements delivered against the minimum acceptance level. This level must constantly be evaluated against changing needs, market conditions, or expectations. The minimum acceptance level is updated after each iteration. # Entry Criteria The scenario list is up-to-date and prioritized. The quality of service requirement list is up-to-date. # 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.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |