In this great book Gojko explains how to overcome the gap between the technical viewpoint of Software Development and the customer perspective. By bringing together the whole development team from the beginning of the project, fewer misunderstandings of business needs can be achieved. For this reason he introduces Specification Workshops and Requirements by Example, that enable teams to start right from the beginning on the right foot and reduce necessary rework to achieve a mutual benefit for the business and the development team.
In Bridging The Communication Gap Gojko discusses topics about requirements, Agile acceptance testing (ATDD), user stories as well as tools for specification by example. He gives a compelling overview into each parts. For the requirements part, specification workshops alongside with requirements by example build the basis for measurable and executable requirements. Gojko gives an overview on the Agile Acceptance Test cycle, and explains where it fits into the Agile development cycle. As user stories are the standard way to introduce new features in Agile projects, he also discusses their role in the ATDD cycle. On the tools in use today, he shows the most commonly used (as by 2008/2009) - FIT, FitNesse, Concordion, TextTest, JBehave and Selenium - and where the development of the tools from tomorrow are most likely to go. Last he takes a closer look on impacts of his approach on different roles in the software cycle - customers, developers, testers and business analysts.
This book is a must read for anyone struggling with requirements and acceptance testing. It shows how to a working approach, which Gojko applied several times on his consulting job. He wrote this book based upon his compelling experience helping organizations and teams with test automation and Agile testing.