Goodreads helps you keep track of books you want to read.
Start by marking “Specification by Example” as Want to Read:
Specification by Example
Enlarge cover
Rate this book
Clear rating
Open Preview

Specification by Example

4.08  ·  Rating Details  ·  390 Ratings  ·  39 Reviews

Specification by Example is an emerging practice for creating software based on realistic examples, bridging the communication gap between business stakeholders and the dev teams building the software. In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in sh
Paperback, 249 pages
Published June 3rd 2011 by Manning Publications (first published June 2011)
More Details... edit details

Friend Reviews

To see what your friends thought of this book, please sign up.

Reader Q&A

To ask other readers questions about Specification by Example, please sign up.

Be the first to ask a question about Specification by Example

The Pragmatic Programmer by Andrew HuntThe C Programming Language by Brian W. KernighanDesign Patterns by Erich GammaCode Complete by Steve McConnellClean Code by Robert C. Martin
Essential Programming Books
66th out of 126 books — 337 voters
Head First Design Patterns by Eric FreemanThe Pragmatic Programmer by Andrew HuntContinuous Delivery by Jez HumbleClean Code by Robert C. MartinWorking Effectively with Legacy Code by Michael C. Feathers
Becoming a Software Crafstman
13th out of 18 books — 5 voters

More lists with this book...

Community Reviews

(showing 1-30 of 1,192)
filter  |  sort: default (?)  |  Rating Details
Jan 27, 2013 Stijn rated it it was ok
Shelves: it
The book offers some very good ideas and is an interesting read, but too me it's too repetitive. You keep reading the same arguments and explanations over and over again, without going into concrete examples. It would have helped if the book contained a full blown actual example of the artifacts that are produced by SBE, and not just describing what the process is.
André Heijstek
Jan 15, 2013 André Heijstek rated it did not like it
Shelves: agile, engineering
The majority of the book is just an expansion of the praise pages typically found in USA books.
Never the book become concrete on HOW to create good test specifications.
Lance Willett
Mar 08, 2016 Lance Willett rated it liked it
Enjoyed this overview of a testing methodology that brings in BDD principles to automated software testing environments. It's a bit too complex for my needs, yet I love the idea of capturing everyone's opinion in specification (business owners, testers, developers, analysts) — as well as the philosophy of living documentation.

Two favorite bits:

1. Functional requirements, specs, and acceptance tests are the same thing.
2. Don't just disable failing tests — either fix the problem or move to a set o
Jan 02, 2012 Andy rated it liked it
Shelves: tech
I like the concepts in this book about having a living documentation system through testing. There are real-world, high-level case-studies, but I would like to have seen more examples of actual tests and tools.
Aug 22, 2015 Helene rated it really liked it
This book was an excellent description of how to develop and maintain good software. He does a great job explaining how product, development and testing can get on the same page. Every stage in the process is illustrated with stories of successful and unsuccessful teams and what teams learned going forward. The footnotes and references at the end are very helpful for people like me that want more background. Because I do not have a working knowledge of Cucumber and FitNesse, I had difficulty vis ...more
Karl Metivier
May 15, 2012 Karl Metivier rated it it was amazing
Shelves: agile
Gojko bring us another book about specifications. The first one was Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing and talked about the author personal experience in this subject. This time, we see other people's experiences with the using of Specification by Example. In addition to that, we see how Gojko has evolved his thinking about specification and after a few chapters, we go beyond the basics.

By the way, this book doesn't talk about code or tools. Jus
Aug 05, 2011 Ronald rated it liked it
Shelves: technical
I'm currently trying to better understand the BDD mind set and how it might improve things on my current project so I was really excited when Specification by Example showed up in my Kindle. I was looking forward to finding a whole check list of dos and don'ts to help accelerate me to BDD nirvana. Instead, I learned that implementation of SBE is very contextual -- one size does not fit all. Different teams use different techniques. The author interviewed several teams using SBE and discovered wh ...more
Ash Moran
Jan 04, 2012 Ash Moran rated it it was amazing
Often I wish I could say about some aspect of software development, literally, "let's do this by the book". Only then do I realise there is no book. It's like realising there is no spoon, except the problem can be solved by an experienced software developer, rather than the saviour of mankind. Until now, the process of capturing, formalising, and validating the high-level specification of software has been one of these inconsistently-documented problems. Gojko Adzic has changed that by structuri ...more
Deniss Rutseikov Ojastu
Feb 24, 2013 Deniss Rutseikov Ojastu rated it really liked it
A book on how to create and deliver software which is (a) quality; (b) what is needed; (c) not more than needed. One way to achieve that is needs and requirements specification together with clients. In addition, using different examples illustrating what software is supposed to do.

Capturing needs, not scripts - that is probably one of the most important messages from the book.

All in all, there are very good ideas and practices presented (many of them are still ahead of their time), albeit in so
Apr 08, 2013 Brett rated it it was amazing
According to Dan North, if you need a book on BDD, this is the book to read. In fact, Dan has said that he did not write a book because this one captures the essence of what he was trying to get across.

This book is based on actually talking with real projects and gives examples of what has and had not worked on projects for writing Executable Specifications. This contains a wealth of information on things to avoid based on what has/has not worked for other teams. On the other hand, when you read
Johnny Graber
Dec 31, 2015 Johnny Graber rated it it was amazing
The book is all about using examples to specify a (software) product and not an example of a specification. This distinction is important and should be considered before buying this book.

The book explains in great detail how example cases and scenarios can help you better understand the purpose and ideas behind a complex system. It will give you plenty of ideas and many things to think about. What you will not find is code. To adapt the ideas of the book in your project is therefore not so simp

Torben Rasmussen
Aug 23, 2012 Torben Rasmussen rated it it was amazing
Gojko Adzik has managed to lay out practices in the area of test driven acceptance testing, autmated testing and documentation. This certainly feels like testing done right and describes a collaborative approach to specification, testing and documentation focused on automation.

The key practices introduced are:
* Deriving scope from goals
* Specifying collaboratively
* Illustrating using example
* Refining the specification
* Automating without changing the specification
* Validating frequently
Vladimir Ryashentsev
May 19, 2016 Vladimir Ryashentsev rated it it was amazing
This book is for teams which want to build systems without bugs.
Mar 03, 2015 Olga rated it liked it
Shelves: technology, learning
Fine book, but it seemed to put too much emphasis on renaming stuff. Not BDD, but Specification by examples; not tests, but live documentation; and on and on.
Jul 09, 2016 Santosh rated it it was amazing
A must if you are in Software development
Nov 13, 2013 Eduardo rated it liked it
It is definitely a book for a more than one read, mainly because it exposes different scenarios and tips on how other teams have resolved them; so you'll probably need to go back to them in the future. All this on teams where they already have started or reaching a mature Agile software development process.
This set up makes for a more complex read since there are lots of related data and not all of them are clear at the beginning.
All in all is good book and worth reading it, even if you are in t
Dwight Walker
Jan 24, 2016 Dwight Walker marked it as to-read
Ruby and devops
Rick Austin
Oct 10, 2012 Rick Austin rated it it was amazing
Great introduction to the concept of specification by example. This is not a technical book and will not teach you how to implement but it does provide a deep overview of specification by example. Extensive interviews with a number of companies provide real-world examples of how this works and the benefits gained by each. Very open about mistakes made by some teams which was very helpful.

Great read that now has me wanting to learn more about how to implement these practices.
Aug 18, 2013 Pavleras rated it really liked it
my interest has been risen progressively. I didn't have any expectation and I've changed my opinion. The framework proposed to apply BDD is very understandable and easy to follow. This book focuses on how to increase collaboration, how to modify your development process. The book explains to the reader, other team experiences applying BDD. I miss a more detailed explanation about how to make the tests but the book would be probably much longer.
Sebastian Gebski
Jan 29, 2013 Sebastian Gebski rated it it was amazing
Deep analysis of ATDD (Acceptance Test Driven Development), enriched with several real life cases. Detailed and precise (sometimes even a bit too much, what made it dull at some points). I leaned towards 4 stars, but this book answers a lot of questions about user acceptance and specifications in agile methods - the questions other are usually afraid to address. That's why it's 5 stars after all.
Karyn Crouse
May 21, 2014 Karyn Crouse rated it really liked it
Well written and interesting read, good examples and case studies, a good introduction to SBE/BDD/ATDD
Daniel Temme
Mar 19, 2012 Daniel Temme rated it really liked it
Really nice book. Especially liked the different context of the different projects' experiences.

At times I might have wished for some more technical examples but the RSpec book seems to be a good companion book for that.
Bjoern Rochel
Aug 18, 2012 Bjoern Rochel rated it really liked it
Shelves: technology
I really like the case studies used throughout the book. I had hoped that the book would go into more detail, but nevertheless It left me with a lot of ideas of how to improve what we're doing in my current team.
Scott Maclellan
Dec 08, 2014 Scott Maclellan rated it really liked it
Some excellent ideas to keep your system/tests maintainable long term. I really like how the book focuses on ideas and different practices that worked for teams over the tools and software they used.
Dec 09, 2012 Kevin rated it liked it
Shelves: computer
Great start and ending, with lots of useful and practical tips straight from the the field. The thesis seemed to get tired and slow during the beginning, but definitely still a worthwhile read.
Jul 22, 2014 Ivan rated it really liked it
Shelves: programming
Краткая статья не хабре
Классные примеры и подробное объяснение рассматриваемых тем. Мне было интересно узнать что вообще такое существует)
Aug 16, 2013 Geert rated it really liked it
Core principles and ideas are very good.
Though I found the interlacing of comments and text a bit frustrating at times. (Stops it from being a smooth read.)
Definitely a great book for who wants to improve or start the "Specification by Example" practice.
A lot of good advices "from the trenches" !
Josh Brown
Dec 31, 2013 Josh Brown rated it really liked it
Shelves: 2013
Great points on why to create a living documentation system. I would've loved to see more examples of good specifications and how to write them.
« previous 1 3 4 5 6 7 8 9 39 40 next »
There are no discussion topics on this book yet. Be the first to start one »
  • The Cucumber Book
  • Agile Testing: A Practical Guide for Testers and Agile Teams
  • Lean from the Trenches
  • Growing Object-Oriented Software, Guided by Tests
  • Agile Retrospectives: Making Good Teams Great
  • User Stories Applied: For Agile Software Development
  • Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing
  • Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
  • Implementing Domain-Driven Design
  • Continuous Integration: Improving Software Quality and Reducing Risk
  • Kanban: Successful Evolutionary Change for Your Technology Business
  • How to Change the World: Change Management 3.0
  • Domain-Driven Design: Tackling Complexity in the Heart of Software
  • Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise
  • Agile Software Development, Principles, Patterns, and Practices
  • Test Driven Development: By Example
  • The RSpec Book
  • ATDD by Example: A Practical Guide to Acceptance Test-Driven Development

Goodreads is hiring!

If you like books and love to build cool products, we may be looking for you.
Learn more »

Share This Book