This book is a succinct summary of what we know about software quality and how to apply it. It can be read in "agile time", and delivers a solid overview that can set readers on course to higher quality, lower risk software. This book is a valuable contribution to professional software engineering practice. Half of the book is devoted to agile quality techniques. Ben’s objective is to make sure the speed of delivery is matched by the speed of assurance.

What Drives Quality by Ben Linders provides an extremely valuable perception to its readers on how to deal with the development process, verification and validation activities in contemporary software development processes. Localizing and applying the practices discussed by Ben will significantly add to the level of maturity that is needed to ensure software quality in your own organization. This book a must-read for every software professional!

What Drives Quality" was a delight to read. It flows well. It is about a lot more than software quality, touching on many of the ideas that have been tried and true for quality in general. Ben Linders has a charming style of writing that is both challenging and thought provoking. I recommend the book for anyone who wants to achieve quality or wants to avoid being the victim of self-inflicted or other quality issues.

Congratulations on putting together a veritable index of various resources related to understanding aspects that drive quality in a software development lifecycle. This is a must-read for all persons contributing to the development or enhancement of software.

Ben’s book is a reflection of his deep knowledge and experience helping teams and organisations identify what quality is in software, why it matters and how to optimise the right qualities for a product. He explores how quality is impacted by the organisational processes and from the perspective of the individual contributor, and gives concrete, tangible advice on how to make better products which meet customer needs effectively. He does this in an entertaining and interesting writing style.

What Drives Quality is a one stop shop reference for software development and testing practitioners. Ben Linders shares highly useful and practical guidelines and recommendations that can help drive quality based decisions into any organization that is maturing its software development process. In addition, the book offers experience based case studies and pointers that can help the readers drive better quality into their agile practices.

This interesting book is a welcome addition to the agile literature. Ben's book also covers testing and other forms of software defect removal. Ben's book is somewhat congruent with my own older book, "The Economics of Software Quality". Up until Ben Linders' book agile averaged about 92.5% in removing bugs. Hopefully the tips and advice in Ben's book can raise agile DRE up above 97% which is the range of the TSP methodology. Overall Ben's book has good advice about improving software quality.

This book is a lovely collection of ideas for anyone looking to to improve their software development process.

Many pieces of useful advice in an easy-to-read book.

Ben's book is practical and actionable. It's a great foundation for agile beginners and also full of resources for advanced practitioners. I am already using the ideas in my coaching work with teams and their executive leaders.

The book What Drives Quality provides a comprehensive and multi-faceted overview of how to increase the quality of software products. Whether you are a manager, programmer, programmer, or (naturally) a tester, this book will provide you with plenty of meaningful and practical ways you can enhance and drive quality at your organization. The book is generously sprinkled with links to articles and books that will help you dive deeper into the discussed topics.

This book is a roadmap to better software with advice for people at all levels of the organisation. I love that it’s not only based on agile practices, but also on what works in the field. Go buy it!

Great content, full of do's and don'ts. It looks at quality and why it is so important to understand the customers' needs before deciding which approach to take. I enjoyed reading it and would recommend it to anyone who has an interest in software quality

I like the fact that, finally, requirements practices are recognized in the book as part of quality. As an agile coach I give a lot of attention to them. And of course, the concept of the team as described in the book, which is an important driver for quality. i will recommend the book for sure.