Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing (Paperback)

~ Gojko Adzic (Author)
Key Phrases: agile acceptance testing, formalising examples, specification workshop, Rick Mugridge, Mike Cohn, Mickey Phoenix (more...)

Editorial Reviews

Product Description

Bridging the Communication Gap is a book about improving communication between customers, business analysts, developers and testers on software projects, especially by using specification by example and agile acceptance testing. These two key emerging software development practices can significantly improve the chances of success of a software project. They ensure that all project participants speak the same language, and build a shared and consistent understanding of the domain. This leads to better specifications, flushes out incorrect assumptions and ensures that functional gaps are discovered before the development starts. With these practices in place you can build software that is genuinely fit for purpose.

Product Details

• Paperback: 284 pages
• Publisher: Neuri Limited (January 5, 2009)
• Language: English
• ISBN-10: 0955683610
• ISBN-13: 978-0955683619
• Product Dimensions: 9 x 5.9 x 0.8 inches
• Shipping Weight: 1 pounds (View shipping rates and policies)
• Average Customer Review: 5.0 out of 5 stars  See all reviews (2 customer reviews)
• Amazon.com Sales Rank: #92,451 in Books (See Bestsellers in Books)

  Popular in these categories: (What's this?)

  #25 in	Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Testing
  #48 in	Books > Computers & Internet > Computer Science > Systems Analysis & Design

Customer Reviews

Most Helpful Customer Reviews

1 of 1 people found the following review helpful:

5.0 out of 5 stars Much needed book., July 18, 2009

By	Bas Vodde (Singapore) - See all my reviews

Amazon Verified Purchase

"Bridging the communication gap" by Gojko Adzic is a much needed book on a very important topic that finally is deserving the attention it needs: Agile acceptance testing. This practice is also known as "automated acceptance testing" or as "acceptance-test-driven development." It has evolved over the last decade, but was known and used in a relative small group. Every year there would be a couple papers on the topic, Lasse Koskela covered it a bit in his "Test-Driven" but now finally Gojko takes the subject further and devotes a whole book on it.

What is it? Agile Acceptance Testing is a technique for closing the communication gap between business, developers and testers. A way to write specifications as examples which become executable. The specification are created together in a workshop and not handed over like traditional requirements.

The book is written in four parts. The first part is an introduction to the topic, describes an overview of the technique. An important part of this part (and the whole book) is the focus on communication instead of test. This is reflected in the excellent discussion about naming. Agile Acceptance Testing is perhaps one of the most poorly named practices, but... still... thats the name it became popular with (or with A-TDD). The second part is the most important parts of the book, which describes how to write specifications, why to work with examples, how to run specification workshops and what to do after these workshops. The part ends with a discussion about change in projects and how the automated acceptance test help with that.

The third part discusses implementation. It starts with how to fit this technique in an iteration and how to adopt the practice. Next is a chapter on user stories and its relationship with acceptance tests. Then the part dives in the tools by first covering the current tools and then discussing the requirements for the future tools. The last part of the book describes the impact of agile acceptance testing on the different functions: business analyst, developer and tester.

Bridging the Communication Gap is a small book (300 pages) and is easy to read. It could have been smaller, the writing is sometimes a little too wordy. It doesn't contain too much pictures, which is too bad when a book talks so much about workshops. Yet, despite these drawbacks, I think this is an excellent book and a much needed contribution to the modern software development/agile development literature. It was one of the few practices that did not have its own book yet and Gojko provided that.

I was doubting between 4 and 5 stars for this review. 4 because this book is certainly not perfect. 5 stars because it is good still. Because this is a first in a new area and because I consider this an important area, I decided to go for 5 stars. This will certainly be a book that I will be recommending to other people (and in fact, I already have). Great work Gojko!

1 of 1 people found the following review helpful:

5.0 out of 5 stars Delivering Value - a cultural shift, January 30, 2009

By	Lisa Crispin (Denver, CO United States) - See all my reviews

Teams transitioning to agile development tend to focus on process rather than values. But you can't simply master a set of practices and be successful. Your whole team needs to understand what your business needs so you can deliver value. Your whole team needs to commit to creating a quality product.

This book not only explains how to use examples to understand requirements and create tests that drive coding, it explains the cultural shift needed for successful software development. The author explains the communication gap, why we should care about it, and how we can fix it.

Whether you're new to agile development, or are on an experienced team wondering why you keep missing or misunderstanding the business requirements, this book delivers critical value.