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

Project Portal
| ### Next Steps Build a Product |
| Implement a Development Task Developer
|  | Participating Roles Responsible: Developer
### Overview A development task is a small piece of development work that stems from a quality of service requirement or scenario. Implementing a development task involves adding the appropriate new functionality to the architectural form of the system. Once the development task has been completed, it must be unit tested, reviewed, code analyzed, integrated, and checked into the existing code base. The scenario or quality of service requirement is then passed on to test. # Entry Criteria Dependencies: The development task is assigned. # Activities
1 | Cost a Development Task | Estimate task length. Balance load. Refine the task and define integration points.
2 | Create or Update a Unit Test | Identify unit test scope. Write or update the test. Validate the unit test.
3 | Write Code for a Development Task | Select component. Create new classes and methods. Implement method logic.
4 | Perform Code Analysis | Determine application rules. Stay in zero defect state. Drive down defects by category.
5 | Perform a Unit Test | Identify unit test from collection. Perform the unit test. Debug code.
6 | Refactor Code | Identify complexity. Apply refactoring. Perform unit test.
7 | Review Code | Verify name correctness. Verify code relevance. Verify extensibility. Verify minimum code complexity. Verify algorithmic complexity. Verify secure code. Fix review changes.
8 | Integrate Code Changes | Check dependencies. Test and integrate with other development tasks. Check in set of changes.
# Exit Criteria
| The code coverage for the unit tests meets the test target.
| The functionality described in the development task is fully implemented.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |