User story
A user story is a concise requirement describing a desired software capability or outcome from the perspective of a user or stakeholder.
BDD in Action, Second Edition
A user story is a concise requirement describing a capability from the perspective of a user or other stakeholder.
- How it is used
- Organizes manageable slices of a feature for iteration planning and earlier stakeholder feedback.
- How deep it goes
- Defines stories, contrasts them with features, and develops initial criteria through examples without treating the story as a complete specification.
- Examples
- Illustrates story slicing with direct and alternative train routes, and story refinement with secure-password registration.
- What you can do after
- Practice/perform feature slicing, then discuss business rules and refine acceptance criteria before implementation.
Read how BDD in Action, Second Edition explains user story →
Coding with AI
A user story is a concise requirement describing a software capability from the perspective of a user or other stakeholder.
- How it is used
- Uses stories to bring the user’s perspective into design and guide development.
- How deep it goes
- Walks through prompting, generated stories, and review, then uses stories as an intermediate step toward application stubs.
- Examples
- Uses a certification practice-test application with stories for registration, test taking, grading, and progress tracking.
- What you can do after
- Apply it via ChatGPT to draft and review stories, then use them to request feature-organized class and method stubs.
Software Testing with Generative AI
A concise requirement statement describing a capability from a user's perspective and the value it provides.
- How it is used
- Frames capabilities and acceptance criteria for TDD loops, API testing, and retrieval-based recommendations for test risks.
- How deep it goes
- Defines role, capability, value, and acceptance criteria through worked examples, then stops short of formal requirements theory.
- Examples
- Uses timesheet tracking, booking cancellation, and branding-update API stories with payload schemas, status codes, authentication, and validation rules.
- What you can do after
- Apply it via TDD loops or retrieval prompts to derive concrete tests and risks from capabilities and acceptance criteria.
Read how Software Testing with Generative AI explains user story →
Test Driven: Practical TDD and Acceptance TDD for Java Developers
A user story is a concise description of a software requirement from the perspective of a user or customer.
- How it is used
- Expresses software requirements as lightweight stories that support acceptance test-driven development.
- How deep it goes
- Defines the story’s purpose and illustrates its scope, while leaving detailed requirements-management and planning treatment aside.
- Examples
- Uses support-call history, preventing multiple application instances, and HTTP proxy authentication as story examples.
- What you can do after
- Evaluate a requirement by identifying who, what, and why, then communicate its value without prescribing implementation.
Read how Test Driven: Practical TDD and Acceptance TDD for Java Developers explains user story →
Delivering Machine Learning Projects: From design to deployment
A user story is a concise description of a system capability from the perspective of a person or group affected by or using the system.
- How it is used
- Uses stakeholder perspectives during pre-project validation to test whether a proposed system can achieve business impact.
- How deep it goes
- Develops requirements, acceptance criteria, harms, corner cases, stakeholder situations, and model-data implications, while deferring detailed elaboration until execution.
- Examples
- Uses first use, normal use, and discontinuation scenarios for sponsors, users, customers, and affected persons.
- What you can do after
- Evaluate implementation viability and specify stakeholder needs, model behavior, data requirements, acceptance criteria, and risks.
Read how Delivering Machine Learning Projects: From design to deployment explains user story →
Effective Behavior-Driven Development
A user story is a concise requirement description expressing desired software behavior from a user's perspective.
- How it is used
- Frames a valuable increment for collaborative BDD discovery, then supports planning and delivery after prioritization.
- How deep it goes
- Defines stories as conversation placeholders, gives a delivery-address example and candidate rule, and defers detailed requirements gathering to discovery.
- Examples
- Uses changing an uncollected order’s delivery address and blocklisting to illustrate candidate rules and feature organization.
- What you can do after
- Understand how to use a story as a discussion prompt and planning aid, not as a complete requirement.
Read how Effective Behavior-Driven Development explains user story →
Build Financial Software with Generative AI (From Scratch)
A user story is a concise Agile requirement statement describing a capability from a user's perspective and its intended benefit.
- How it is used
- Breaks epics and projects into value-focused capabilities for sprint planning and communication with developers, analysts, QA, and stakeholders.
- How deep it goes
- Defines the role-want-benefit format, pairs stories with acceptance criteria, and stops short of teaching Agile methodology comprehensively.
- Examples
- Uses ACH exception viewing and transaction search to connect operator capabilities with payment-processing and customer-support outcomes.
- What you can do after
- Apply it via Agile sprint planning to write focused requirements, identify acceptance criteria, and organize implementation work.
Read how Build Financial Software with Generative AI (From Scratch) explains user story →
Developer Experience on Kubernetes
A concise requirements description expressing a software capability from a user's or stakeholder's perspective.
- How it is used
- Uses concise stakeholder-centered requirements to plan and prioritize changes entering the development inner loop.
- How deep it goes
- Defines the template, INVEST qualities, and acceptance-criteria workflow but defers detailed implementation discussion until development begins.
- Examples
- Uses appointment category selection and a Cardiology visibility scenario to connect a story with testable behavior.
- What you can do after
- Apply it via a role-feature-benefit template and acceptance criteria to plan, prioritize, and verify a capability.
Read how Developer Experience on Kubernetes explains user story →
Spec-Driven Development
A user story is a concise requirement expressed from the perspective of a person who needs a capability and its purpose.
- How it is used
- Uses structured dialogue to carry a user’s purpose into requirements and address intent lost between product owners and developers.
- How deep it goes
- Develops persona, need, and purpose into verifiable acceptance criteria, emphasizing conversation over Gherkin syntax.
- Examples
- Uses password-reset scenarios involving session invalidation and time-limited reset links.
- What you can do after
- Apply it to state a persona’s need and purpose, then clarify intent with concrete, verifiable acceptance criteria.
Also covered in
- Collaborative Software Design: How to facilitate domain modeling decisions
- Statistics Every Programmer Needs
What to know first
- stakeholderA stakeholder is a person, group, or organization with an interest in, influence over, or potential to be affected by a system, project, decision, or its outcomes.
- requirementsA requirement is a stated need, capability, quality, condition, or constraint that a system, product, solution, or project is expected to satisfy.
- capabilityA capability is an ability or defined authority that enables an entity to perform an action, provide a function, or achieve an outcome.
- language modelA language model is a computational model that represents patterns in linguistic sequences to assign probabilities, predict, generate, or evaluate language.
Related concepts
- requirementscontrasts with · A requirement is a stated need, capability, quality, condition, or constraint that a system, product, solution, or project is expected to satisfy.
- acceptance criteriahas part · Acceptance criteria are verifiable conditions that a requirement, feature, or deliverable must satisfy to be considered acceptable or complete.
- Example Mappingused by · Example Mapping is a collaborative technique for clarifying a requirement by organizing its rules, examples, and open questions.
- acceptance testingused by · Acceptance testing evaluates whether a system satisfies specified user, business, or stakeholder requirements and acceptance criteria.
- backlog refinement meetingproduced by · Backlog refinement is a collaborative activity for clarifying, detailing, estimating, splitting, and ordering items in a product backlog.
Questions about user story
What is user story?
A user story is a concise requirement describing a desired software capability or outcome from the perspective of a user or stakeholder.
Which Manning books explain user story?
BDD in Action, Second Edition, Coding with AI, Software Testing with Generative AI, Test Driven: Practical TDD and Acceptance TDD for Java Developers, Delivering Machine Learning Projects: From design to deployment, Effective Behavior-Driven Development, Build Financial Software with Generative AI (From Scratch), Developer Experience on Kubernetes and 1 more.
What should I know before learning user story?
Manning books that teach user story usually introduce stakeholder, requirements, capability and language model first.
What is the difference between user story and requirements?
A user story is a concise requirement describing a desired software capability or outcome from the perspective of a user or stakeholder. A requirement is a stated need, capability, quality, condition, or constraint that a system, product, solution, or project is expected to satisfy.
What are the parts of user story?
User story includes acceptance criteria.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.








