Choose Your Level
Pick the difficulty that matches where you are. You can come back and try a harder level later.
Write User Stories for a Feature
Write 8 user stories for a mobile banking "Send Money" feature.
Acceptance Criteria & Edge Cases
Write Given/When/Then acceptance criteria for 3 user stories with edge cases.
Story Mapping a Product Release
Build a user story map for an MVP launch with backbone and release slices.
Agile User Stories & Acceptance Criteria (Gherkin Syntax)
User stories define product requirements from the end user's perspective. Agile teams assess business analysts on writing stories using standard syntax ('As a... I want... So that...'), adhering to INVEST quality criteria, and defining testable acceptance criteria in Gherkin (Given-When-Then) format.
1. Agile User Story Backlog Specification
Product backlog document containing well-structured user stories complete with user personas and business value justifications.
2. Gherkin Acceptance Criteria Test Suite
Acceptance criteria library written in Given-When-Then format covering happy path and edge-case scenarios.
3. INVEST Criteria Quality Audit Log
Quality assurance checklist verifying user stories meet INVEST standards before sprint planning.
Frequently Asked Questions (User Stories & Acceptance Criteria)
What does the INVEST acronym stand for in user stories?
Independent, Negotiable, Valuable, Estimable, Small, and Testable.
How do you write acceptance criteria using Gherkin syntax?
Given [initial context/state], When [action occurs], Then [expected outcome/behavior].
What is the difference between a User Story and a System Requirement?
A User Story focuses on end-user needs and value ('As a shopper...'). A System Requirement specifies technical mechanics ('The database shall encrypt stored credit card numbers').
Explore Business Analysis Career Paths
Build proof of work across other topics or view full career roadmaps mapping technical skills to hiring expectations.