User Stories
Short descriptions of features from the user's perspective used to capture requirements.
Also known as: User Story, Agile User Stories
Category: Techniques
Tags: agile, requirements, user-centered, planning, communication, product-management
Explanation
User stories are a lightweight technique for capturing product requirements from the end user's perspective. Popularized by Extreme Programming (XP) and widely used in Scrum, they focus on the value delivered rather than technical specifications.
The classic format:
As a [type of user],
I want [some goal/desire],
So that [benefit/value].
Example: 'As a returning customer, I want to save my payment details, so that I can checkout faster on future purchases.'
Key characteristics:
1. User-focused - Written from the perspective of someone using the system
2. Independent - Can be developed and delivered separately
3. Negotiable - Details are discussed, not prescribed upfront
4. Valuable - Delivers clear benefit to users or business
5. Estimable - Team can roughly estimate the effort
6. Small - Fits within a single sprint
7. Testable - Clear criteria for success
(This is the INVEST criteria by Bill Wake)
Components of a complete user story:
- Card: The written story itself (brief)
- Conversation: Discussion to clarify details
- Confirmation: Acceptance criteria defining 'done'
Acceptance criteria example:
- Given I am logged in with saved payment details
- When I click 'Express Checkout'
- Then my saved card is pre-selected
- And I can complete purchase with one click
User stories differ from traditional requirements:
- Focus on 'why' not just 'what'
- Encourage conversation over documentation
- Delay detailed specifications until needed
- Keep scope small and deliverable
User stories can be organized into Epics (large stories spanning multiple sprints) and broken down into tasks during sprint planning.
Related Concepts
← Back to all concepts