User Story Templates
The three user story formats — standard, job story, and INVEST criteria — with acceptance criteria templates.
Syntax
design-and-specify
// Standard | Job Story | INVEST | Gherkin ACExample
design-and-specify
// STANDARD USER STORY FORMAT
As a [role],
I want to [action],
So that [benefit].
// Example:
As a registered user,
I want to reset my password via email,
So that I can regain access if I forget my credentials.
// JOB STORY FORMAT (situation-driven)
When I [situation],
I want to [motivation],
So I can [outcome].
// Example:
When I'm trying to log in and can't remember my password,
I want to get a reset link without contacting support,
So I can get back into my account immediately.
// INVEST CRITERIA (good story checklist)
// I — Independent (can be built without depending on another story)
// N — Negotiable (details can be discussed)
// V — Valuable (delivers user/business value)
// E — Estimable (team can size it)
// S — Small (fits in one sprint)
// T — Testable (has clear acceptance criteria)
// ACCEPTANCE CRITERIA (Gherkin format)
Scenario: Successful password reset
Given: the user is on the login page
When: they click "Forgot password" and enter their email
Then: a reset link is sent within 60 seconds
And: the link expires after 24 hours