user-story-fundamentals

Use the format "As a [specific user type], I want [goal], so that [benefit]". Make the persona specific (e.g., "returning customer" not "user"), focus the goal on user outcomes rather than implementation, and always include the "so that" clause explaining the value.

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. It is a quality checklist ensuring each story can be built separately, delivers real value, fits within a sprint, and has clear acceptance criteria for verification.

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

Acceptance criteria are story-specific, testable conditions unique to each story, 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 equals Reach times Impact times Confidence divided by Effort. Estimate how many users are affected, the impact level (3 for massive to 0.25 for minimal), your confidence percentage, and person-months of effort. Higher scores indicate higher priority.

Avoid user stories for purely technical tasks with no direct user value, such as "create database table". Also avoid them when the story prescribes a solution ("I want a dropdown menu") instead of describing a user goal open to negotiation.