Loggen Sie sich ein, um 1-Click® einzuschalten.
Jetzt eintauschen
und EUR 10,75 Gutschein erhalten
Alle Angebote
Möchten Sie verkaufen? Hier verkaufen
Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Keine Abbildung vorhanden

Den Verlag informieren!
Ich möchte dieses Buch auf dem Kindle lesen.

Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.

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

Gojko Adzic
5.0 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)
Preis: EUR 33,95 kostenlose Lieferung Siehe Details.
  Alle Preisangaben inkl. MwSt.
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
Nur noch 6 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon. Geschenkverpackung verfügbar.
Lieferung bis Donnerstag, 23. Oktober: Wählen Sie an der Kasse Morning-Express. Siehe Details.


28. Juni 2011
"Specification by Example" is a must-read for anyone serious about delivering software that matters. In it, author Adzic shares the secrets of how teams all over the world specify, develop, test, and deliver the right software, without defects, in very short iterative delivery cycles.

Wird oft zusammen gekauft

Specification by Example: How Successful Teams Deliver the Right Software + Impact Mapping: Making a Big Impact with Software Products and Projects
Preis für beide: EUR 41,50

Die ausgewählten Artikel zusammen kaufen

Kunden, die diesen Artikel gekauft haben, kauften auch


Mehr über die Autoren

Entdecken Sie Bücher, lesen Sie über Autoren und mehr


Ü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.

In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Hier reinlesen und suchen:

Eine digitale Version dieses Buchs im Kindle-Shop verkaufen

Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen. Weitere Informationen


4 Sterne
3 Sterne
2 Sterne
1 Sterne
5.0 von 5 Sternen
5.0 von 5 Sternen
Die hilfreichsten Kundenrezensionen
3 von 3 Kunden fanden die folgende Rezension hilfreich
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.
War diese Rezension für Sie hilfreich?
2 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Learn from teams around the globe 7. Juni 2011
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.
War diese Rezension für Sie hilfreich?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com: 4.4 von 5 Sternen  29 Rezensionen
17 von 18 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen "Specification by Example" with no examples 13. Februar 2013
Von Yuriy Zubarev - Veröffentlicht auf Amazon.com
One one hand, the book is not deep, reflective and well argued enough to be a timeless classic. One the other hand, it lacks concrete examples, steps and instructions to be a timely and actionable cookbook. It hangs in a midair between realms of inspirational and practical, touching on both and delivering on none.

I was really looking forward to read this book after hearing an interview with the author on Devnology podcast. It pains me to admit that reading it was not a time well spent. How could the author call his approach "Specification by Example" and offer no end-to-end examples that could be studied, evaluated and replicated? Please comment with a page number(s) for such examples if you disagree, and I will be more than happy to admit my blindness.
20 von 22 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.
5 von 5 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen Informative, Pragmatic real-world recipes for agile success 2. April 2012
Von Gishu Pillai - Veröffentlicht auf Amazon.com
The book was well organized and timely. Most teams swerve to the extremes of the test automation path... this book advocates striking a pragmatic balance between spotty automated test coverage and a plethora of maintenance-magnet technical tests. SBE is shown as a treasure map.. and then each checkpoint is elaborated in a chapter. Lot of real world knowledge collated in this book...

Key take-aways:
* Don't let customers dictate solutions, instead challenge and extract scope/solutions via collaboration.
* Don't make test automation your end-goal. Move on to living documentation (although I have no clue on how to convince teams of the benefits).
* Keep specs readable by business users.
* Adapt your test suites to the current reality.. Fast feedback is key even for acceptance tests.

Nitpicks: Could have been a shorter book. I realized I don't like reading about case studies... maybe others would like it. I strafed over Part III. and at 50$ a pop, the price is a bit steep.
8 von 10 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen CAUTION: This book could seriously improve the way you deliver software!!! 11. Oktober 2011
Von A Spec by Example user "from the real world" - Veröffentlicht auf Amazon.com
The concepts in this book, process patterns as Gojko describes them, seem quite straight forward and that's partly because they are, partly because they are very well described within and partly because they just make so much sense.

Its pages describe one of the most effective ways in which teams can build the right product and build that product right. Specification by Example harnesses some key attributes of agile frameworks such as Lean & XP in a mechanism that allows teams to get from business ideas to an implemented and evolving (self-documented) product with the minimum of fuss or waste.

What's more from the research undertaken with real teams in real companies, you the reader, can learn from the many other practitioners who have been using and honing these techniques in the field (that's a real field by the way, with grass and everything).

I think it's rare to get this amount of good practical advice from so many teams distilled into a single reference guide alongside the process.

A fantastic book which should be the accompaniment of every software team member!!!
2 von 2 Kunden fanden die folgende Rezension hilfreich
1.0 von 5 Sternen No practical value 30. Januar 2014
Von alex__ - Veröffentlicht auf Amazon.com
This book is not much more than a collection of case studies. I found nothing in the book that can be used to apply "Specification by Example" in a real-world project. There are no detailed examples of code or documents, just generalities and stories about the benefits of the author's approach. I feel that both money spent on buying the book, and time spent on reading it were simply wasted.
Waren diese Rezensionen hilfreich?   Wir wollen von Ihnen hören.
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Erster Beitrag:
Eingabe des Log-ins

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen

Ähnliche Artikel finden

Ihr Kommentar