Set Balance

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Story Tasks version X Developer Y

Box-Out.png
Exit

  • Story Tasks version X Developer Y

Star.png
Solution

process-descending-24px.png
Proces

Set Balance1.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 in any project that has been observed that there are programmers with a load factor too high.

end-flag.png
Result Context

Developers get themselves the assess how busy they are in the project.

cloud.png
Problem

Developers should be able to know if they are too busy or otherwise if they are too lazy.

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 of use::If it need urgent application or dispose of some of their funcionalidades.

roles.png
Roles

  • Developers (2-12)

lightbulb.png
Lessons Learned

  • Programmers who commit too much(the result of adding the estimates of the tasks that were assigned to them by their load factor is high compared to that of other team members) should be released some tasks to establish balance in the team work. If whole team is too involved it must be found a way to back into balance. All programmers should have time to do their jobs and to help their peers to make their own.
  • Developers should add the estimations of all tasks and multiply by its load factor.
  • In the output document Story Tasks version X Developer Y the document header is filled with the balance established by the developer in question.

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