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

Project Portal
| ### Next Steps Develop Performance Model Schedule Quality of Service Requirement Implement a Development Task Test a Quality of Service Requirement |
| Activity: Divide Quality of Service Requirements into Tasks
Project Manager
|  |  |  | Plan an Iteration |  |  |  | Task |
|  | Participating Roles Responsible: Project Manager Consult: Developer
### Overview Each quality of service requirement is divided into development tasks for implementation. Dividing a requirement into smaller development tasks improves the accuracy of cost estimates and provides developers with a better understanding of the work needed. There are often multiple development tasks that are needed to fulfill a given quality of service requirement. The key to successfully dividing the quality of service requirement into tasks is to involve the developers in the division and encourage them to select their own development tasks. All development tasks must be selected. # Entry Criteria When: A performance requirement is scheduled for the upcoming iteration. Dependencies: The performance requirement has broken down into individual tasks. # Sub-Activities
1 | Identify Development Tasks | Determine the impact of the quality of service requirement. Find the related scenarios from the links and review them. Quality of service requirements vary in their total impact. Some impact a single scenario while others might affect multiple scenarios. Identify how system components are affected when implementing the quality of service requirement.
2 | Create Development Tasks | Create a new development task for each major area of the system touched by the scenario. For each task, describe the new or changed functionality. Keep the tasks broad enough to allow design to emerge but focused enough that a single person could complete them in one to three days. Group low level changes that are logically related into higher level tasks. Further divide high level changes and additions into lower level tasks if they are broad. Review the set of tasks to ensure that they adequately address the quality of service requirement.
3 | Choose Development Tasks | Developers choose their development tasks. Check to make sure all development tasks are chosen.
4 | Reassign the Quality of Service Requirement | Reassign the quality of service requirement to the developer who owns development tasks for that scenario. This developer’s job is to test the end-to-end integration of the development tasks.
5 | Create Test Tasks | Gather the testers to write the verification tests for the scenario. Divide the scenario into test tasks, using the test strategy for the system. Update the test approach document for the iteration, filling in the test data and other sections. Determine which tests can be automated and added to the iteration tests. Allow the testers to choose their tasks and be sure all test tasks are chosen.
# Exit Criteria
| The list of tasks describes all the work necessary to fulfill the requirement.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |