Phase 3 · Requirements Analysis & Documentation
TopicsUser Stories & Acceptance Criteria
Part of the Business Analyst Roadmap.
Summary
A user story frames a requirement from the user's perspective ('As a [user], I want [goal], so that [reason]'); acceptance criteria define exactly when that story is considered done — the standard format in Agile delivery.
How to Learn This
- 1Write 5 user stories for a feature idea, each with 2-3 acceptance criteria.
- 2Practice the Gherkin 'Given-When-Then' format for acceptance criteria.
- 3Learn why vague acceptance criteria cause the most BA-engineer friction.
More topics in Requirements Analysis & Documentation
Functional vs Non-Functional RequirementsBusiness Requirements Document (BRD)Functional Requirements Document (FRD)Use Cases & Use Case DiagramsRequirements Traceability Matrix (RTM)Requirements Prioritization (MoSCoW)Writing Clear, Testable RequirementsRequirements Validation & Sign-OffManaging Requirement Changes
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — free on the InsideEdge app.