- Paperback: 296 pages
- Publisher: Manning Publications; 1 edition (June 6, 2011)
- Language: English
- ISBN-10: 1617290084
- ISBN-13: 978-1617290084
- Product Dimensions: 7.4 x 0.6 x 9.2 inches
- Shipping Weight: 1.1 pounds (View shipping rates and policies)
- Average Customer Review: 35 customer reviews
- Amazon Best Sellers Rank: #155,422 in Books (See Top 100 in Books)
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 mobile phone number.
Specification by Example: How Successful Teams Deliver the Right Software 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2018 So Far
Looking for something great to read? Browse our editors' picks for the best books of the year so far in fiction, nonfiction, mysteries, children's books, and much more.
Frequently bought together
Customers who bought this item also bought
About the Author
A UK based consultant, Gojko Adzic helps teams worldwide implement specification by example and agile testing practices. He has written two previous books on the subject and contributed to several open source projects supporting specification by example. Gojko is a frequent speaker at leading software development and testing conferences and runs the UK Agile Testing User Group.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
A must read for everyone building non-trivial systems with long life spans! Some downsides (I’d given 5 stars without these):
- Although the case studies were very interesting, their reporting in the book was a bit shallow. I would liked to have seen more details and in-depth analysis of each case.
- As it says in the book, one of the best ways to learn to write good specifications is to study good examples, I expected to see more examples of specifications and wanted to see what the specs the teams in the case studies were creating look like.
- Although this book isn’t about tools, I would liked to have seen some kind of sketches or diagrams of the development / test / build / documentation environments the teams build in the case studies. I also think that the hierarchy or structure of the specs (e.g. epic-feature-story) would be one important topic to discuss about.
The book Specification by Example is the result of drawing experiences from how a number of actual project teams work with the practice Specification by Example. This makes the book particularly valuable, since its advice in not solely based on theories or opinions on how develop software, but it distills experiences of what has actually worked in different situations and in different domains.
The ideas of the practice Specification by Example have been in use for some time now, under different names like Acceptance Test-Driven Development, Agile Acceptance Testing and Behavior-Driven Development. The author chooses in my mind a sensible terminology for the practice itself and its different parts, or process patterns to use the authors term.
The book has two main parts, the description of the process patterns of Specification by Example, and a set of case studies of project that uses Specification by Example. In addition the book contains an introduction to the practice of Specification by Example and guidelines on how to introduce the practice in organizations.
These process patterns of Specification by Examples are described together with tips about "does" and "don'ts". The case studies part of the book contains six case studies covering a diverse set of domains.
As a software developer that was "test infected" 10 years ago, a think that the practice Specification by Example, essential for successful and efficient software development. I think this book is the best book on the market today, for learning and adopting the practice Specification by Example.
One of the biggest questions I have always received is how do you scale a process for specifying your work via Examples so that small projects can obtain the same benefits and this is covered very well in the book, it has given me many new ideas about how to work within smaller project/team structures.
If you are just starting Agile, read this book, your teams will benefit from the discipline of Specification by Example. If you are already Agile this book will help you get better, improve your velocity, lower defects identified and generally make the process of moving fast less stressful.
Quality isn't a word is a process and this book will help you build the right process for your organization.
Most recent customer reviews
As Gojko has discovered the hard part about Acceptance Test Driven Development (aka ATDD), Behaviour Driven Development (BDD) or...Read more