Set Scope Version

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Business Story

Box-Out.png
Exit

  • Story Scope Version X
  • Business Story

Star.png
Solution

process-descending-24px.png
Process

Set Scope Version1.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_Ambito_Ver_X.doc

stuff.png
Examples

  • None

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used on all projects in which the delivery of application to the area of business will be organized versions or incrementally.

end-flag.png
Result Contextt

The business area gets a fully operational product and ready to run with a particular functionality.

cloud.png
Problem

The business area should establish the scope of that version. It is they who determine the records that are part of a particular version. The technology area is limited to receiving the list of records selected by the business area.

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

roles.png
Roles

  • Area of business users(2 at most)
  • Developers (2-12)
  • Director of Development Project (1)
  • Trainer (1)
  • Controller (1)

Note: The trainer and driver can be the same person.

lightbulb.png
Lessons Learned

  • Stories should be chosen with the highest value to the business from among the remaining unimplemented considering speed restrictions in the area of technology. If the number of selected stories is too adjusted for each field at the speed of development it can lead to delays in deliveries by overwork.
  • The business choose that version for the stories that it qualified with the higher value considering the speed set by technology. The number of points of stories selected for the version may not exceed 3 speed.
  • Referring to the output product Story Business, the selected stories are marked with the corresponding version to keep control over them in the general document stories.
  • The output product Story Scope X version is a selection of records for the scope of the corresponding version.

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