Which statement best describes the difference between functional and non-functional user stories?

• A. Functional stories describe indirect benefits
• B. Non-functional stories describe new user features
• C. Functional stories add functionality end users experience directly
• D. Non-functional stories require no stakeholders

Answer: (C)

Functional stories describe features that deliver direct capabilities the user can interact with. They specify what the user can do in the product, such as adding an item to a cart, searching for a product, or generating a report. Non-functional stories, on the other hand, focus on how the system operates or the quality attributes it must meet—things like performance, security, accessibility, reliability, and maintainability. They aren’t about new user-visible features, but about constraints and standards the product must satisfy.

The statement that best fits this distinction is that functional stories add functionality end users experience directly. Those stories capture the tangible features a user uses day to day.

Why the other ideas don’t fit: functional stories aren’t about indirect benefits—direct user-facing functionality is the hallmark. Non-functional stories aren’t about new features for users; they describe quality and constraints instead. And non-functional stories still involve stakeholders to define acceptable levels or criteria; they aren’t requirements that somehow don’t need anyone to decide them.