Skip to content

User Stories

User Stories are short, simple descriptions of a feature told from the perspective of the end user.

Purpose

  • Capture requirements in a user-centric way
  • Facilitate collaboration between stakeholders and the team
  • Provide a basis for estimation and planning

Format

A common template is:
As a [type of user], I want [some goal] so that [some reason].

Example:
As a registered user, I want to reset my password so that I can regain access to my account.

Characteristics

  • Focus on value to the user
  • Small and testable
  • Negotiable and flexible

Benefits

  • Encourages conversation around requirements
  • Helps break down complex features
  • Supports iterative development

Acceptance Criteria

Acceptance Criteria are the "definition of done" for a User Story. They are a set of conditions that must be met for the story to be considered complete.

Purpose: - Eliminate ambiguity and align understanding. - Define the boundaries of the story. - Provide a basis for testing.

Common Format (Gherkin Syntax): * Given a specific context. * When an action is performed. * Then a specific, observable outcome occurs.

Example: For a password reset story: * Given I am on the password reset page, * When I enter my registered email and click "Send Reset Link", * Then I should see a confirmation message and receive an email with a reset link.

Story Mapping

Story Mapping is a visual and collaborative exercise to create a shared understanding of a product's user journey.

Process: 1. Map the Journey: Identify the main activities and steps a user takes (the "narrative flow"). 2. Organize Stories: Place user stories under the corresponding steps. 3. Prioritize: Arrange stories vertically by priority (high to low). 4. Slice Releases: Draw lines across the map to define product releases, starting with a Minimal Viable Product (MVP).

Benefits: - Visualizes the entire product and user experience. - Helps prioritize work and identify gaps. - Facilitates release planning.