BIBLIO is the largest independent book marketplace in the world, with over 100 million books.

Skip to content

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

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

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

by Gojko Adzic

Add to wish list
  • New
  • Paperback
New

Description

Paperback. New. New Book; Fast Shipping from UK; Not signed; Not First Edition; 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 t
Ask the seller a question Add to wish list
A$56.32
A$15.26 Delivery to USA
Standard delivery: 7 to 12 days
More delivery options
Ships from Ria Christie Collections (Greater London, United Kingdom)

Details

About Ria Christie Collections Greater London, United Kingdom

Biblio member since 2014

Hello We are professional online booksellers. We sell mostly new books and textbooks and we do our best to provide a competitive price. We are based in Greater London, UK. We pride ourselves by providing a good customer service throughout, shipping the items quickly and replying to customer queries promptly. Ria Christie Collections

Terms of Sale:

30 day return guarantee, with full refund including original shipping costs for up to 30 days after delivery if an item arrives misdescribed or damaged.

Browse books from Ria Christie Collections

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

From the publisher

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.
tracking-