Any book that can assist project teams to get it right and on time at the projected cost has to be welcome. The recent debacles featured in the media have illustrated how inaccurate both software measurement and estimation can be. For many software project leaders the whole process of developing software is very much a “hit and miss” affair.
The authors have tried to bring some “science” and order into the whole process. Their approach may not please every engineer or manager but it is an ordered and structured one that can only benefit any software endeavour.
The authors start their thesis by introducing an approach that has much merit. They say it is new and tried and gives the reader information about how to make sound estimations. The emphasis given throughout is to the practical approach' promised by the book's title.
The authors do this by concentrating on the basics needed to be identified to reach a given level of performance. They begin by discussing measurement and the appropriate metrics as well as the necessary tools and methodology required to obtain the degree of both quality and performance.
It is obviously essential to review estimates and to change them as the targets set change. This means that the three critical constituents of the process: project timing, budget control and quality level are continuously monitored. The authors are well aware of this and help the reader in a practical way by introducing the necessary theoretical treatment and the techniques needed to tackle difficult estimation situations.
Throughout the aim is to take a practical approach and this is supported by the many examples which illustrate the strategies introduced.
The authors take a real‐life approach throughout and have chosen situations where the problems that arise are those faced by managers and engineers everyday.
There is also a message for management in the book. They should stay in touch with their software engineers who should be encouraged to supply progress reports at very regular stages of the project. Many of the software project failures reported in the press recently have shown so clearly that those who have initiated a project have simply been left in ignorance about its progress. Perhaps, this book will help to remedy this. Corporations should advise both their project managers and their software teams to study methods introduced in this worthy text.
