What characteristic describes a User Story?

A User Story is characterized by a brief description of the desired outcome. It captures the essence of what the user wants to achieve in a simple and clear format, typically structured to reflect the perspective of the end user. This approach allows team members to understand the user's needs without getting bogged down in extensive detail or technical jargon.

The fundamental goal of a User Story is to articulate the requirement in a manner that facilitates understanding and fosters collaboration among team members. By focusing on the outcome rather than a rigid specification, User Stories empower teams to engage in discussions that can lead to more innovative and effective solutions. This format encourages developers and stakeholders to explore the underlying needs and to prioritize work in a way that delivers maximum value to the user.

Options that suggest a detailed technical specification, lengthy planning document, or direct instructions for developers do not align with the fundamental purpose of a User Story, which is meant to remain agile and flexible, adaptable to changes as they arise throughout the development process.