What is the primary purpose of a user story in Agile development?

• A. To document every technical detail for developers
• B. To describe a feature from the user's perspective and guide development
• C. To replace acceptance criteria
• D. To estimate budgets

Answer: (B)

A user story expresses a feature in terms of what the user needs and why it matters, using the user's perspective to guide development. The main aim is to describe a feature so the team understands the value and the desired outcome, which helps with prioritization, conversation, and delivering usable increments that can adapt to feedback. It isn’t about capturing every technical detail for developers, and acceptance criteria aren’t a replacement for the story itself—though they help define what “done” looks like. It also isn’t a tool for budgeting estimates.