Example of a user story (eXtreme Programming)

User stories describe system functions from the user's point of view. through discussion with the user, we can conclude that in fact, XP practices should be written by the user, but it is not easy for many users, so many practices are written by developers and users.

Developers estimate the time required to complete each task based on the description in the user story, and claim the tasks they are responsible for from the project manager. Developers are generally encouraged to claim different types of tasks each time, to enhance the understanding of the entire project and master different types of technologies. The estimated time may be significantly different from the actual completion time in the early stage of the project. However, after a period of implementation, the test time can also be around the corner.

After obtaining the tasks that you are responsible for, the developers will find their teammates and start the implementation process. The two generate software design while discussing and designing, and put them into testing andCodeOnly unit tests and code are produced here. As for the design, all the results can be placed on the draft paper. Once the test and code are completed, it makes no sense. If there are obvious differences during the discussion, we should take the idea of the task owner first. It should be noted that each task is assigned a "owner", but the idea of XP is that the entire development team is responsible for the code, not the individual, in fact, even a single task is completed by multiple developers. XP encourages frequent change of teammates, even if they are only in a single task.

The following is an example of a user story:

Story 2 run the refund request processing story (Priority: high technical risk: Low)
Estimation: 2 weeks of development time
2.1 obtain the bank refund details for a certain period of time 0.5 days
2.2 display the bank's refund details list for a certain period of time by PAGE, and provide the selection of refund records for 2.5 days
2.3 refund for Operation Processing 2 days
2.4 (constraints) 2.3 refund information card number and name information can be added. If you need to enter a card number, you must enter it twice for review.
2.5 (constraints) 2.4 The input card number provides 3 4-digit input and 4th unlimited-digit input segments, facilitating Proofreading
2.6 (constraint) 2.4 The unit number is followed by a note (this) (different) to distinguish the space of the local and remote cards.
2.7 (constraints) 2.3 you can select partial or all details for refund Processing
2.8 (constraints) 2.3 after processing, the refund details record status should be changed to the running handled status and set the running processing date
2.9 (constraints) 2.3 After confirmation, a confirmation dialog box is required to prevent misoperation
2.10 refund details list can be obtained by condition for one day
2.11 (constraints) 2.10 conditions can be: Bank & refund processing status & refund request Date segment
2.12 (constraints) 2.10 conditions can be: Merchant & refund processing status & refund request Date segment
2.13 (constraints) refund in the application status is not required to be queried
2.14 display the list of refund details processed by the operation on the page according to the conditions for 1.5 days
2.15 (constraints) 2.14 The table header must contain query condition information, total number of transactions and amount information
2.16 refund details list can be downloaded for 2.5 days
2.17 (constraints) 2.16 organize data into execl table format
2.18 (constraints) 2.16 tables can be generated by each payment gateway
2.19 (constraints) 2.16 tables can be generated by each merchant
In the 2.20 (constraint) 2.16 table, some payment gateways can be printed or not on some topics except the basic section.
2.21 refund transactions that have been processed can be rolled back to the Operation Department for re-processing.
2.22 (restricted) 2.21 the refund transaction that can be rolled back must have not been refunded by the finance.