User Story Examples: Complete Guide & Template for Business Analysts

A user story is an informal, general explanation of a software feature written from the perspective of the end user or customer. In Agile and Scrum frameworks, user stories serve as the primary building blocks for project backlogs, turning complex business requirements into clear, user-focused technical tasks.

What is a User Story in Agile?

A user story articulates who needs a feature, what capability they require, and why it adds value to their overall experience. Unlike traditional, lengthy requirement specifications, a user story shifts the focus from writing about requirements to discussing them with developers and stakeholders.

Standard User Story Template:

As a <type of user>,

I want to <perform some action>,

So that <achieve a business value or goal>.

Core Components: The 3 Cs of User Stories

Created by Ron Jeffries, the 3 Cs framework defines the lifecycle of every effective user story:

1. Card: A written representation of the user story (traditionally an index card or a Jira/Confluence ticket) capturing the basic requirement template.

2. Conversation: Ongoing dialogue between the Product Owner, Business Analyst, UX Designers, and Developers to clarify details, edge cases, and technical assumptions.

3. Confirmation: The explicit Acceptance Criteria used to verify that the story has been implemented correctly and meets the definition of done (DoD).

Real-World User Story Examples across Industries

Below are real-time user story examples with corresponding acceptance criteria across common software domains:

1. E-Commerce Domain: Wishlist Feature

• User Story:

  • As an online shopper,

  • I want to save items to a personal wishlist,

  • So that I can easily review and purchase them later without searching again.

• Acceptance Criteria (Given-When-Then Format):

  • Scenario 1: Adding an item to wishlist while logged in.

    • Given the user is logged into their account,

    • When they click the heart icon on a product card,

    • Then the product is added to their wishlist and the heart turns red.

  • Scenario 2: Guest user attempts to add an item.

    • Given a guest user clicks the heart icon on a product,

    • When the action is triggered,

    • Then prompt a modal requesting the user to log in or register.

2. Banking & Fintech Domain: Mobile Fund Transfer

• User Story:

  • As a mobile banking customer,

  • I want to transfer money instantly via phone number,

  • So that I can send funds quickly without entering full bank account numbers.

• Acceptance Criteria:

  • Rule 1: The transfer amount cannot exceed the daily peer-to-peer limit of $1,000.

  • Rule 2: System must send a 6-digit OTP to the user’s registered phone number before finalizing payment.

  • Rule 3: Display confirmation screen with Transaction ID and updated balance upon completion.

3. Healthcare Domain: Patient Appointment Scheduling

• User Story:

  • As a patient,

  • I want to view available doctor time slots online,

  • So that I can book an appointment that fits my schedule.

• Acceptance Criteria:

  • Rule 1: Calendar must only display available slots in real time.

  • Rule 2: Automatically send an email and SMS confirmation once a slot is reserved.

  • Rule 3: Allow cancellation or rescheduling up to 24 hours prior to the appointment.

How to Write User Stories Using the INVEST Quality Framework

To ensure user stories are ready for sprint refinement, Business Analysts evaluate them using the INVEST quality criteria:

Quality Indicator	Meaning	Explanation & BA Best Practice
I – Independent	Can be delivered separately	Avoid tight coupling with other stories so it can be prioritized freely.
N – Negotiable	Open to discussion	Leaves room for technical input during team backlog refinement.
V – Valuable	Delivers clear user value	Must provide tangible value to end users or business operations.
E – Estimable	Easy to size	Development team has enough clarity to estimate effort in Story Points.
S – Small	Fits in a single sprint	Can be designed, built, and tested within a standard 2-week sprint cycle.
T – Testable	Clear acceptance criteria	Contains verifiable criteria so QA engineers can write pass/fail tests.

User Story Template

A typical user story follows this simple template:

This format helps keep the focus on the user’s needs and the value delivered.

 

User Story Example with Acceptance Criteria

Example 1: Website Search Functionality

• User Story: As a user, I want to search for products on the website so that I can quickly find items I am interested in.

• Acceptance Criteria:
  • Users can enter keywords in the search bar.
  • The system returns relevant product results.
  • Results include product name, price, and a brief description.
  • Results are displayed within 2 seconds.

Example 2: Registration Process

• User Story: As a new user, I want to create an account so that I can access member-only features.

• Acceptance Criteria:
  • Users can enter their name, email, and password.
  • The system sends a confirmation email.
  • Users must verify their email to activate the account.
  • The system displays a success message upon verification.

User Stories in Agile Examples

Agile methodologies emphasize iterative development and collaboration. Here are examples of user stories typically used in Agile:

Example 1: Task Management System

• User Story: As a project manager, I want to assign tasks to team members so that we can track work progress.

• Acceptance Criteria:
  • The system allows project managers to create tasks.
  • Tasks can be assigned to team members.
  • Team members receive notifications when assigned a task.
  • The system tracks task status (e.g., pending, in progress, completed).

Example 2: E-Commerce Platform

• User Story: As a customer, I want to view my order history so that I can reorder products easily.

• Acceptance Criteria:
  • Users can access their order history from their account dashboard.
  • Order history includes order date, products, and total amount.
  • Users can reorder items directly from the order history.

User Story Example for Websites

Example 1: Blog Subscription

• User Story: As a reader, I want to subscribe to the blog so that I receive updates via email.

• Acceptance Criteria:
  • Users can enter their email address in the subscription form.
  • The system sends a confirmation email.
  • Users receive email notifications for new blog posts.

Example 2: Commenting System

• User Story: As a user, I want to leave comments on blog posts so that I can engage in discussions.

• Acceptance Criteria:
  • Users can submit comments on blog posts.
  • Comments are moderated before being published.
  • Users receive notifications if their comment is approved.

User Story Examples for Registration

Example 1: Basic Account Registration

• User Story: As a new user, I want to register for an account so that I can access exclusive content.

• Acceptance Criteria:
  • Users can enter necessary information (name, email, password).
  • The system validates the email address.
  • Users receive a confirmation email.
  • The system displays a registration success message.

Example 2: Social Media Registration

• User Story: As a user, I want to register using my social media account so that I can sign up quickly.

• Acceptance Criteria:
  • Users can register using Facebook, Google, or Twitter accounts.
  • The system fetches basic information (name, email) from the social media account.
  • Users can set a unique username.

User Story Examples for Mobile Apps

Example 1: Mobile Banking App

• User Story: As a bank customer, I want to check my account balance on my mobile app so that I can manage my finances on the go.

• Acceptance Criteria:
  • Users can log in using secure credentials.
  • The system displays the current account balance.
  • The balance is updated in real-time.

Example 2: Fitness Tracking App

• User Story: As a fitness enthusiast, I want to track my daily steps so that I can monitor my activity levels.

• Acceptance Criteria:
  • The app tracks and displays daily steps.
  • Users can set daily step goals.
  • The app sends notifications when goals are achieved.

User Story Examples for Login

Example 1: Standard Login

• User Story: As a returning user, I want to log in to my account so that I can access personalized features.

• Acceptance Criteria:
  • Users can enter their username and password.
  • The system validates credentials.
  • Users are redirected to their dashboard upon successful login.
  • The system displays an error message for invalid credentials.

Example 2: Two-Factor Authentication

• User Story: As a security-conscious user, I want to enable two-factor authentication so that my account is more secure.

• Acceptance Criteria:
  • Users can enable two-factor authentication from their account settings.
  • The system sends a verification code to the user’s phone.
  • Users must enter the verification code to complete the login process.

Conclusion

User stories are a vital tool in Agile development, helping teams understand and prioritize user needs. By using a standard template and incorporating acceptance criteria, teams can ensure that user stories are clear and actionable. Whether for websites, mobile apps, or specific features like registration and login, well-crafted user stories guide the development process and lead to better user experiences.

Related Articles :

1. Understanding Agile User Stories: A Comprehensive Guide
2. Agile Methodology Scrum Master: The Architect of Agile Success
3. Data Analyst vs Business Analyst: Understanding the Roles and Career Prospects
4. How to create Activity Diagram: A Comprehensive Guide

Frequently Asked Questions (FAQ)

What is the difference between an Epic and a User Story?

An Epic is a large body of work (e.g., Customer Onboarding System) that cannot be completed within a single sprint. Epics are broken down into multiple smaller User Stories (e.g., User Registration, Email Verification, Password Reset).

Who writes user stories in an Agile project?

While the Product Owner (PO) owns the backlog, Business Analysts (BAs) frequently write, refine, and maintain user stories, working closely with developers and QA engineers during sprint refinement.

What is Acceptance Criteria in a user story?

Acceptance Criteria are the specific conditions that a software product must satisfy to be accepted by the Product Owner or client. They define the boundaries of the story and serve as test cases for QA teams.