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

Project Portal
| ### Next Steps Schedule Scenario Implement a Development Task Test a Scenario |
| Activity: Divide Scenarios into Tasks
Project Manager
|  |  |  | Plan an Iteration |  |  |  | Task |
|  | Participating Roles Responsible: Project Manager Consult: Developer
### Overview A scenario is divided into the development tasks to implement the scenario. Dividing scenarios further defines cost estimates and provides developers with a better understanding of the work to be accomplished. Some scenarios might impact multiple partitions within an application. In this case, separate tasks are created for each affected partition. A final integration task may be necessary to integrate the tasks. # Entry Criteria Dependencies: The scheduled scenario is written, published to the project portal, and storyboarded if necessary. # Sub-Activities
1 | Identify Development Tasks | Identify developers to work on the scenario. Begin where the scenario differs from previously implemented scenarios and follow the control path through the system. Consider user visible features, changes to the underlying infrastructure or data structures and items that have architectural impact. Identify how system components are affected when implementing the planned scenario.
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 to be implemented. 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. Make sure each task can be unit tested. 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 scenario.
3 | Choose Development Tasks | The developers choose their development tasks. Check to make sure all development tasks are chosen.
4 | Reassign Scenario to a Developer | Reassign the scenario to one of the developers 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 | Identify the testers who are writing the verification tests for the scenario. Divide the scenario into test tasks, in accordance with 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. The iteration tests run after the build verification tests. Allow the testers to choose their tasks and be sure all test tasks are chosen.
# Exit Criteria
| The initial iteration plan contains tasks describing all work necessary to fulfill all scenarios.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |