Glossary
What is a user story? Structure and examples
A user story describes a benefit from the user's point of view rather than a task. Structure, two examples, INVEST, and how it differs from a task and an epic.
A user story describes a requirement from the point of view of whoever gets the benefit — not as a step of work but as an outcome. It is deliberately short: a reminder of a conversation, not a specification.
The form
As a <role> I want <goal> so that <benefit>. The third part matters most and gets dropped most often — without it you have written down a feature, and nobody can check whether a different solution would serve the purpose better.
Two examples
As a project lead I want to see who is over-committed this week so that I can move work before somebody burns out.
As a developer I want my commit to link the card itself so that I do not have to write anything up after hours.
INVEST
A usable story is Independent, Negotiable (not a finished solution), Valuable, Estimable, Small enough for one iteration, and Testable. What the last one is measured against lives in the acceptance criteria.
Story, task, epic
A task is a step of work ("install the certificate"), a story is a benefit ("as a customer I want to pay with Apple Pay"), an epic is the bracket above ("payment in checkout"). The story is what gets estimated, usually in story points, and it lives in the backlog.
In Zuuna
A story is a card with a type, an epic, story points and a checklist for the acceptance criteria — the same card that later shows up in the sprint and the burndown.
FAQ
Do I have to use the "As a … I want … so that …" form?
No. The form is an aid, not a law. All it enforces is naming the role and the benefit — if your team does that without a template, the template is redundant.
How small should a user story be?
Small enough to finish within one iteration. Anything that routinely does not finish is too big — split it rather than lengthening the iteration.
Is every card a user story?
No. Bug fixes, technical work and maintenance have no user benefit in the story sense. Forcing them into the template produces sentences like "as a developer I want to migrate the database", which helps nobody.