Overview/Goal:
I created a user story issue type using Jira and authored the following user story and acceptance criteria to turn gathered requirements into functional tasks. Turning requirements into user stories, authoring acceptance criteria, and collaborating within an agile or scrum team to manage the product backlog and sprint backlog are frequent responsibilities for me as a Business Analyst. This example serves to highlight my skill at authoring user stories, acceptance criteria, and utilizing Jira.
While creating this user story in Jira, I also attached a mock-up visual of the login page to the issue to aid the team in visualizing the goal of the user story. The mock-up was created by Darlene Bachoo as a UI concept for the company Starbucks.’
*At the bottom of this post, I have attached the mock-up visual and a screenshot of my user story example within Jira.
Tools Used: Jira
My User Story Example:
*Please note that this is just an example for the company Starbucks, I am not affiliated with Starbucks nor do I work with them. This example is strictly for demonstrative purposes*
As an End-User, I want to be able to login with my username and password so that I can successfully access my Starbucks Online Ordering Application account.
My Acceptance Criteria Example:
Scenario 1: End-User Login Successful
Given the End-User is on the login page, the system will display the following fields:
a. Username
b. Password
and includes a “Forgot Password?” option (See attached mock-up, Functionality for resetting password handled in {XYZ}).
2. The End-User enters a valid username and password and clicks the ‘Login’ button
3. Then the system logs the End-User into their account successfully.
Scenario 2: End-User Login Unsuccessful
Given the End-User is on the login page, the system will display the following fields:
a. Username
b. Password
and includes a “Forgot Password?” option (See attached mock-up, Functionality for resetting password handled in {XYZ}).
2. The End-User enters an invalid username and password and clicks the ‘Login’ button
3. Then the page will display an error message as “Login Failed, Invalid Username or Password.”
Scenario #3: End-User Can Reset Password
Given the End-User is on the login page, the system will display the following fields:
a. Username
b. Password
and includes a “Forgot Password?” option (See attached mock-up, Functionality for resetting password handled in {XYZ}).
2. End-User clicks on “Forgot Password?” and receives a Reset Password link to the email address inputted.
3. End-User follows the link and provides a new password
4. End-User clicks the ‘Reset’ button and the new password is updated within the system
5. End-User is brought back to the Login page
6. End-User enters their valid username and new password then clicks the ‘Login’ button
7. The system logs the End-User into their account successfully.
Mock-Up Visual of Login Page:
Screenshot of User Story + Acceptance Criteria Within Jira:
Comments