CAPM Practice: Determine how project methodologies influence business analysis processes

User stories (card + conversation + confirmation) are intentionally brief — the conversation they spark matters more than the text. Traditional requirements specifications aim for self-contained completeness, minimizing the need for clarifying conversation downstream.

**Why not A:** This answer reverses the typical usage. Both specifications and user stories can be shared with various stakeholders, including customers. The key distinction is not about audience but about format and level of detail. Specifications tend to be formal, comprehensive documents, while user stories are brief, conversational descriptions of desired functionality.

**Why not B:** User stories are intentionally shorter and less detailed than traditional specifications, not longer. A user story typically follows a simple template ("As a [role], I want [feature], so that [benefit]") and fits on an index card, whereas a traditional specification can span many pages with exhaustive detail on requirements, constraints, and acceptance criteria.

**Why not D:** There are significant differences between agile user stories and traditional specifications. User stories are brief, informal, and focus on user value, while traditional specifications are formal, detailed documents that comprehensively describe system requirements. Claiming no difference ignores fundamental distinctions in format, purpose, and level of detail.