Open hassanshamim opened 7 years ago
About: https://www.mountaingoatsoftware.com/agile/user-stories Another: http://www.agilemodeling.com/artifacts/userStory.htm
Generally they follow the format
Given <scenario>
or As a <type of user>
In order to <desired outcome/objective>
When I <do an action>
. I.e. visit a page or click a link
Then <observable outcome>
ex. 'I should see a map', 'I should see 'facility created' on my screen'
You'll generally want to cover the different starting scenarios first (i.e. a new user, a logged in user, offline user) Then you can cover the happy paths (everything works as expected) and then the not-so-happy-paths (website is down, address is invalid, etc.)
I don't need these to be super thorough, just want the functionality of the website documented so I can implement. Also it's good because it makes you think about these types of things before the user experiences them first hand.
Given I was just in an accident and need to find an emergency room right away When I I load nomademergency.com Then it immediately geolocates me and offers up options nearby.
Given that I am a French-speaker who needs to have a check-up in Thailand When I search locations Then I am able to see which hospitals/clinics have doctors which speak French
Given I want to visit my friend in the hospital When I load your nomademergency.com Then I am able to search by hospital name and see the address & get directions via google maps
Given I am a good samaritan Who wants to add information / locations to nomademergency.com When I click on a location on the map / enter an address Then I am able to submit more information about that location with ease (by mostly checking boxes.)
Get Amna example Users Stories.