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

Project Portal
| ### Next Steps Create or Update a Unit Test Write Code for a Development Task |
| Activity: Cost a Development Task
Developer
|  |  |  | Implement a Development Task |  |
|  | Participating Roles Responsible: Developer
### Overview Estimating the cost of development tasks helps scope features, schedule, and prioritize work. The costing of all development tasks should be completed and any issues resolved prior to the iteration planning meeting. If the total cost of the development tasks is more than can be accomplished in an iteration, a task must be deferred or reassigned. After a development task is chosen, it is the responsibility of the developer to cost the task. # Entry Criteria Dependencies: The development task is chosen and assigned. The system and application diagrams have been updated as necessary to reflect the architecture for the new scenario or quality of service requirement. # Sub-Activities
1 | Estimate Based on Experience | Estimate based on how long it took to complete a similar task. Consider other development tasks for the scenario or quality of service requirement and the integration costs. Factor in the cost of writing unit tests.
2 | Balance Load | If the estimate creates more work than can be accomplished in the iteration, work with the project manager to load balance the task or move to another iteration.
3 | Refine the Task | Examine the development task for any parts of the system not yet assigned. For those parts, create new development tasks. Assign new tasks to the appropriate developers. Work with the project manager to add new development tasks to the iteration plan.
4 | Define the Integration Points | Work with the other development team members to establish a clear understanding of how this functionality will integrate with other functionality.
# Exit Criteria
| All development tasks for the iteration have a development cost.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |