What is a User Story?

• A. Technical documentation of a software feature.
• B. A general explanation of a software feature from the end user's perspective.
• C. A detailed analysis of system performance by developers.
• D. A formal proposal for a new software system.

Answer: (B)

A User Story is fundamentally aimed at capturing a feature from the end user's perspective, describing what the user wants to accomplish and why it is valuable to them. This approach puts a focus on the user's needs and preferences, encouraging developers to understand and deliver solutions that enhance user experience.

By framing software features in terms of user stories, teams can prioritize development tasks based on the value they deliver to the user rather than solely on technical requirements. This method fosters better communication between technical and non-technical stakeholders and ensures that the development work is aligned with user expectations and outcomes.

In contrast, the other choices do not align with the User Story concept; they either pertain to documentation, analysis, or proposals that do not prioritize end-user perspective but rather focus on technical specifications or formalities.