Atlassian's Detailed User Story
Atlassian's enhanced user story format that adds acceptance criteria, technical notes, design considerations, and testing requirements to the classic format.
User Story Template - Atlassian (Detailed Format)
Variant: Atlassian Detailed User Story Format Source: Atlassian Agile Coach (2023) PM33 Adaptation: 1.0 Focus: Structured details, acceptance criteria, technical clarity
Overview
Atlassian's detailed format provides structured templates for capturing comprehensive story information. This variant emphasizes well-defined acceptance criteria and clear technical requirements while maintaining PM33's strategic alignment focus.
Story Information
| Field | Value |
|---|---|
| Story ID | [PROJECT-001] |
| Title | [Clear, action-oriented title] |
| Story Type | Feature / Bug Fix / Technical Debt / Spike |
| Status | Backlog / Ready / In Progress / In Review / Done |
| Priority | P0 / P1 / P2 / P3 |
| Assignee | [Team member] |
| Sprint | [Sprint name or Backlog] |
| Story Points | [Points] |
| Epic | [Epic name] |
User Story
Summary
As a [user type/role], I want to [action/feature], So that [benefit/outcome]
Description
Showing 40 of 362 lines
Enter your email below to unlock the full template
Unlock Full Template
Enter your email to access the complete template
Other User Story Variants
Mike Cohn's Classic User Story
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.
BDD Gherkin Format
Behavior-Driven Development (BDD) user stories using the Given-When-Then (Gherkin) format. Creates executable specifications that bridge business requirements and automated tests.
Related Templates
Fill This Template With AI
PM33 turns these templates into living documents. AI-powered suggestions, auto-populated metrics, and team collaboration built in.
Join the Waitlist