20 Years of BDD
summary
A first‑principles history with concrete claims: BDD starts as a way to teach TDD without the word “test,” the Java project registered jbehave.org Dec 23 2003 spawns tooling (JBehave, RSpec, Cucumber, Reqnroll, behat) and a Given-When-Then three column rule that becomes grammar Gherkin; the ecosystem carries 70+ language ports and commercial churn, and practical metrics surface — throughput, WIP and lead times 2 weeks to 14 months — plus Demand‑Led Planning and flow levers that actually change delivery.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 2:58The importance of empathy
- 5:28Origins of bdd
- 10:59Evolution of bdd tools
- 14:15Building the community
- 15:48Demand-led planning
- 25:26Autonomy through alignment
- 26:53The future of bdd
related talks
48mBDD - It’s More Than Acceptance Tests
41mBDD Crash Course for Testers
08m"BDD: NOT The Given-When-Then Thing"
48mMake Your Life Simple and Carefree with BDD
40mMaking BDD Work for you
45mBehaviour Driven Development: Embrace Uncertainty
31mBDD: Behaviour Driven Development
48mMake Your Life Simple and Carefree with BDD