User Story: Title
Story – acceptance criteria, UX notes, estimation
Cómo usar: Sprint backlog items. Acceptance criteria are the contract – write them testable.
Vista previa
User Story: Title
As a [type of user] I want [goal] So that [benefit/outcome]
Context
Why this story exists. Link to research, feedback, or parent epic.
Acceptance criteria
- Given [context], when [action], then [expected result]
- Given [context], when [action], then [expected result]
- Edge case: [scenario] → [expected handling]
Out of scope
- What this story does not include
UX / design notes
Mockup link, interaction details, error states, empty states, loading states, accessibility requirements (keyboard nav, screen reader labels).
Technical notes
Implementation hints, API touchpoints, data model impact, performance constraints.
Estimation
| Field | Value |
|---|---|
| Story points | N |
| Priority | P0 / P1 / P2 |
| Sprint | NN |
| Depends on | #NNN |