I think this book can be the most anticipated book of this year in my personal list of books which must be read.
This book already gives really good impressions, its written by somebody who active in the field.
Author telling from the beginning, that there a lot of errors in the way how we measure the quality of code.
Author of this book describe day to day activities which help to gather data for further analysis.
There different tables presented with measure of different software development tasks.
Author many times mentions, that coverage by line not always provide insights about code quality, it more like guideline, but it never provides overall impression of code quality.
Reusable components are interesting topic, Author of opinion that many times companies ignore which influence such components have on overall efficiency.
I like how author present different data in table format, it clearly outlines the problems with measuring.
IBM actually doing great work, so it’s seeming by what the Jones claims.
Author of the opinion that accuracy is hard to measure and even to proof, I totally agree with this statement.
International Software Benchmarking Standards Group (ISBSG) and other are mentioned too.
Oh yes the famous productivity analysis, book author describe that there exist different metrics and yet productivity is hard to measure , because it depends on what actually productivity for one or another company really means can be very different.
Summary: This book is a collection of reflections on the data which was gathered by the author, but I hardly can define it as guide for selecting benchmarking software, yes you can find in this book some good examples on how to measure software quality , but in my opinion this book main goal to be a source for reference if you need proofs of one or another quality maintaining ideas , otherwise it make no sense, I can hardly recommend this book to anyone who doing practical day after day work in QA or development.