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

Lots of words in this book. The first few chapters were fairly interesting but eventually it became rather a grind to get to the end.Sum up the thesis with "don't make assumptions about what people want: ask"And some software developers are full of their own self-importance.

An enjoyable read that gives a satisfactory introduction into improving your software development process with the help of "specification by example" practices. The author spends plenty of time highlighting and addressing subtle and important issues that come up during typical software development life cycle for analysts, testers and developers. He explains in detail how "specification by example" (used interchangeably with "agile acceptance testing") can heighten effective levels of collaboration during a typical development iteration and lead to nipping common issues in the bud and improving the engagement of all involved.

This book covers some all important missing pieces from many software development teams.If the thought of developing software without the ambiguity of requirements appeals to you, this is the book to read.

I bought this book after attending a seminar on testing using Fitnesse by the author.The book is an excellent introduction to agile acceptance testing explaining the concepts, tools available and practices. The book reads very well and the author has also obviously done his research and I learnt a lot from reading it having only recently fully embraced agile methodologies.

Gojko is a bit of a phenomenon here in London.He makes sense in a field where relatively few people actually know what they're talking about. At the core, he understands that specification examples are about communication, with regression as a bonus, and that it takes effort and taste to get the (substantial) benefits from applying the technique.