Facebook Twitter Pinterest
EUR 35,95
  • Statt: EUR 39,99
  • Sie sparen: EUR 4,04 (10%)
  • Alle Preisangaben inkl. USt
Nur noch 11 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon. Geschenkverpackung verfügbar.
Specification by Example:... ist in Ihrem Einkaufwagen hinzugefügt worden
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Hörprobe Wird gespielt... Angehalten   Sie hören eine Hörprobe des Audible Hörbuch-Downloads.
Mehr erfahren
Alle 3 Bilder anzeigen

Specification by Example: How Successful Teams Deliver the Right Software (Englisch) Taschenbuch – 28. Juni 2011

5.0 von 5 Sternen 2 Kundenrezensionen

Alle Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Neu ab Gebraucht ab
"Bitte wiederholen"
EUR 35,95
EUR 30,00 EUR 34,98
46 neu ab EUR 30,00 12 gebraucht ab EUR 34,98
click to open popover

Wird oft zusammen gekauft

  • Specification by Example: How Successful Teams Deliver the Right Software
  • +
  • Fifty Quick Ideas to Improve Your User Stories
  • +
  • Fifty Quick Ideas To Improve Your Tests
Gesamtpreis: EUR 118,43
Die ausgewählten Artikel zusammen kaufen

Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.

  • Apple
  • Android
  • Windows Phone

Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.

Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.



Über den Autor und weitere Mitwirkende

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.

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


5.0 von 5 Sternen
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Stern
Beide Kundenrezensionen anzeigen
Sagen Sie Ihre Meinung zu diesem Artikel


Format: Taschenbuch
In this book Gojko collected stories from more than fifty teams all around the globe. After his second book Bridging the Communication Gap Gojko made field studies with teams appyling Acceptance Test driven development. Gojko provides guidance from his collection on what to try and to avoid when starting with Specification by Example - formerly known as Acceptance Test-driven development (ATDD). Gojko shares not only his own experience, but the collected experience of all these teams, thereby providing a thorough body of knowledge on Specification by Example, and what teams did to apply it successful in their particular context.

Gojko covers Specification Workshops, in which teams gain a shared understanding about the features to be implemented. He continues to explain how to derive relevant examples as a specification for the software. While the code is implemented, these examples are automated to the letter, so that an executable specification evolves. Over time a living documentation is created, eventually leading to a well maintainable software system.

Gojko abstracts from the particular tools that support Agile friendly test automation. Instead he explains the approaches that different teams took, and which trade-off decisions they were faced with, and which lessons they learned. By sharing these lessons you can avoid most common mistakes. This book reflects the current state of the art of Specification by Example, and the content comes close to the classic Design Patterns book by Gamma, Helm, Johnson, and Vlissides.
Kommentar 4 Personen fanden diese Informationen hilfreich. War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Missbrauch melden
Format: Taschenbuch
No matter if you are just starting with ATDD and specification-by-example or already practicing it: this book provides a wealth of experience from teams around the globe to learn from.

Independent of the specific tools that were used, Gojko identified and described common challenges teams were facing and solutions they found as well as common patterns teams applied successfully.

For beginners this book will give a head start into the topic. Note, however, that this book is not a beginner's guide. Reading Gojko's first book, 'Bridging the Communication Gap', is a useful supplement for getting started.

Practitioners will find both confirmations to already found patterns and solutions as well as new inspiration to improve their practice.

The book is also very suitable for convincing decision makers who want see evidence about ATDD and specification-by-example applied in different organizations.
Kommentar 2 Personen fanden diese Informationen hilfreich. War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Missbrauch melden

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 4.5 von 5 Sternen 35 Rezensionen
4.0 von 5 Sternen Holy grail for requirements, test automation and documentation 26. Februar 2014
Von Pirkka Rannikko - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
This book describes one kind of a “holy grail” for software requirements, test automation and documentation: Stakeholders and developers in collaboration derive requirements from business goals, specify them through examples and automate their validation thus creating a living documentation of the system.

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.
1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Essential reading for the modern practitioner 26. Oktober 2011
Von Bjorn Rasmusson - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
The heart of the practice Specification by Example is the unification of specifications and tests. This unification guides development teams to avoid several of the common anti-patterns in software development; like testing bolted on at the end, and documentation getting out of sync with the implemented functionality.

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.
5.0 von 5 Sternen Examples to use on projects 3. Oktober 2011
Von Brian Levy - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
Specification By Example is an easy read and introduction into methods for using example driven acceptance tests in place of requirements documents. The great thing about the book is that it not only provides practical explanations of how to begin specifying examples, but also how to explain its importance to management. I used some of the explanation in the book on my current project, and it worked! This was just the lever that I needed to convince the client to make the change. I would definitely recommend this book to others who are interested in better forecasting, better group dynamics, and more coordination on their teams.
4 von 5 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Succeeding with Agile and Quality 3. November 2011
Von AgilePro - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
So many organizations that do 'Agile' don't understand that there is a process by which teams need to work in order to understand what they are building. Having led many organizations through this effort I had developed many of the types of processes that are presented in this book, but Gojko has provided guidance around all the many types of projects that teams face while trying to be Agile on top of it.

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.
23 von 27 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Standard Reference on Specification by Example and A-TDD 24. Juni 2011
Von Bas Vodde - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
Specification by Example is Gojko's third book on this subject. The first book, Fitness.net, was very technical and tool oriented. The second book, Bridging the Communication Gap, was a lot more coordination oriented. Now his third book, this one, he describes practices that teams he studied have used. From that perspective, this book is the follow-up of Bridging and might go a little fast if you are totally unfamiliar with the subject.

The book is divided in three parts. The first part is mainly introduction where Gojko describes the benefits and the key practices that will be described in this book. The second part is the actual description of the key practices and the third part are different case studies about different teams in different companies that have adopted specification by example.

The key practices that are introduced in part one and described in part 2 are:
- Deriving scope from goals
- Specifying collaboratively
- Illustrating using example
- Refining the specification
- Automating without changing the specification
- Validating frequently
- Evolving a documentation system

Deriving scope from goals discusses how customers main concert is not the software but solving a problem and developers shouldn't just expect to get the requirements from the customer but work together with them to help them to solve their problem in the best way. Specifying collaboratively covers how the customer and the teams will cooperatively define the specifications that the team will be implementing later. Illustrating using examples explains how these specifications can be described best by moving from abstract requirements to concrete examples. Refining the specification then takes the essence out of the requirements and describes them in the clearest possible way. After that, the specification can be automated without changing the specification and this chapter gives tips on how to do that. When the specifications are automated, you want to run them frequently which is described in the validate frequently chapter. Evolving a documentation system describes how the specifications become the documentation of what the system does. They stay in-sync with the system because they are continuously executed.

The third part described a couple of case studies of companies that implemented specification by example. I really loved these case studies and they were written very well.

I've read both of Gojko's earlier books and had high expectations for this book. I was not disappointed, it is an excellent follow-up and will be my standard book reference on Specification by Example (or A-TDD as it is also called). The book is not perfect though. As times I felt there was too much focus on documentation and too little on collaboration. Still, I'd rate this book five stars and recommend everyone in an Agile development team to read this and practice specification by example.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.