User Story
A simple description of a feature from the end-user's perspective.
A user story is an informal, general explanation of a software feature written from the perspective of the end user or customer. Its purpose is to articulate how a software feature will provide value to the customer. User stories are a key component of agile software development frameworks like Scrum and Kanban. They follow a simple template: 'As a [type of user], I want [some goal] so that [some reason].' This format encourages focusing on the user's needs and the business value rather than technical implementation details. User stories are often written on index cards or sticky notes and are placeholders for conversation between the developers and the product owner.
graph LR
Center["User Story"]:::main
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 Explain Like I'm 5
Generated ELI5 content
🤓 Expert Deep Dive
Generated expert content
❓ Frequently Asked Questions
What is the format of a user story?
As a <role>, I want <feature> so that <benefit>.
Who writes user stories?
Typically, the Product Owner writes them, but anyone on the team can contribute.
What is Acceptance Criteria?
Conditions that a software product must satisfy to be accepted by a user, stakeholders, or a consuming system.