User Story Block
Document user stories with the standard 'As a/I want/So that' format, acceptance criteria tracking, story points, and sprint assignment.
The User Story block documents user stories in the standard agile format. It captures the user's perspective, desired outcome, and business value along with acceptance criteria and sprint planning information.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Story ID | No | Unique identifier (e.g., US-001) |
| Title | Yes | Brief story summary |
| As a | No | User role or persona |
| I want | No | Desired capability or feature |
| So that | No | Business value or outcome |
| Acceptance Criteria | No | List of verifiable conditions with completion tracking |
| Priority | No | Critical, High, Medium, Low |
| Story Points | No | Estimation value |
| Status | No | Backlog, Ready, In Progress, Done, Blocked |
| Sprint | No | Sprint assignment |
| Assignee | No | Team member responsible |
| Epic | No | Parent epic reference |
| Notes | No | Additional context |
Story Status
Example: Feature Story
A typical product feature user story with acceptance criteria.
Example: Bug Fix Story
A user story for addressing a bug from the user's perspective.
Example: Technical Story
A story for technical improvements with user impact.
Best Practices
| Practice | Description |
|---|---|
| User Perspective | Write stories from the user's perspective, not technical implementation |
| Sprint-Sized Stories | Keep stories small enough to complete in one sprint |
| Measurable Criteria | Include measurable acceptance criteria |
| Epic Linking | Link related stories to their parent epic |
| Relative Estimation | Estimate using relative story points |
| Status Updates | Update status as work progresses |
| Progressive Tracking | Mark criteria as met during development, not just at completion |
| Context Notes | Use notes for technical context or follow-up items |