User Stories - tugosera/tralalero-tralala GitHub Wiki
๐งพ User Stories in Software Development โ Summary
โ Definition
A user story is a short, simple description of a feature or requirement from the perspective of an end user or customer. It is a key element of Agile development methodologies like Scrum or Kanban.
๐งฑ Typical Format
As a [type of user],
I want to [do something],
so that [achieve some value or goal].
Example:
As a registered user, I want to reset my password, so that I can regain access to my account if I forget it.
๐ฏ Purpose of User Stories
- Keep the focus on user needs and value
- Serve as a tool for communication between stakeholders and developers
- Enable flexible and iterative planning
- Provide a basis for time and effort estimation
- Help define acceptance criteria and guide testing
๐ Key Characteristics of a Good User Story
- Independent โ can be developed separately
- Negotiable โ open for discussion and refinement
- Valuable โ delivers value to users or customers
- Estimable โ can be estimated for planning
- Small โ small enough to be completed in a short iteration
- Testable โ has clear criteria for success
(Acronym: INVEST)
๐งช Acceptance Criteria
A user story often includes acceptance criteria, which define the conditions under which the story is considered complete.
Example:
- "Forgot password" link is visible on the login page
- A reset email is sent to the correct address
- User is redirected to login after resetting the password
๐ Use in Agile Workflow
- Written by product owners, business analysts, or team members
- Discussed during backlog refinement
- Estimated and prioritized
- Implemented during sprints/iterations
- Validated via tests against acceptance criteria
๐ง Summary
User stories help create a shared understanding between the team and stakeholders. They are not detailed specs but starting points for conversations that ensure the team builds what users really need.