Win a copy of Zero to AI - A non-technical, hype-free guide to prospering in the AI era this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

BDD and non-agile

 
Ranch Hand
Posts: 34
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
John,

I'll repeat the same question I did during last JavaOne (for recors purposes): is it possible to use BDD in a non-agile environment?

Paulo
 
Author
Posts: 43
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In short: BDD at the coding level (AKA BDD-style TDD) is possible and valuable for any team: benefits include fewer bugs, more focused development activities and great technical documentation for your APIs in the form of well-written and well-structured unit tests. But it is at the requirements level that the real benefits of BDD become obvious: more relevant and more valuable features, a better shared understanding of the requirements, fewer misunderstood, misaligned or forgotten requirements, less waste, more efficient use of tester time, etc. These benefits hinge on collaborative discovery of the requirements, which is very hard to do in a prescriptive software development approach where the requirements are "completed" and "signed-off" before being handed to the development team for implementation. Similarly, the role of the tester is handicapped if she can only intervene at the end of the process, or to automate regression tests. So in essence, BDD without the ability to collaborate on requirements discovery is somewhat ham-stringed.
 
I think I'll just lie down here for a second. And ponder this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic