Luke Redpath wrote a very interesting post on Behaviour Driven Development (BBD), the missing step in the agile practices arena, inheriting some good idea from Domain Driven Design -- read the introduction by Martin Fowler (see picture) or the PDF book Domain Driven Design Quickly. It's free if you register.
If you have ever felt that Test Driven Development (TDD) is great but you need a human-human interface to talk to customers (not always) on site, or that TDD practice doesn't go beyond your code activity, BBD introduction is worth a read.
Not something against TDD but integrating, in favour of one of my educational missions: working for one culture, against the false dichotomy humanists vs. technologists.
Quoting:
BDD relies on the use of a very specific (and small) Vocabulary to minimise miscommunication and to ensure that everyone – the business, developers, testers, analysts and managers – are not only on the same page but using the same words. It must be stressed that BDD is a rephrasing of existing good practice, it is not a radically new departure. Its aim is to bring together existing, well-established techniques under a common banner and with a consistent and unambiguous terminology. In fact, “getting the words right” was the starting point for the development of BDD, and is still very much at its core. “Getting the words right” is intended to produce a vocabulary that is accurate, accessible, descriptive and consistent.
Thanks to Matteo's post for this link discover.
No comments:
Post a Comment