Lab: Create User Stories for Login and Logout for a Website
Estimated time: 30 minutes
Learning objectives
After completing this lab, you will be able to:
- Write user stories to capture the requirements of a functionality.
- Write the acceptance criteria for a user story.
Welcome to the lab on creating user stories!
Exercise: Create user stories for login and logout for a website
QuickShop is an e-commerce platform for buying and selling products online. To provide a seamless shopping experience, the platform requires users to create an account. The account enables features like order tracking and personalized recommendations.
Your task is to create user stories that capture the requirements for the QuickShop website's login and logout functionalities. Quantify and validate your user story using acceptance criteria.
Software used for this lab
We recommend using Microsoft's ‘Word for the Web,’ one of the most used online word-processing software applications worldwide. To access this application, you will need to sign up for a free Microsoft 365 account. For instructions on how to sign up for a free account, click here. For step-by-step guidance on getting started with Word Online, click here.
You can alternatively use any word-processing software or text editor for this exercise.
Template to use
If you're using Microsoft Word, you can download the Create User Stories for login and logout template.docx. Right-click the link to download the file. You can use this template to perform the tasks outlined in the lab.
If you're using any other word-processing software, you can download the PDF format. Right-click the link to open the PDF in a new tab.
Let's begin.
Instructions
Task 1: Identify user types
Think about the different types of users who will interact with your website and how. Focus on interactions with the login and logout features. Record the user types in the space given in the template.
| User type 1 | Registered users |
| User type 2 | |
| User type 3 | |
| User type 4 |
Hint
Common user types include:
- Registered users
- Guest users
- Admins (if applicable)
Task 2: Identify the login and logout scenarios for each user type
For each user type, think of what they might expect or need while logging in or logging out.
Login scenarios
List the scenarios that may occur while the user logs in the table provided in the template.
| User Type | Login scenarios |
|---|---|
| Registered users |
• Scenario 1 • Scenario 2 • Scenario 3 |
| User type 2 | |
| User type 3 |
Hint
Consider scenarios such as:
- Successful login
- Error handling for incorrect credentials
- “Remember me” functionality
- Password reset
- Account lockout
Logout scenarios
Similarly, list the scenarios that may occur while the user logs out in the table provided in the template.
| User Type | Logout scenarios |
|---|---|
| Registered users |
• Scenario 1 • Scenario 2 • Scenario 3 |
| User type 2 | |
| User type 3 |
Hint
Consider scenarios such as:
- Successful logout
- Confirmation message
- Redirect after logout
- Option to log out from all devices
Task 3: Create user stories
User stories are short, simple descriptions of a feature told from the end user's perspective. They typically follow the format:
As a [type of user], I want [an action] so that [a benefit].
Example: “As a registered user, I want to log in so that I can access my account and view my orders.”
Where:
- Type of user = Registered user
- Action = To log in
- Benefit = I can access my account and view my orders
While writing user stories, use plain language. Avoid technical jargon that might confuse non-technical users.
User stories for login:
Write the user stories for the following login scenarios for registered users in the template. The user story for a successful login is given below.
| User Type | User Story ID | User Story Scenario | User Story | Acceptance Criteria | Rationale |
|---|---|---|---|---|---|
| Registered user | US1 | Successful login | As a registered user, I want to log in with my email and password so that I can access my account and view my orders. | ||
| Registered user | US2 | Incorrect credentials | |||
| Registered user | US3 | Password reset |
User stories for logout:
Write the user stories for the following logout scenarios for registered users.
| User Type | User Story ID | User Story Scenario | User Story | Acceptance Criteria | Rationale |
|---|---|---|---|---|---|
| Registered user | US4 | Successful logout | |||
| Registered user | US5 | Confirm logout |
Task 4: Review and refine user stories
Ensure your user stories are clear and concise. While reviewing the user stories, consider potential challenges users might face during login and logout. Think about their expectations regarding the functionality.
Hint
For example, consider issues like forgotten passwords and account verification. Users may be concerned about how you ensure security during the login process. Think about what feedback users should receive after logging out and what visual cues and messages users will receive to confirm their actions.
Use the “INVEST” criteria:
- Independent
- Negotiable
- Valuable
- Estimable
- Small
- Testable
Here is an example of how each criterion can be applied to the user stories.
User story: As a registered user, I want to log in with my email and password so that I can access my account and view my orders.
INVEST analysis:
- Independent: This user story does not depend on other stories; it stands alone.
- Negotiable: The specific user interface (UI) elements for login can be discussed and modified as needed.
- Valuable: It provides value by allowing users to access their accounts.
- Estimable: Development time can be estimated based on complexity.
- Small: It focuses on one clear action—logging in.
- Testable: Acceptance criteria can be established to confirm functionality.
Task 5: Write the acceptance criteria for each user story
To validate your understanding and solution, create acceptance criteria.
For each user story, define acceptance criteria that must be met for the feature to be considered complete.
Example
For a successful login scenario, the acceptance criteria would be:
“Given valid credentials, when I click ‘Login,’ then I should be redirected to my dashboard.”
In the space provided in the table, write the acceptance criteria for the user stories you have created for both login and logout.
| User Type | User Story ID | User Story Scenario | User Story | Acceptance Criteria | Rationale |
|---|---|---|---|---|---|
| Registered user | US1 | Successful login | As a registered user, I want to log in with my email and password so that I can access my account and view my orders. | Given valid credentials, when I click ‘Login,’ I should be redirected to my account dashboard. |
Task 6: Present your rationale
When presenting user stories to stakeholders, it's essential to convey the thought process and rationale behind each story clearly. This ensures that stakeholders understand the value and purpose of each feature, which can help gain their approval.
Here is an example of the thought process and rationale for a user story related to successful login into the website.
User Story: As a registered user, I want to log in with my email and password so that I can access my account and view my orders.
Thought Process: The primary goal of this story is to provide users with a seamless entry point to their accounts. Given that the login feature is critical for accessing personalized services (like order tracking), it's essential to ensure that users can log in easily using their credentials.
Rationale: This user story adds significant value by enabling users to access their accounts, which is fundamental for any e-commerce platform. Ensuring a smooth login experience fosters user satisfaction and retention.
In the last column, explain your thought process and rationale behind each story.
| User Type | User Story ID | User Story Scenario | User Story | Acceptance Criteria | Rationale |
|---|---|---|---|---|---|
| Registered user | US1 | Successful login | As a registered user, I want to log in with my email and password so that I can access my account and view my orders. | Given valid credentials, when I click ‘Login,’ I should be redirected to my account dashboard. |
Thought Process: The primary goal of this story is to provide users with a seamless entry point to their accounts. Given that the login feature is critical for accessing personalized services (like order tracking), it's essential to ensure that users can log in easily using their credentials. Rationale: This user story adds significant value by enabling users to access their accounts, which is fundamental for any e-commerce platform. Ensuring a smooth login experience fosters user satisfaction and retention. |
Summary
Congratulations on completing the hands-on lab on creating user stories for login and logout for a website.
Here is an exemplar you can refer to for the solution. Right-click the link and open the PDF in a new tab. Please remember that the exemplar is just a point of view and not a definitive solution.