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

Project Portal
| ### Next Steps Schedule Quality of Service Requirement |
| Activity: Estimate Quality of Service Requirement
Project Manager
|  |  |  | Plan an Iteration |  |
|  | Participating Roles Responsible: Project Manager Consult: Developer
### Overview Quality of service requirement estimates are used to provide a general idea of how much effort is needed to implement the requirements. The estimates also assist the business analyst who must make priority decisions and set external expectations. The project manager works with the developers to collect estimates for the top ranked quality of service requirements in the quality of service requirements list. # Entry Criteria Dependencies: The length of the iteration is defined for the project. Notification has been received that quality of service requirements in the quality of service requirements list have been prioritized, published, and are ready to be estimated. # Sub-Activities
1 | Identify a Subset of the Quality of Service Requirement List | Open the quality of service requirements list on the project portal. For each of the highest priority quality of service requirements, determine the appropriate developer or development group to provide an estimate. Trace the quality of service requirement to affected scenarios if applicable. Provide estimates for enough of the highest priority quality of service requirements to allow for large and small scenario options by the business analyst. Provide estimates for enough quality of service requirements to encompass approximately twice the number of ideal person days in an iteration.
2 | Create Implementation Estimates | Work with the developers to estimate the time needed to implement each quality of service requirement. If further elaboration is necessary, work with the business analyst and the developers to create a universal understanding. All estimates should be made in ideal person days. Update the quality of service requirements list to reflect these estimates.
3 | Identify Constraints | Work with the developers to identify risks that can delay or prevent successful completion of the work required for realizing the quality of service requirements, such as knowledge deficiencies and third-party software dependencies. Document any special needs that a quality of service requirement might have. Look for potentially overloaded developers or dependencies that might affect the scheduling. Additionally, consider the architectural impacts. Note any impacts in the description of the quality of service requirement.
# Exit Criteria
| The highest priority quality of service requirements in the quality of service requirements list have estimates that indicate the ideal person days needed.
| The updated quality of service requirements list is published to the project portal.
| Special resources, risks, or constraints associated with realizing a quality of service requirement have been communicated.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |