Software Metrics: Establishing a Company-Wide Program

All about what motivated the Hewlett-Packard company to get involved in a software development metrics program. This is not a how-to book, but good background for thinking about why you would want to measure software development work rather than just doing it. If you want to learn more about metrics, try this online course: [...]

Its not your typical review that begins by praising the book's bibliography. But, then again, this isn't your typical book. The authors highlight the books that helped them most during their efforts both to create the metrics program and write the book (some 31 sources) followed by the citation of some 185 more sources listed alphabetically. This is a thoroughly researched work. Don't confuse thorough with academic or theoretical. Included is a whole chapter on selling your metrics program to management including suggested slides and a clear step-by-step list of points to emphasize. A metrics program is as much about people as it is about software and this books is careful to support ideas on both flanks. If you are interested in starting a metrics program or are just interested how such programs work this is an excellent place to start. I highly recommend it.

This book, written in 1986, is as applicable today as it was when it was written over 14 years ago. To summarize, this book is a diary of the trials and tribulations of implementing a metrics program at Hewlett-Packard that is packed with practical advice that came from lesson's learned and a great roadmap to implementing a program of process improvement. The book addresses the difficulties and rewards of establishing an effective, viable metrics program. The authors clearly show the business and technical value that rewards the daunting effort, and guides the reader by providing an engaging saga that is easy to read packed with factual information. I was also struck by the excellent use of [the 144] charts that convey meaningful statistical information and portray data in a clear manner. Another nice surprise is the attention paid to metrics and how to effectively interpret and use them after a project transitions to production. Although I first read this book when it was originally published, it took 14 years of experience in the trenches to fully appreciate the message and content embodied within this book. I strongly recommend this book to the beginer and exerienced practitioner alike. If you have previously read this book I urge you to re-read it. Over the years I have learned and re-learned from this slim (288-page) book. I expect to spot additional gems of insight as I re-read it in the future. If you by one book on software metrics and process improvement, this is the one to get!