What is the primary purpose of a user story?

• A. To document technical requirements.
• B. To articulate how a piece of work delivers value back to the customer.
• C. To outline all functionality of a software product.
• D. To record issues encountered during software testing.

Answer: (B)

The primary purpose of a user story is to articulate how a piece of work delivers value back to the customer. User stories are designed to capture the needs and perspectives of end users in a simple and effective way, often following the format of “As a [type of user], I want [an action] so that [a benefit].” This structure helps teams focus on the outcome and value that a feature or requirement provides rather than just its functionality or technical specifications. By centering the discussion around the value to the customer, teams can prioritize work that enhances user experience and meets customer needs, ultimately leading to more successful products.

In contrast, documenting technical requirements tends to focus on specifics that may not be directly tied to user needs. Outlining all functionality of a software product is broader and may miss the nuanced benefits to users. Recording issues encountered during software testing is a different context entirely, as it deals with quality assurance rather than user value.