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
Stock photo: cover may vary

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

by Adzic, Gojko

Add to wish list
  • Used
  • Good
  • Paperback
Used - Good

Description

Neuri Limited. paperback. Good. 6x0.6x9.1. Buy with confidence. Excellent Customer Service & Return policy.
Ask the seller a question Add to wish list
A$23.16
Free Delivery to USA
Standard delivery: 7 to 10 days
More delivery options
Dropship order
Ships from Ausvora INC (Connecticut, United States)

Details

About Ausvora INC Connecticut, United States

Biblio member since 2025

We are a U.S.-based online bookstore specializing in quality used books at affordable prices. With over 1 million books in stock, we serve readers, resellers, libraries, and institutions across the United States and internationally.

Terms of Sale:

Fast & Reliable Shipping All orders ship within 1–2 business days. Domestic shipping across the U.S. via USPS or UPS. International shipping available to most countries. 🔁 30-Day Hassle-Free Returns If the book isn't as described, we'll make it right. Enjoy a full 30-day return window with no questions asked.

Browse books from Ausvora INC

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-