or
Sign in to turn on 1-Click ordering.
Trade in Yours
For a £8.55 Gift Card
Trade in
More Buying Choices
Have one to sell? Sell yours here
Sorry, this item is not available in
Image not available for
Colour:
Image not available

 
Tell the Publisher!
I’d like to read this book on Kindle

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Specification by Example: How Successful Teams Deliver the Right Software [Paperback]

Gojko Adzic
4.6 out of 5 stars  See all reviews (8 customer reviews)
RRP: £31.99
Price: £25.60 & FREE Delivery in the UK. Details
You Save: £6.39 (20%)
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Only 9 left in stock (more on the way).
Dispatched from and sold by Amazon. Gift-wrap available.
Want it Thursday, 25 Sep.? Choose Express delivery at checkout. Details
Trade In this Item for up to £8.55
Trade in Specification by Example: How Successful Teams Deliver the Right Software for an Amazon Gift Card of up to £8.55, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Learn more

Book Description

6 Jun 2011 1617290084 978-1617290084 1

Summary

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 short iterative delivery cycles.

About the Technology

Specification by Example is a collaborative method for specifying requirements and tests. Seven patterns, fully explored in this book, are key to making the method effective. The method has four main benefits: it produces living, reliable documentation; it defines expectations clearly and makes validation efficient; it reduces rework; and, above all, it assures delivery teams and business stakeholders that the software that's built is right for its purpose.

About the Book

This book distills from the experience of leading teams worldwide effective ways to specify, test, and deliver software in short, iterative delivery cycles. Case studies in this book range from small web startups to large financial institutions, working in many processes including XP, Scrum, and Kanban.

This book is written for developers, testers, analysts, and business people working together to build great software.

Purchase of the print book comes with an offer of a free PDF, ePub, and Kindle eBook from Manning. Also available is all code from the book.

What's Inside
  • Common process patterns
  • How to avoid bad practices
  • Fitting SBE in your process
  • 50+ case studies

For additional resources go to specificationbyexample.com.

========================================​=======

Table of Contents
    Part 1 Getting started
  1. Key benefits
  2. Key process patterns
  3. Living documentation
  4. Initiating the changes
  5. Part 2 Key process patterns
  6. Deriving scope from goals
  7. Specifying collaboratively
  8. Illustrating using examples
  9. Refining the specification
  10. Automating validation without changing specifications
  11. Validating frequently
  12. Evolving a documentation system
  13. Part 3 Case studies
  14. uSwitch
  15. RainStor
  16. Iowa Student Loan
  17. Sabre Airline Solutions
  18. ePlan Services
  19. Songkick
  20. Concluding thoughts

Frequently Bought Together

Specification by Example: How Successful Teams Deliver the Right Software + Impact Mapping: Making a Big Impact with Software Products and Projects
Price For Both: £34.79

Buy the selected items together


Product details

  • Paperback: 296 pages
  • Publisher: Manning Publications; 1 edition (6 Jun 2011)
  • Language: English
  • ISBN-10: 1617290084
  • ISBN-13: 978-1617290084
  • Product Dimensions: 23.4 x 18.8 x 1.5 cm
  • Average Customer Review: 4.6 out of 5 stars  See all reviews (8 customer reviews)
  • Amazon Bestsellers Rank: 168,446 in Books (See Top 100 in Books)

More About the Authors

Discover books, learn about writers, and more.

Product Description

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.


Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

Sell a Digital Version of This Book in the Kindle Store

If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store. Learn more


Customer Reviews

4 star
0
3 star
0
1 star
0
4.6 out of 5 stars
4.6 out of 5 stars
Most Helpful Customer Reviews
9 of 10 people found the following review helpful
Format:Paperback|Verified Purchase
This book is a tragically missed opportunity to sell Specification by Example into organisations.

Whilst brimming with "good ideas", Specification by Example ironically seems to lack the very thing that would make it more useful i.e. examples. Instead, the author, Gojko Adzic, relies on a series of quotes and opinions from interviews with research subjects in organisations that he identifies have adopted these practices. This is fine if you already "get" what the practices are about, but it doesn't really teach you how to go about doing it. Consequently, it's not a particularly engaging read.

One of the things that niggled at me throughout the book was the assertion that the primary goal is to automate your acceptance tests. He then goes on to suggest (from his research anecdotes) that this is actually very hard to do in a maintainable way. From personal experience, I would agree with this. So why set your readers up to feel they've failed?

My own experience has lead me believe that you don't have to automate your acceptance tests to get value from Specification by Example. Simply having requirements that stand up to the scrutiny of testing adds significant value and is something I have explored successfully with a number of teams. This has lead these teams to automate certain tests where appropriate and leave others to the domain of manual or exploratory testing.

The supporting practices explored in this book (including TDD and automated testing) are a hard sell in most organisations as there is a perception that they slow down delivery. Whilst this is an obvious over-simplification, the counter argument needs to be presented in more management-friendly language than is used here. A series of simple case studies would be more compelling than the quotes and vox-pops favoured by the author.
Comment | 
Was this review helpful to you?
2 of 2 people found the following review helpful
5.0 out of 5 stars Simple, straightforward and practical 27 Oct 2011
Format:Paperback
This book is great.
While as other reviewers have noted, it does not say anything "new" from a technical perspective, this is a great "glue it together" book, which focuses on bringing together the ideas of continuous integration while developing, and starting with example-based acceptance test driven stories and requirements to drive customer value and success in projects.
This is not a technical book, and reads simply and straightforwardly. To be honest, to such a point, that at the beginning, I was saying to myself "So what? I know all this" - but the great joy of the book is that it leads by example by using examples (case studies) to explain how to go about making the idea of continuously developed specification and test harnesses actually take root and flower within an organisation. As with all great user stories, it gives you the context and the criteria to prove success.
I would recommend reading this book with "Test Driven" (also Manning) and "the RSpec Book" (Pragmatic) to complete out a full, detailed view - and probably also recommend reading it with a decent requirements book (Wiegers), and a decent agile methodology book if you are starting out, as these will help you to flesh out the ideas within (maybe even "the Secret Ninja Cucumber Scrolls" for a Cucumber approach (wink)).
If I have but one criticism, it is that I do not recall an example for my situation - trying to influence multiple development suppliers to take on this approach (i.e. delivering to a central corporate client managing application delivery and support). Maybe the next update will contain this...
If I have but one piece of praise to single out, it is that I used the book just yesterday to talk about using some of the ideas contained within to improve reliability on a legacy system. I think "I use it" is the highest piece of praise you can give to such a book.
Comment | 
Was this review helpful to you?
2 of 2 people found the following review helpful
5.0 out of 5 stars Meeting customer's needs. 26 Oct 2011
Format:Paperback
The book is very helpful in emphasizing how important it is to understand customer requirements and how to get it implemented so it meets the customer's needs.
The author is very ambitious in defining new terms for terminology already given by others in the field of software development processes. But as the author puts it: Terms are not so important. It's the way how you live the process especially the requirements and testing process. How you name it is secondary and may be 3% of importance.
Good cooperation and open communication are most important part when developing software.
Living documentation is another identified key factor for success of software projects which is described in the book. Documentation is usually out of date as requirements change.
In Specification By Example the author describes the concept of executable specifications which are automated tests that read like documentation.
This kind of documentation is always up to date, because it's run daily against the software to test it.
I personally also love the idea that you should define the scope with the customer. Customers mostly have solutions in mind when they talk to a software company. Finding out what the customer's goals are and maybe even how to save the customer money is a key requirement for software companies these days.
Do not blindly follow customer requirements but consulting them. We have to thank Gojko Adzic
for putting together the experience made by over 50 companies around the globe when developing
software and writing it down in this well-organized book.
Comment | 
Was this review helpful to you?
Would you like to see more reviews about this item?
Were these reviews helpful?   Let us know

Customer Discussions

This product's forum
Discussion Replies Latest Post
No discussions yet

Ask questions, Share opinions, Gain insight
Start a new discussion
Topic:
First post:
Prompts for sign-in
 

Search Customer Discussions
Search all Amazon discussions
   


Look for similar items by category


Feedback