User Stories Below is a list of criteria for evaluating the efcacy of user stories. Independent and does not rely on the implementation of another user story. 1. 2. Emphasizes features that are delivered. A user strut},r should not be a \"to do" list. 3. It uses business language and is written from the perspective of the user. 4. Iiielatiyel},r small, meaning that the user storj,r can be completed in a Sprint. 5. The user stot'j,r should be "testable,\" which means a test case can be created. AnEpic is a large group of work that accomplishes a specic objective. An Epic is decomposed into smaller parts called User Stories. Below are three Epics (Registration, Logiu, and My Account) from a mobile device user= s perspective. And the User Stories identied for each Epic. As a user. I can register for the application by entering my email. password. and conrming my password As a user. I will receive a conrmation email once I have registered tor the application As a user. I can register for the application through Faoebo-oic As a user. I can upload a prole photo and add my name to my account As a user. I can log into the application by entering my m u- 'EI'I'IIII and password As a user. I can log into the application through Facehoolr. if I previously registered with it As a user. I can reset my password if I have forgotten my password Registration As a user. I can yiew my personal information As a user. I can edit my prole photo HY Account As a user. I can edit my emaiL I will receive a conrmation email to my new email address. As a user. I can Iogout of the application from my account \f