user story

A short description of a feature requirement written from the user's perspective in agile software development.

3 articlesLast mentioned

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.

This entry is based on AIPOST articles and widely known facts. If something is wrong, please send us a correction request.

Articles covering this entry

  • Levi Strauss Cuts App Delivery From 9 Months to 2.5 With GitHub Copilot AgentsAI in Practice ·

    The current-state map showed four stages: Plan (prioritize, write user stories, break them down, size and assess dependencies), Build (write code and unit tests…

    Read article
  • Example Mapping Plus TDD Lifts AI Agent Code Correctness From 27% to 94%AI in Practice ·

    A collaborative modeling technique created by Matt Wynne, in which a team breaks a user story down into rules and concrete examples on sticky notes.

    Read article
  • Claude Code Friction Shapes a Server-Run Coding AgentAI in Practice ·

    The voice assistant did more than transcribe the request: it created a card with a user story, requirements and test criteria, then opened it for review.

    Read article

Found a mistake or missing an entry?

Wiki entries are based on AIPOST articles and widely known facts. If an entry is wrong, send us a correction request and we will check and fix it. Names from new articles are added to the wiki after the article is published.