What best defines a feature?

• A. Capabilities that indirectly support user goals
• B. Behaviors of the system that directly fulfill some user need
• C. Nonfunctional attributes only
• D. A document describing user journeys

Answer: (B)

A feature is a piece of functionality that delivers observable value to a user by describing the system behavior that directly fulfills a user need. In practice, a feature represents what the user can do with the system (like a searchable product catalog, a checkout flow, or a report) and is small enough to be planned and delivered within a Program Increment. It’s something you can test against with acceptance criteria and demonstrate to stakeholders.

This makes the option describing system behaviors that directly fulfill a user need the best fit. The other ideas don’t align with how features are used: capabilities are larger, cross-cutting behaviors that span multiple teams; nonfunctional attributes are quality requirements like performance or security rather than the visible functionality delivered to users; and a document describing user journeys is an artifact, not the actual user-facing functionality.