Divide Story

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Business Story

Box-Out.png
Entries

  • Business Story

Star.png
Solution

process-descending-24px.png
Process

Divide Story1.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

stuff.png
Examples

  • None

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used on any project in which once written the story and delivered to the area of development, they can not estimate it due to it is very complex to be treated unitarily, which should be divided into smaller ones.

The user story should be able to be scheduled at a time between one and three weeks. If the estimate is greater than three weeks, should be divided into two or more story. If less than a week, should be combined with another record.

end-flag.png
Result Context

A new set of records (2 to n) for each initial story is obtained that could not be estimated by the technology area.

cloud.png
Problem

The business area should be able to split the stories no estimated in a number of specific stories than can be reflected unitarily. They should be as simple as possible.

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 must be set up meetings between business and technology areas where communication is smooth and has mutual trust. The workspace should be organized according to the guidelines of the methodology. It is important to keep food and drink to ensure meetings are relaxed.

roles.png
Roles

  • Area of business Users(2 at most)

lightbulb.png
Lessons Learned

  • Stories should be as atomic as possible, if not it should be returned by the technology area. A feature story.
  • To establish meetings which always involved the business area along with the development team (developers included).

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