MENU
The following checklist has been produced to help reviewers detect defects with user stones:
User Story Checklist:
1. The user story must have a unique identifier
2 The user story must contain the user/customer
3 The user story must contain the need
4. The user story must contain the reason.
5. The user story must contain testable acceptance Criteria-Using the checklist above what is wrong with the following user story?
User Story US2018
As a bank account customer, I would like to transfer money from one account to another using the mobile banking application by using the drag
and drop feature.
This is acceptable when
* I can drag and drop from one account to another and select any of the pre-defined amounts
* I can drag and drop from one account to another and type in any positive amount
* Once I confirm the details the amount is debited from the first account and credited to the second account
According to the user story checklist, the user story must contain the reason for the need, which is usually expressed by using the word ''so that'' or ''because''. For example, the user story could be rewritten as:
User Story US2018 As a bank account customer, I would like to transfer money from one account to another using the mobile banking application by using the drag and drop feature,so that I can easily manage my finances.
This way, the user story provides a clear value proposition and a justification for the need. The reason also helps to define the scope and priority of the user story, as well as to verify the acceptance criteria.