Sort by Value

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

Sort by Value.png

time-24px.png
Development time

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

video-24px.png
Explanatory video

  • None

Search-32px.png
Quality Controllers

  • None

template.png
Templates

Historias_Negocio.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 requiring prioritization by business area about stories written by themselves and then estimated by the area of technology. This prioritization is marked by the value that would bring new functionality to the business when it is developed. Within this classification three groups are established, the stories that describe essential features, the important and the miscellaneus items.

end-flag.png
Result Context

A set of estimated record sorted by technology will be obteined, but they will be ordered depending on the value contributed the bussiness. Within this set 3 subsets will be taken (essential, important and miscellaneous).

cloud.png
Issue

The business area should have very clear what role each story represents in the application to develop and not be swayed by the story that represent irrelevant features (miscellaneous) rather than essential, for example.

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: The user must have formal studies of functional viability with the pros and cons of the functionality described for each of the stories to launch a reliable opinion. The first to develop should be essentials.

roles.png
Roles

  • Area of business users (2 at most).

lightbulb.png
Lessons Learned

  • The vision of the application to be obtained should be clear. The most important features must be classified above than those that are merely decorative.
  • It must be refill the field indicating the priority of the record from the point of view of business. There are three categories (A- (high) Essentials, M (medium) Needed, B- (low) Miscellaneous).

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