|
|
|
|
|
|
|
|
|
Enterprise MSF Agile (with CobiT) > Wiki Pages > Activity - Cost a Database Development Task (Create a Quality of Service Requirement)
|
Activity - Cost a Database Development Task (Create a Quality of Service Requirement)
|
|
|
|
|
|
Activity Information/Wiki%20Pages/images/icons/activity.gif) Cost a Database Development Task
DescriptionEstimating the cost of database development tasks helps scope features, schedule, and prioritize work. The costing of all development tasks is done during 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. The tasks are prioritized by the project manager and business analyst and tasks having the lowest priority are deferred. After a database development task is chosen, it is the responsibility of the database developer to cost the task. Before beginning costing of the database development task, it is important for the database developer to review the assigned task to understand its scope and requirements, and discuss the estimation with other database developers. This ensures all team members have the same expectations surrounding the task at hand. StepsReview Assigned Task:
Review work item currently assigned to you associated with this task.
Understand the scope and requirements of the task.
Get an overview and discuss the requirement with the project manager and business analyst.
Refine the Task:
Examine the development task in the context of the other development tasks for any parts of the scenario or quality of service requirement that are not yet covered by a development task. Create new development tasks to cover these areas.
Work with the project manager to add new development tasks to the iteration plan. 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 database unit tests.
Factor in risk associated with the development task based on existing unit test coverage. Balance Load:
The tasks are prioritized by the project manager and business analyst, and tasks having the lowest priority are deferred. If the estimate creates more work than can be accomplished in the iteration, work with the project manager to properly prioritize and load balance the tasks for the iteration. 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.
Inputs and Outputs| WorkProduct | Input | Output | Allowable States |
|---|
| Task | /Wiki%20Pages/images/Input.gif "Input") | /Wiki%20Pages/images/Output.gif "Output") | Active |
|
Last modified at 1/17/2008 11:18 PM by Administrator
|
|
|
|
 |
|
|
|
|