BDD Gherkin Format
Behavior-Driven Development (BDD) user stories using the Given-When-Then (Gherkin) format. Creates executable specifications that bridge business requirements and automated tests.
User Story Template - BDD/Gherkin Format
Variant: BDD/Gherkin User Story Format Source: Behavior-Driven Development (Cucumber, SpecFlow) PM33 Adaptation: 1.0 Focus: Executable specifications, test automation, shared language
Overview
BDD/Gherkin format combines user stories with executable specifications. Stories are written in plain language but structured as scenarios that can be automated. This variant emphasizes collaboration between developers, QA, and product owners using shared, executable specifications.
Story Header
Feature: Generate Competitive Analysis Report
As a VP of Product Strategy
I want to generate competitive analysis reports from collected intelligence
So that I can make data-driven strategic decisions about feature prioritization
Strategic Alignment: Enables data-driven decision making for Q1 2026 strategy roadmap
Epic: Strategic Intelligence Platform
Story Points: 8
Scenario-Based Format
Scenario 1: User Generates Report with Valid Data
Scenario: User successfully generates competitive analysis report
Given I am logged in as a user with "strategy_admin" role
And my workspace "Acme Corp Strategy" exists with 50 collected articles
And the articles are tagged with 5 competitors
When I navigate to "Reports" > "Competitive Analysis"
Showing 40 of 389 lines
Enter your email below to unlock the full template
Unlock Full Template
Enter your email to access the complete template
Frequently Asked Questions
What is the Gherkin format?
Gherkin is a structured language for writing BDD scenarios: 'Given [precondition], When [action], Then [expected result].' Scenarios are written in plain English but can be directly executed as automated tests using tools like Cucumber, making them both documentation and test specifications.
Other User Story Variants
Mike Cohn's Classic User Story
The original 'As a [role], I want [capability] so that [benefit]' format from Mike Cohn's User Stories Applied. The most widely used user story format in agile.
Atlassian's Detailed User Story
Atlassian's enhanced user story format that adds acceptance criteria, technical notes, design considerations, and testing requirements to the classic format.
Related Templates
Fill This Template With AI
PM33 turns these templates into living documents. AI-powered suggestions, auto-populated metrics, and team collaboration built in.
Join the Waitlist