EUR 44,80
  • Tous les prix incluent la TVA.
Il ne reste plus que 9 exemplaire(s) en stock (d'autres exemplaires sont en cours d'acheminement).
Expédié et vendu par Amazon.
Emballage cadeau disponible.
Quantité :1
Specification by Example a été ajouté à votre Panier
Amazon rachète votre
article EUR 14,55 en chèque-cadeau.
Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir les 2 images

Specification by Example (Anglais) Broché – 9 juin 2011


Voir les formats et éditions Masquer les autres formats et éditions
Prix Amazon Neuf à partir de Occasion à partir de
Broché
"Veuillez réessayer"
EUR 44,80
EUR 25,36 EUR 74,95

Offres spéciales et liens associés


Produits fréquemment achetés ensemble

Specification by Example + Impact Mapping: Making a Big Impact With Software Products and Projects + Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation
Prix pour les trois: EUR 110,37

Acheter les articles sélectionnés ensemble



Vendez cet article - Prix de rachat jusqu'à EUR 14,55
Vendez Specification by Example contre un chèque-cadeau d'une valeur pouvant aller jusqu'à EUR 14,55, que vous pourrez ensuite utiliser sur tout le site Amazon.fr. Les valeurs de rachat peuvent varier (voir les critères d'éligibilité des produits). En savoir plus sur notre programme de reprise Amazon Rachète.

Détails sur le produit

  • Broché: 270 pages
  • Editeur : Manning Publications; Édition : 1 (9 juin 2011)
  • Langue : Anglais
  • ISBN-10: 1617290084
  • ISBN-13: 978-1617290084
  • Dimensions du produit: 18,7 x 1,5 x 23,5 cm
  • Moyenne des commentaires client : 2.0 étoiles sur 5  Voir tous les commentaires (1 commentaire client)
  • Classement des meilleures ventes d'Amazon: 39.254 en Livres anglais et étrangers (Voir les 100 premiers en Livres anglais et étrangers)
  •  Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?


En savoir plus sur les auteurs

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Dans ce livre (En savoir plus)
Parcourir les pages échantillon
Couverture | Copyright | Table des matières | Extrait | Index | Quatrième de couverture
Rechercher dans ce livre:

Commentaires en ligne

2.0 étoiles sur 5
5 étoiles
0
4 étoiles
0
3 étoiles
0
2 étoiles
1
1 étoiles
0
Voir le commentaire client
Partagez votre opinion avec les autres clients

Commentaires client les plus utiles

0 internautes sur 1 ont trouvé ce commentaire utile  Par check le 7 juillet 2014
Format: Broché Achat vérifié
Pa rapport au titre, ce livre ne montre pas les veritables examples de specifications. Il ne correspond pas à ce que je recherche. Je deconseille pour des personnes qui recherchent de veritables livres de specifications avec des vrais exemples.
Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
Merci pour votre commentaire. Si ce commentaire est inapproprié, dites-le nous.
Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 30 commentaires
20 internautes sur 21 ont trouvé ce commentaire utile 
"Specification by Example" with no examples 13 février 2013
Par Yuriy Zubarev - Publié sur Amazon.com
Format: Broché
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.
21 internautes sur 23 ont trouvé ce commentaire utile 
Standard Reference on Specification by Example and A-TDD 24 juin 2011
Par Bas Vodde - Publié sur Amazon.com
Format: Broché Achat vérifié
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 internautes sur 5 ont trouvé ce commentaire utile 
Informative, Pragmatic real-world recipes for agile success 2 avril 2012
Par Gishu Pillai - Publié sur Amazon.com
Format: Broché
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 internautes sur 10 ont trouvé ce commentaire utile 
CAUTION: This book could seriously improve the way you deliver software!!! 11 octobre 2011
Par A Spec by Example user "from the real world" - Publié sur Amazon.com
Format: Broché
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!!!
4 internautes sur 5 ont trouvé ce commentaire utile 
Succeeding with Agile and Quality 3 novembre 2011
Par AgilePro - Publié sur Amazon.com
Format: Broché Achat vérifié
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.
Ces commentaires ont-ils été utiles ? Dites-le-nous


Commentaires

Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?