Set Speed

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Business Story

Box-Out.png
Exit

  • Business Story

Star.png
Solution

process-descending-24px.png
Process

Set Speed.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

  • Historias_Negocio.doc

stuff.png
Examples

  • None

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used in projects where the technology area must notify the business area the speed with which the development team can schedule the ideal engineering time per month, in order to enable the latter to establish the scope of a particular version of the application to be developed.

The speed is set as the user stories completed at each iteration by the team.

end-flag.png
Result Context

The business area knows the number of stories points (a point of story is a week in the estimation of each story) that will be delivered at the end of the 3 highest estimates story weeks.

cloud.png
Problem

The speed must be obtained from an empirical method.

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:: It should be obtained as long as the business area requires this data to establish a scope of a version of the application to be developed.

roles.png
Roles

  • Controller (1)

lightbulb.png
Lessons Learned

  • The rate serves to the area of technology to limit requests business area in establishing the scope of a release. If speed is not set correctly the development team can not meet deadlines. The best to set the speed is to assign each programmer a point of story, so if they are 6 programmers, the speed will be 6 points of story each week. If the speed is multiplied by the 3 weeks of estimation the number of points maximun for setting up the story of a version field is obtained.
  • Input document is an internal document for development. It should contain a table with the classification of business records as a function of value and risk. In this document the speed is recorded.
  • The output document must have the filling velocity field.

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