User Story
A user story is a short description of a software feature written from the perspective of an end user, expressing a desired capability and its business value.
“A user or business requirement consisting of one sentence expressed in the everyday or business language which is capturing the functionality a user needs, the reason behind it, any non-functional criteria, and also including acceptance criteria.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is User Story?
User stories help Agile teams understand user needs and serve as the basis for development, testing, and acceptance criteria.
User focused: Describes value from the user's perspective.
Simple format: Encourages conversation rather than detailed specifications.
Acceptance criteria: Define conditions for successful implementation.
Real World Example
A healthcare scheduling team is building a feature that lets patients book follow-up appointments after a consultation.
Developers, testers, clinicians, and product owners may all believe they understand the request while imagining different rules. User story gives the team a shared way to confirm intent.
The tester turns clinical and business expectations into concrete examples, such as eligible appointment windows, unavailable doctors, and messages shown when no slot is open.
The team prevents late rework because User story makes expected behavior testable before the feature is treated as finished.
Practice Questions
Question 1
Which statement BEST describes User story in the context of ISTQB terminology?
Question 2
A tester needs to explain User story to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned User Story. Test your understanding with topic-specific questions in our Mock Exams.