Facebook Twitter Pinterest
  • Alle Preisangaben inkl. MwSt.
Nur noch 4 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon. Geschenkverpackung verfügbar.
Menge:1
Bridging the Communicatio... ist in Ihrem Einkaufwagen hinzugefügt worden
Gebraucht: Gut | Details
Verkauft von FatBrain
Zustand: Gebraucht: Gut
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

Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing (Englisch) Taschenbuch – 5. Januar 2009

5.0 von 5 Sternen 4 Kundenrezensionen

Alle Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Preis
Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
Taschenbuch
"Bitte wiederholen"
EUR 29,95
EUR 20,48 EUR 12,80
8 neu ab EUR 20,48 6 gebraucht ab EUR 12,80
click to open popover

Wird oft zusammen gekauft

  • Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing
  • +
  • Specification by Example: How Successful Teams Deliver the Right Software
  • +
  • Fifty Quick Ideas to Improve Your User Stories
Gesamtpreis: EUR 106,80
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.



Produktinformation

Produktbeschreibungen

Über den Autor und weitere Mitwirkende

Gojko Adzic was bitten by the specification-by-example bug five years ago. He has helped numerous teams implement these practices, 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.


Kundenrezensionen

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

Top-Kundenrezensionen

Format: Taschenbuch Verifizierter Kauf
Das Buch ist ein Muss für Alle, für die die Kommunikation zwischen den unterschidlichen Gruppen in einem Projekt ein wichtiges Thema ist und was dazu lernen möchten. Es ist einfach zu lesen und der Author hat es in einer sehr einfachen und direkten Weise geschaft, die Problematik erklären und anzugehen.
Kommentar 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
In this great book Gojko explains how to overcome the gap between the technical viewpoint of Software Development and the customer perspective. By bringing together the whole development team from the beginning of the project, fewer misunderstandings of business needs can be achieved. For this reason he introduces Specification Workshops and Requirements by Example, that enable teams to start right from the beginning on the right foot and reduce necessary rework to achieve a mutual benefit for the business and the development team.

In Bridging The Communication Gap Gojko discusses topics about requirements, Agile acceptance testing (ATDD), user stories as well as tools for specification by example. He gives a compelling overview into each parts. For the requirements part, specification workshops alongside with requirements by example build the basis for measurable and executable requirements. Gojko gives an overview on the Agile Acceptance Test cycle, and explains where it fits into the Agile development cycle. As user stories are the standard way to introduce new features in Agile projects, he also discusses their role in the ATDD cycle. On the tools in use today, he shows the most commonly used (as by 2008/2009) - FIT, FitNesse, Concordion, TextTest, JBehave and Selenium - and where the development of the tools from tomorrow are most likely to go. Last he takes a closer look on impacts of his approach on different roles in the software cycle - customers, developers, testers and business analysts.

This book is a must read for anyone struggling with requirements and acceptance testing. It shows how to a working approach, which Gojko applied several times on his consulting job. He wrote this book based upon his compelling experience helping organizations and teams with test automation and Agile testing.
Kommentar 6 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: Kindle Edition Verifizierter Kauf
Ein sehr gutes Buch zu diesen Themen, adressiert genau die heißen Themen und gibt hilfreiche Tipps mit praktischer Relevanz. Sehr lesenswert!
Kommentar 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 Verifizierter Kauf
Easy to read.
Contains Background and examples.
The practices are described in a way that they can be applied in daily routine.
Kommentar 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: HASH(0x9ea0e900) von 5 Sternen 7 Rezensionen
12 von 12 Kunden fanden die folgende Rezension hilfreich
HASH(0x9d305240) von 5 Sternen Much needed book. 18. Juli 2009
Von Bas Vodde - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
"Bridging the communication gap" by Gojko Adzic is a much needed book on a very important topic that finally is deserving the attention it needs: Agile acceptance testing. This practice is also known as "automated acceptance testing" or as "acceptance-test-driven development." It has evolved over the last decade, but was known and used in a relative small group. Every year there would be a couple papers on the topic, Lasse Koskela covered it a bit in his "Test-Driven" but now finally Gojko takes the subject further and devotes a whole book on it.

What is it? Agile Acceptance Testing is a technique for closing the communication gap between business, developers and testers. A way to write specifications as examples which become executable. The specification are created together in a workshop and not handed over like traditional requirements.

The book is written in four parts. The first part is an introduction to the topic, describes an overview of the technique. An important part of this part (and the whole book) is the focus on communication instead of test. This is reflected in the excellent discussion about naming. Agile Acceptance Testing is perhaps one of the most poorly named practices, but... still... thats the name it became popular with (or with A-TDD). The second part is the most important parts of the book, which describes how to write specifications, why to work with examples, how to run specification workshops and what to do after these workshops. The part ends with a discussion about change in projects and how the automated acceptance test help with that.

The third part discusses implementation. It starts with how to fit this technique in an iteration and how to adopt the practice. Next is a chapter on user stories and its relationship with acceptance tests. Then the part dives in the tools by first covering the current tools and then discussing the requirements for the future tools. The last part of the book describes the impact of agile acceptance testing on the different functions: business analyst, developer and tester.

Bridging the Communication Gap is a small book (300 pages) and is easy to read. It could have been smaller, the writing is sometimes a little too wordy. It doesn't contain too much pictures, which is too bad when a book talks so much about workshops. Yet, despite these drawbacks, I think this is an excellent book and a much needed contribution to the modern software development/agile development literature. It was one of the few practices that did not have its own book yet and Gojko provided that.

I was doubting between 4 and 5 stars for this review. 4 because this book is certainly not perfect. 5 stars because it is good still. Because this is a first in a new area and because I consider this an important area, I decided to go for 5 stars. This will certainly be a book that I will be recommending to other people (and in fact, I already have). Great work Gojko!
11 von 11 Kunden fanden die folgende Rezension hilfreich
HASH(0x9d524e64) von 5 Sternen Delivering Value - a cultural shift 30. Januar 2009
Von Lisa Crispin - Veröffentlicht auf Amazon.com
Format: Taschenbuch
Teams transitioning to agile development tend to focus on process rather than values. But you can't simply master a set of practices and be successful. Your whole team needs to understand what your business needs so you can deliver value. Your whole team needs to commit to creating a quality product.

This book not only explains how to use examples to understand requirements and create tests that drive coding, it explains the cultural shift needed for successful software development. The author explains the communication gap, why we should care about it, and how we can fix it.

Whether you're new to agile development, or are on an experienced team wondering why you keep missing or misunderstanding the business requirements, this book delivers critical value.
4 von 5 Kunden fanden die folgende Rezension hilfreich
HASH(0x9d524da4) von 5 Sternen Bridging IT worlds. 21. März 2013
Von Amazon Customer - Veröffentlicht auf Amazon.com
Format: Kindle Edition Verifizierter Kauf
One of the first lessons of the book is that we in IT should pay more attention to the marketing of our methods.
Thet second big lesson that the book describes is how specifications can me made more clear by working together as a team and saving lots of time when we store the specifications in testing tools in a format that customers can read and understand.
HASH(0x9d305960) von 5 Sternen Excellent concept and practices to improve requirements definition 4. Januar 2014
Von Chris Crafford - Veröffentlicht auf Amazon.com
Format: Kindle Edition Verifizierter Kauf
The concept of using real world examples that explicitly validate expected business outcomes of a product feature is both practical and very powerful. Crystalizing out the process details to do this in an Agile development cycle is what this book does, and it does it well.

Personally I find the style of writing rather dry so pushing ahead through the material takes some commitment, but it is worth it. The lessons, techniques and value of the results provide an excellent payoff.
HASH(0x9d524f84) von 5 Sternen Great guide! 30. September 2015
Von CollinK - Veröffentlicht auf Amazon.com
Format: Kindle Edition Verifizierter Kauf
This method of agile acceptance testing for specifying requirements is specific and so thoroughly helps to communicate what is being talked about and agree on it - it really is useful to all parts of the project and implementation. Gojko gives good examples and summaries of techniques and makes the process clear.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.