Foreword by Dale Emery
Too many software projects fail to deliver what their customers request. Over the years, I’ve heard scores of project customers explain the failures: The developers don’t pay attention to what we ask them to build. And I’ve heard hundreds of developers explain the failures: The customers don’t tell us what they want. Most of the time they don’t even know what they want.
I’ve observed enough projects to come to a different conclusion: Describing a software system’s responsibilities is hard. It requires speaking and listening with precision that is rare—and rarely so necessary—in normal human interactions. Writing good software is hard. Testing software well is hard. But the hardest job in software is communicating clearly ...
Get ATDD by Example: A Practical Guide to Acceptance Test-Driven Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
