Suggest an editImprove this articleRefine the answer for “What is a user story?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)A **user story** is a short description of functionality through the user's eyes, explaining what they want to do and why. **Key point:** a user story describes what needs to be done from the user's point of view and helps the team build features that deliver real value.Shown above the full answer for quick recall.Answer (EN)Image**User Story** is a short description of functionality **through the user's eyes**, explaining *what they want to do and why*. It helps understand **the value of the task**, not just its technical part. --- ### Format The classic form of a user story: > "As a [type of user], I want [action], so that [goal / benefit]." Example: > "As a shopper, I want to save items to my favorites, so I can come back to them later." --- ### Why they are needed - make requirements clear without excessive documentation; - help the Product Owner focus on value rather than features; - serve as the basis for discussion, estimation, and testing (through **acceptance criteria**). --- ### Structure 1. **Description** - the story itself. 2. **Acceptance Criteria** - the conditions under which the task is considered done. 3. **Priority** - importance to the user. --- **Summary:** A user story describes *what needs to be done* from the user's point of view and helps the team build features that deliver real value.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.