Amazon calculates a product’s star ratings based on a machine learned model instead of a raw data average. The model takes into account factors including the age of a rating, whether the ratings are from verified purchasers, and factors that establish reviewer trustworthiness.
If you or your team are involved in building software then this book is highly recommended. Be prepared to approach the book without holding on to your existing notion of how software is built because this thinking can make you change the way you approach and execute software development.
Who are the intended readers? 1. Managers who are accountable for delivering software. If you oversee delivery of software from conceptualization all the way to deployment to production, then this book is something worth every minute of reading time. In fact, the recommended practices here do benefit long term total cost of ownership of the software which your clients (internal or external) can benefit from (perhaps your career too). 2. Business Analysts, Testers and Programmers are also targeted readers because these are the key roles that contribute to the success of the software delivery team.
This is not just another book evangelizing a thesis, but the later chapters give you key takeaways on what the exact tools are recommended to implement it. Although you should not treat that list of tools as the final list because this book is already 'old' as far as that list is concerned today, instead go to Adzic's website to see a more up to date list of tools recommended. Even without the tools, the lessons advocated in this book are classic teachings on software quality -- that we should start addressing good quality software before we even start writing the first line of code.
Agile software development is a game changer some years back but it remains to be an approach that folks are uncomfortable with in traditional organizations with established "tried and tested" methodologies. This book will add further justification on why you should go agile. If you are doing agile now, then this book will improve on that practice further which can help you convince your stakeholders to side with you on the agile movement.
This is a review from somebody who actually wrote code for a living and managed software delivery for years.
Message of the book is introduction to communication and discussion to discover missing (stories/hidden assumptions) + clearing between teams in organization (many teams).
It's very useful for anyone first step in Agile and need to know difference between tradition and new wave. This book does not mention tools for automation however it is enough to find automation that conformity and approciate to Agile team.
"Document is nothing, documenting is everything" - this quote book is impressed to the most value are communication and concensous/commitments.
"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!
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.
I think this is a must read for anyone involved in a software development project. I love how it teaches you specification by example as a concept and philosophy to be learned by all parties involved before thinking of using any kind of software tool to automate it.
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.
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.
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.