Join Task

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Story Tasks version X
  • Story Task version X Developer Y

Box-Out.png
Exit

  • Story Tasks version X
  • Story Task version X Developer Y

Star.png
Solution

process-descending-24px.png
Process

Join Task.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

bricks.png
Related Patterns

Search-32px.png
Quality Controllers

  • None

template.png
Templates

  • Tareas_Historias_Ver_X.doc
  • 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 in any project that due to the result of the estimation of a task, that is observed which can be completed in a few hours and also can be grouped with other/s task, it is done.

If the task in question is too simple and takes very little time realize it will be necessary to combine it with another.

end-flag.png
Result Context

Developers get new tasks as a result of the grouping of simple tasks.

cloud.png
Problem

Developers must be able to estimate each task, and grouping them, and if possible its implementation in a few hours and they are complementary.

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::If you need urgent application or dispose of some of its functionality.

roles.png
Roles

  • Trainer (1)
  • Developers (2-12)

lightbulb.png
Lessons Learned

  • In the input document Story Task version X Developer Y the field indicating that the task is simply should be marked.
  • In the output document Story Tasks version X new tasks resulting from the union of those with the field in question are added marking the end of the document, eliminating the latter tasks.
  • In the input document Story Task version X Developer Y the new tasks resulting from the union are added to the end of the document, eliminating the latter.
  • Developers group tasks if the estimation and its characteristics allows it.
  • The programmer must group a set of tasks compatible among themselves and whose estimations do not exceed a few hours.

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