Description

Roles

Attributes

Steps

1. Gather the Team:
   Gather the architects, developers, and testers who will be working on or impacted by this quality of service requirement. The project manager facilitates the brief meeting or email discussion and records the tasks.

2. Identify Architecture and Development Tasks:
   Find the related scenarios from the links in the quality of service requirement and review them. Quality of service requirements vary in their total impact. Some impact a single scenario while others might affect multiple scenarios. Add any scenarios that were left out by the business analyst.
   
   Ensure that the architecture will be able to handle the quality of service requirement. If architectural changes are necessary, create the roadmap and tasks for refactoring the architecture to the new state. Split the quality of service requirement if necessary.
   
   Create a new development task for each major area of the system impacted by the requirement. 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 Architecture and Development Tasks:
   Architects and developers choose their development tasks.
   
   Check to make sure all of the 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:
   Update the test approach document for the iteration, filling in the test data and other sections. Create a set of tasks to create the necessary test cases to achieve the goal of the iteration.
   
   Determine which tests can be automated and added to the iteration tests. The iteration tests run after the build verification tests.

6. Choose the Test Tasks:
   Allow testers to choose their test tasks.
   
   Check to make sure all test tasks are chosen.

Inputs and Outputs

WorkProduct	Input	Output	Allowable States
Iteration Plan			(none)
Project Checklist			(none)
Quality of Service Requirement			Active
Task			New

Predecessors

Type	Name	Dependency Type
	Identify Security Objectives	Finish-Start
	Schedule Quality of Service Requirement	Start-Start
	Write Quality of Service Requirement	Finish-Start

Successors

Type	Name	Dependency Type
	Implement a Development Task	Finish-Start
	Test a Quality of Service Requirement	Finish-Start
	Develop Performance Model	Finish-Start