Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your email address or mobile phone number.
Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing Paperback – January 5, 2009
|New from||Used from|
Top 20 lists in Books
View the top 20 best sellers of all time, the most reviewed books of all time and some of our editors' favorite picks. Learn more
Frequently Bought Together
Customers Who Bought This Item Also Bought
More About the Author
Gojko's book Specification by Example was awarded the #2 spot on the top 100 agile books for 2012 and won the Jolt Award for the best book of 2012. In 2011, he was voted by peers as the most influential agile testing professional, and his blog won the UK agile award for the best online publication in 2010.
Top Customer Reviews
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.Read more ›
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.
Thet second big lesson that the book describes is how specifications can me made more clear by working together as a team and saving lots of time when we store the specifications in testing tools in a format that customers can read and understand.
Personally I find the style of writing rather dry so pushing ahead through the material takes some commitment, but it is worth it. The lessons, techniques and value of the results provide an excellent payoff.
Most Recent Customer Reviews
This method of agile acceptance testing for specifying requirements is specific and so thoroughly helps to communicate what is being talked about and agree on it - it really is... Read morePublished 4 months ago by CollinK
I think this is a must read for anyone involved in a software development project. I love how it teaches you specification by example as a concept and philosophy to be learned by... Read morePublished 10 months ago by Deryl Spielman