Customer Reviews

The Capability Maturity Model: Guidelines for Improving the Software Process

5 star:		(8)
4 star:		(4)
3 star:		(1)
2 star:		(0)
1 star:		(2)

 

 

At one time this was the definitive text on the CMM, but is rapidly showing its age because of the new CMMI suite that the Software Engineering Institute is developing. For reference the CMMI (Capability Maturity Model Integration) is an effort to integrate maturity models for software, system engineering and integrated product development).

This book is the one that introduced the CMM to the masses and is what is now called the CMM-SW (SW=Software). It is still a valid reference for software-only organizations from a key process area point of view. As such, it still has value to any organization that is striving to attain CMM level 2 or above. If you're new to the CMM (and there are many who are), this the CMM is five levels of capability maturity, when chaotic organizations assumed to be at level 1. It is not a methodology, so do not expect to find any "how to" information in this book. What you will find in this book is a description of the CMM itself and its structure, and key process areas that need to be in place in an organization for each level of the model. Each key process area has associated key practices.

In a nutshell, the CMM is a benchmark. The key to achieving level 2 or above requires a commitment to perform. This book will tell you what processes need to be in place, and what the key practices are for each process, but will not tell you which methods to use. It's dry reading, but there is no ambiguity in the descriptions, which makes this book a valuable reference if you are involved in a company-wide CMM initiative. If your goal is to explore the value and benefits of the CMM, then I recommend A Guide to the CMM by Kenneth Dymond as a better place to start. Despite its age and the CMMI initiatives this book still merits 5 stars for those who are actually implementing the CMM for software.

This book gives a very thorough description of the CMM, its key processes and levels. However, it does not give practical advice on implementation. I would not recommend this book to the beginner just starting to explore the CMM - it is better for someone with a basic understanding who wants an in depth description. The charts and graphs are completely unhelpful, in many cases I could not figure out exactly what the graph was supposed to illustrate. The use of the space shuttle project as a level 5 example is also not very applicable to the average business or software development house in determining their CMM level. A very good academic book and one that should be read if you are planning to implement CMM, but get a basic foundation using simpler books or training before tackling this one.

This is a complete description of the Capability Maturity Model for software from SEI/CMU. The big issue of the book, and the model itself, is that it describes widely what has to be done, but no clue of how to do it. This flexibility is very good to one who has been working with the model for so long, but very hard to news fellows to interpret by themselves.

This book is an excellent reference for anyone studying the SEI/CMM framework. It is excellent if you are a beginner or an old timer in the world of process improvement. This is by far the best book written by the Watts Humphrey group. I received this book at 4:00pm, cracked it open at 7:30pm and did not put it down till 11:00pm. The style, and approach makes this book enjoyable, YES enjoyable to read. Some critics have been too harsh on the CMM model and try to dismiss it. These same critics then try to explain that CMM is a waste of time,and praise RUP/UML. This is not so. SEI/CMM establishes the framework that gauge success in a software organization. Methodologies such as RUP/UML, and Structured Analysis and Design support the CMM and its Key Process Areas. There is no conflict, only support. Think of the CMM KPA(s) as the "what" and the methodologies as the "how". Kudos to the authors in their continuing efforts to teach the software community about process improvement.

You've come to the right place, this IS the CMM. As a model it is complete. This book does not take into account the miriad of political obstacles, but for those software groups that are seriously ready for continuous software improvement, this is the source of what to do. There are other great books, such as the one by Kim Caputo, that give more specific ideas about implementation. Obtaining CMM compliance takes a lot of research and careful planning to get the job done, after all, it is all process and doesn't happen overnight or in a vacuum.

This book is an excellent reference for everyone. Whether you're in the beginning stages of defining a software process and it's improvement or already have a well-defined process in place. This book gives you the guiding steps to becoming SEI - CMM compliant regardless of your platform. If you want the recognition of having well-defined processes that improve your software quality which in turn brings better customer retention and even increased sales - you want the CMM process and this book!

Excellant reading for anyone in software, especially for those in software quality and project management. Greatly helps understanding of the software process. Gives the basic concepts of the CMM and in-depth understanding of each KPA. Includes implementation guidance. Also discusses ISO & SPICE project.

The book offers a way to impose discipline on the entire software development process. It targets large software projects, where there are numerous programmers, and where the eventual code base might number millions of lines. The CMM may let you manage a scaling of effort that can yield a successful project, on time and on budget. No guarantees, mind you. But Carnegie Mellon's authors have extensively studied this field and their advice is generally considered sound.

The text is deliberately written as a set of lists, where a list consists of tasks to be done. This is not a book you necessarily read for insight. A book of lists, come on! Rather, you have some experience with CMM, from other texts or live instruction. And you then use this book for specific tasks. This is a reference book, like a dictionary, if you will.

This book was seminal in the study of the maturity of the software development process within an organization.

Even though the model has been revised, this is still a good book and an excellent place to start if you are going to be involved in CMM(I).