User Story
/ˈjuːzɚ ˈstɔːɹi/ · Noun · Development · Origin: 1998
Definitions
A short description of a feature told from the perspective of the person who wants it, conventionally phrased as 'As a [role], I want [capability], so that [benefit]'. The format's value lies almost entirely in the final clause, which forces the author to state the purpose and often reveals that the requested implementation is not the only way to deliver it. User stories were introduced in Extreme Programming as deliberately lightweight placeholders, intended as a promise to hold a conversation rather than as a specification to be handed over. They are commonly misused as exactly the specification they were meant to replace, producing pages of templated text that convey less than a paragraph of plain description, and they fit poorly for technical work with no meaningful end-user role.
In plain English: A one-sentence description of what someone wants a piece of software to do, written in everyday language instead of technical jargon. It keeps the team focused on real people's needs, not just features for features' sake.
Example: "As a returning customer, I want to see my previous orders so that I can quickly reorder items I liked."