A user story is a short description of a feature requirement written from the user's perspective in agile software development. It commonly follows the form 'As a [type of user], I want [goal], so that [benefit].'
User stories were introduced in extreme programming (XP) by Kent Beck and others in the late 1990s and are widely used as product backlog items in Scrum. Rather than a detailed specification, a story is treated as a placeholder for a conversation, with completion conditions written separately as acceptance criteria. The INVEST criteria (independent, negotiable, valuable, estimable, small, testable) are often cited as qualities of a good user story.