user-story-fundamentals

Write user stories in the format "As a [specific user type], I want [goal], so that [benefit]." Use a specific persona rather than a generic user, focus the goal on user outcomes instead of implementation, and always include the "so that" clause explaining the value.

INVEST is a quality checklist: Independent, Negotiable, Valuable, Estimable, Small, and Testable. A story should be deliverable on its own, open to discussion, valuable to users, estimable by the team, small enough for one sprint, and verifiable through acceptance criteria.

Split large stories by workflow steps, user type, CRUD operations, data variations, or acceptance criteria. For example, split "user can manage contacts" into create, view, edit, and delete stories that each fit within a single sprint.

Acceptance criteria are story-specific, testable conditions defining when that story is complete, such as "reset link expires after 24 hours." Definition of done is a universal quality checklist applied to all stories, like code review and tests written.

RICE scores stories as (Reach × Impact × Confidence) / Effort. Estimate how many users are affected, rate impact from 0.25 to 3, set confidence as a percentage, and divide by person-months of effort. Higher scores indicate higher priority.

Avoid user stories for purely technical tasks with no user value, such as "create database table." Also avoid them when the story prescribes a solution ("I want a dropdown menu") instead of a user goal, or when the item is too vague to be actionable.