A user story is a short, simple description of a feature told from the perspective of the person who desires the capability. User stories are the building blocks of agile development, capturing requirements in a way that is understandable to both business and technical stakeholders.
A user story is a short description of a feature told from the user's perspective, typically using the format: 'As a [type of user], I want [capability] so that [benefit].' Created by Mike Cohn, this format is the standard in agile development. Variations include Atlassian's detailed format with acceptance criteria and BDD's Given-When-Then (Gherkin) format for executable specifications.
Document Type: User Story PM33 Version: 1.0 Last Updated: 2026-02-14 Template Format: Comprehensive
A user story is a concise description of a feature from the perspective of an end user or stakeholder. PM33 user stories emphasize strategic alignment, ensuring each story connects to broader business objectives and contributes measurably toward strategic goals.
[STORY ID]: [PROJECT-001]
Title: [Clear, action-oriented title in user perspective]
Status: Backlog | Ready | In Progress | Review | Done
Priority: P0 | P1 | P2 | P3
Points: [Estimated story points]
Assigned To: [Team member]
Sprint: [Sprint name/number or "Backlog"]
Format: "As a [user role], I want to [action], so that [business value]"
As a [user role/persona] I want to [specific action/capability] So that [business outcome/value]
Background Provide context for why this story matters, what problem it solves, or what opportunity it addresses.
Acceptance Criteria Define the conditions that must be satisfied for this story to be considered complete. Use Given/When/Then BDD format where applicable.
Showing 50 of 255 lines
Enter your email below to unlock the full template
Enter your email to access the complete template
Explore 3 community-created variations optimized for different workflows and team structures.
The original 'As a [role], I want [capability] so that [benefit]' format from Mike Cohn's User Stories Applied. The most widely used user story format in agile.
Atlassian's enhanced user story format that adds acceptance criteria, technical notes, design considerations, and testing requirements to the classic format.
Behavior-Driven Development (BDD) user stories using the Given-When-Then (Gherkin) format. Creates executable specifications that bridge business requirements and automated tests.
A user story is a short description of a feature from the user's perspective. The classic format is: 'As a [type of user], I want [capability] so that [benefit].' User stories are the building blocks of agile backlogs and help teams focus on delivering value to users.
Good acceptance criteria are specific, testable, and independent. Use the Given-When-Then format: Given [precondition], When [action], Then [expected result]. Each criterion should test one thing, be verifiable by QA, and not depend on other criteria. Aim for 3-7 acceptance criteria per story.
These templates complement user story and work well together in your product development process.
You have defined requirements. Now organize teams to execute.
Explore Execution Phase Templates