Estimate Task

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Story Task version X Developer Y

Box-Out.png
Exit

  • Story Task version X Developer Y

Star.png
Solution

process-descending-24px.png
Process

Estimate Task1.png

time-24px.png
Development time

    • To acquire the necessary knowledge to develop the software product:
    • To create the Product Pattern: 45 minutes.
    • To apply the Product Pattern:

video-24px.png
Explanatory video

    • Not applicable




Search-32px.png
Quality Controllers

  • None

template.png
Templates

  • Tareas_Historias_Ver_X_DyD_Y.doc

stuff.png
Examples

  • None

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used on any project on which it must be estimated the technical tasks to perform resulting from the processing of business records in these tasks.

end-flag.png
Result Context

Developers get an estimate of the ideal number of days of engineering to implement each of the tasks assigned to them.

cloud.png
Problem

Developers should be able to estimate each task, and divide tasks requiring more than a few days to be implemented or group them.

forces.png
Restrictions (Forces)

  • Characteristics of organizations: This pattern can be used in existing projects in any company.
  • System Type to develop This product can be used in projects in which user requirements are changing.
  • Type of Customer: It must exist or be achieved, the target area development business being involved in achieving it.
  • Heuristics for use:: Estimation techniques based on Albretch function points and COCOMO can be used.


roles.png
Roles

  • Developers (2-12)

lightbulb.png
Lessons Learned

  • The programmer must estimate the tasks that are assigned to him, and depending on the result of estimation, comparing the tasks that finish in time or not he must decide if they must be divided into simpler ones or if instead they must be grouped.
  • The developers estimate tasks and decide their division or group comparing tasks that finish in time with no.
  • The output document Story Task version X Developer Y is exclusive to the developer concerned with the tasks that have been assigned. If the estimation of the task is not acceptable the field is marked. If the task is very simple the field corresponding is marked.

award.png
Capability Level

  • Not applicable.

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Knowledge of coding standard that defines the shared code ownership and the rules for writing and documenting code and communication between different pieces of code developed by different teams. Programmers have to follow the so that the code in the system look like if it had been written by one person.
  • Knowledge of the common vision of how the program works in which the activities take place.


help-24px.png
Abilities

  • Ability to work in group. All on an XP computer contribute in any way they can.
  • Predicting what will be completed by the deadline, and determining what to do next.
  • Programming capability in pairs. Besides to generate better code and tests, used to communicate knowledge through teams.


Information-Sources.png
Information Resources