|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt Specification by Example: How Successful Teams Deliver the Right Software gegen einen Amazon-Gutschein in Höhe von EUR 15,10 ein - einlösbar für Tausende von Artikeln bei Amazon.de. Entdecken Sie mehr eintauschbare Bücher im Bücher Trade-In Shop. Bitte beachten Sie die Teilnahmebedingungen.
 Jetzt für Amazon Student anmelden und um 20% erhöhten Eintauschwert sichern. |
Wird oft zusammen gekauft
Produktinformation
|
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von Gojko Adzic auf Amazon
› Besuchen Sie die Seite von Gojko Adzic auf Amazon
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
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
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
1 von 1 Kunden fanden die folgende Rezension hilfreich
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.
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.
1 von 1 Kunden fanden die folgende Rezension hilfreich
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.
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.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
22 Rezensionen
12 von 13 Kunden fanden die folgende Rezension hilfreich
Standard Reference on Specification by Example and A-TDD
24. Juni 2011
Format:Taschenbuch|Von Amazon bestätigter 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.
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.
4 von 4 Kunden fanden die folgende Rezension hilfreich
CAUTION: This book could seriously improve the way you deliver software!!!
11. Oktober 2011
Format:Taschenbuch
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!!!
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!!!
3 von 3 Kunden fanden die folgende Rezension hilfreich
Succeeding with Agile and Quality
3. November 2011
Format:Taschenbuch|Von Amazon bestätigter 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.
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.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
