User Story Template
A structured user story template with the standard "As a... I want... So that..." format, acceptance criteria, story points, and definition of done — designed for agile teams that value clarity in their backlog.
USER STORY — [Story ID]
Epic: [Epic Name] | Priority: [High / Medium / Low] | Points: [#]
1. User Story
As a [type of user, e.g., "returning customer"],
I want [action, e.g., "to reset my password via email"],
So that [benefit, e.g., "I can regain access to my account without contacting support"].
2. Acceptance Criteria
Given [precondition], When [action], Then [expected result]
• [AC 1, e.g., "Given the user clicks Forgot Password, When they enter a valid email, Then they receive a reset link within 2 minutes"]
• [AC 2, e.g., "Given the reset link is clicked, When the user enters a new password meeting requirements, Then the password is updated and they are logged in"]
• [AC 3, e.g., "Given the reset link is older than 24 hours, When clicked, Then it shows an expiration message with a new-request option"]
3. Technical Notes
• Dependencies: [APIs, services, or other stories this depends on]
• Edge cases: [Known edge cases to handle]
• Out of scope: [What this story explicitly does NOT cover]
4. Definition of Done
• All acceptance criteria pass
• Code reviewed and merged
• [Unit/integration tests written and passing]
• [Documentation updated if applicable]
• [Deployed to staging and verified]
How to Use This Template
Start with the user, not the feature
Think about who needs this and why before describing what to build. "As a customer" is better than "As a user" — specificity helps the team empathize.
Write testable acceptance criteria
Use the Given/When/Then format. Each criterion should be independently verifiable. If QA cannot test it, it is not clear enough.
Keep stories small
A story should fit in one sprint. If it takes longer, split it. Large stories hide complexity and risk. Small stories ship predictably.
Define what is out of scope
Explicitly state what the story does not cover. This prevents scope creep during development and keeps the team focused on the committed work.
Customize in Dewx
Inside Dewx, tell Dew: "Write user stories for the checkout redesign." Dew generates properly formatted stories with acceptance criteria, suggests story points based on complexity, and adds them to your backlog in the CX Hub. During sprint planning, drag stories into sprints and track them through completion.
Related Templates
Frequently Asked Questions
What is the correct format for a user story?
The standard format is: "As a [type of user], I want [action/capability], so that [benefit/value]." This three-part structure forces you to think about who needs it, what they need, and why it matters. Accompany every user story with acceptance criteria that define "done" in testable terms.
How detailed should a user story be?
A user story should be small enough to complete in one sprint but large enough to deliver value. The story itself should be 1-2 sentences. The detail lives in the acceptance criteria (3-7 specific, testable conditions). If a story needs more than 7 acceptance criteria, it is probably an epic that should be broken down further.
What is the difference between a user story and a task?
A user story describes a need from the user's perspective and the value it delivers. A task describes implementation work. "As a user, I want to reset my password" is a story. "Add forgot-password endpoint to the API" is a task. Stories define what and why; tasks define how. Good teams break stories into tasks during sprint planning.
How does Dewx help write user stories?
Inside Dewx, tell Dew: "Write user stories for a password reset feature." Dew generates properly formatted stories with acceptance criteria, suggests story points based on complexity, and adds them to your backlog in the CX Hub. During sprint planning, Dew helps prioritize and estimate the backlog.
Backlog Management, Simplified
Simple, Transparent Pricing
Starting at $29/mo for solopreneurs. $79/mo for teams. All features included.
View pricingWrite Better Stories, Ship Faster
Dew generates user stories with acceptance criteria and estimates — so your backlog is always sprint-ready.
Try Dewx FreeStop Writing Vague Backlog Items
Dewx generates properly formatted user stories with acceptance criteria, estimates, and priority. Keep your backlog clean, your sprints focused, and your team shipping.