An effective, quantitative approach for estimating and managing software projects
How many people do I need? When will the quality be good enough for commercial sale? Can this really be done in two weeks? Rather than relying on instinct, the authors of Software Measurement and Estimation offer a new, tested approach that includes the quantitative tools, data, and knowledge needed to make sound estimations.
The text begins with the foundations of measurement, identifies the appropriate metrics, and then focuses on techniques and tools for estimating the effort needed to reach a given level of quality and performance for a software project. All the factors that impact estimations are thoroughly examined, giving you the tools needed to regularly adjust and improve your estimations to complete a project on time, within budget, and at an expected level of quality.
This text includes several features that have proven to be successful in making the material accessible and easy to * Simple, straightforward style and logical presentation and organization enables you to build a solid foundation of theory and techniques to tackle complex estimations * Examples, provided throughout the text, illustrate how to use theory to solve real-world problems * Projects, included in each chapter, enable you to apply your newfound knowledge and skills * Techniques for effective communication of quantitative data help you convey your findings and recommendations to peers and management
Software Measurement and A Practical Approach allows practicing software engineers and managers to better estimate, manage, and effectively communicate the plans and progress of their software projects. With its classroom-tested features, this is an excellent textbook for advanced undergraduate-level and graduate students in computer science and software engineering.
An Instructor Support FTP site is available from the Wiley editorial department.
Metrics around software can be a difficult to attain. Some (Agile) suggest making up estimates and then making metrics based off of those estimates. Others (function points) build entire abstract schemes based on difficult-to-attain calculations. Either way, predicting and measuring progress are complex tasks, but they are necessary to communicate to management and to provide appropriate managerial oversight. In this book, the authors seek to provide practical methods to assure that projects are on track and as advertised.
The collection of metrics span everything from estimated schedules and benchmarking to understanding financials and measuring complexity. Math equations, graphics, and tables to reason from fill the text. It's more of a reference book than a how-to manual and offers plenty of options for a software manager to think through.
This book is suitable for advanced engineers and managers who want to master all aspects of a project. Though it's a bit dated by not mentioning Agile techniques, it's not overly simplistic - a failure, I contend, of many Agile texts. I doubt anyone would use all the material in one project, but it helps to see the many measurement options available in one place.
I really enjoyed this book! I thought this was a concise (and fairly comprehensive) treatment of the measurement and estimation of software. My biggest complaint is the lack of a solution key to the questions.
Ms. Laird does an excellent job of detailing the various aspects of measurement (e.g. what it means to measure something, how best to measure it, what kind of measurements software has), as well as tying these in to current research. This book has made it much easier to enhance my knowledge merely from its bibliography and frequent citations. Moreover, since empirical data is most important, seeing these citations gives me assurance of the validity and veracity of the author's statements (to some extent, at least).
I'd give this a 9.0/10, but I'll round up to 10/10.