Practices
User Story
A short, simple description of a feature from the user’s perspective.
Plain English explanation
A User Story describes what a user wants and why. It helps the team understand the purpose of the work.
Why it matters
User Stories keep the team focused on user value instead of just building features.
How it works
They are usually written in a simple format: 'As a user, I want X so that Y'. The team discusses and refines them before building.
Example
As a user, I want to reset my password so that I can access my account again.
Common myths
A User Story is not a detailed specification. It is a starting point for conversation.
Key points
- Focuses on user needs
- Encourages collaboration
- Keeps requirements simple
- Supports iterative delivery
Was this explanation helpful?
Learning note
This is a common Agile/Scrum-related term or practice included to help learners understand language often used around Scrum.
View related reference