User story

Roles that need it

• Product Owner
• Product Owner (Banking)
• Business Analyst
• Business Analyst (Banking)

Skills it belongs to

• Agile delivery (Scrum, Kanban)
• Requirements gathering and documentation
• Project tools (Jira, Asana)

Related concepts

• Acceptance criteriaAcceptance criteria are the specific, testable conditions a feature or user story must meet to be accepted, often written as "Given [context], when [action], then [result]". They guide development and form the basis of test cases and UAT.
• Product backlogThe product backlog is the ordered list of everything that might be built or changed in a product, such as user stories, defects and technical work. The product owner keeps it prioritised, and items near the top are refined until they are ready for a sprint.
• ScrumScrum is an agile framework in which a small team delivers a usable increment in fixed iterations called sprints, of one month or less. It has three accountabilities (product owner, Scrum Master, developers), five events and three artefacts: product backlog, sprint backlog and increment.
• RequirementsRequirements are documented statements of what a solution must do or achieve. Business requirements describe the need, functional requirements describe system behaviour, and non-functional requirements set qualities such as performance or security. Each should be clear, testable and traceable.

Sources

• The Scrum Guide, Schwaber and Sutherland (external site) accessed 31 Oct 2026
• Manifesto for Agile Software Development (external site) accessed 31 Oct 2026

Updated 31 Oct 2026.