A Guide to the Cmm: Understanding the Capability Maturity Model for Software [Spiral-bound]

Kenneth M. Dymond (Author)

Product Details

• Spiral-bound
• Publisher: Process Inc U.S. (April 1995)
• Language: English
• ISBN-10: 0964600803
• ISBN-13: 978-0964600805
• Product Dimensions: 8.9 x 8.8 x 0.7 inches
• Shipping Weight: 1.2 pounds
• Average Customer Review: 3.9 out of 5 stars  See all reviews (9 customer reviews)
• Amazon Best Sellers Rank: #2,540,824 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

26 of 27 people found the following review helpful:

5.0 out of 5 stars Great intro to CMM, August 31, 2000

By 

Michael R. Brown (Tamarac, FL) - See all my reviews

This review is from: A Guide to the Cmm: Understanding the Capability Maturity Model for Software (Spiral-bound)

If you need to understand the CMM, this is the book for you. Don't look for this book to justify why your organization should use the CMM, there are other sources for that.

And despite what "James McGovern" claims, the CMM is backed up by several years of real world use. Over 1000 organizations in 19 countries have used the CMM. Many companies, large and small, use it. My company has mandated it as a corporate goal.

12 of 12 people found the following review helpful:

5.0 out of 5 stars Clearly explains the CMM - best intro book on the topic, July 3, 2001

By 

Linda Zarate "IT Ops Consultant" (Azusa, CA United States) - See all my reviews

This review is from: A Guide to the Cmm: Understanding the Capability Maturity Model for Software (Spiral-bound)

If you want a no frills book on the CMM get Mark Paulk's "The Capability Maturity Model", which is authoritative and written by one of the principal developers. However, if you want a more readable book that explains the CMM this is the best I've read.

This 350-page book is comprised of five chapters and two appendices. Chapter 1 covers the basic concepts and structure in clear terms. Chapters 2 through 5 are devoted to capability levels 2 through 5. Each chapter covers the key process areas of the level that it discusses and its applicable practices, and ends with a summary view of process assets and relationships between and among the key process areas at the particular level. There are also exercises at the end of each chapter to reinforce the material and check your understanding. I like this approach because with 316 practices you can quickly lose track of what's where within the CMM.

So why the CMM? Some claim it's a hindrance. First, it does not tell you how to run your organization, only how mature your organization is based on key processes and practices that you employ. Your maturity level is indicative of the efficiency (read: cost effectiveness) or your organization and probable quality of the software you produce. Those who claim it's a hindrance, I suspect, really lack the discipline and/or leadership to achieve a level of maturity beyond repeatable - if that. But the underlying reason to pay close attention to the CMM, or at least understand it, is because there is a lucrative business called litigation. If you find yourself involved in product liability litigation you're going to hear terms like "prevailing standard of care" and "what a reasonable member of your profession would have done". Considering the fact that well over a thousand companies world-wide have achieved level 3 or above, and the body of knowledge about the CMM is readily available, you might have some explaining to do if you claim ignorance. This book will go a long way towards preventing that by at least arming you with the basics - and doing so in a clear manner.

12 of 12 people found the following review helpful:

3.0 out of 5 stars Helpful information on Activities., July 14, 1999

By A Customer

This review is from: A Guide to the Cmm: Understanding the Capability Maturity Model for Software (Spiral-bound)

My focus on this book was Level 2 with a focus on Software Subcontractor Management. It clarified some of the Activities, and tied them into their related goals, but there was no information on Measurement and Analysis, or Verification. The book is liberally sprinkled with graphics which are poorly drawn and, at least to me, not at all helpful. I finally just ignored them, and used only the written part. Overall, it was helpful, but I hope to find something with more specific information on how to actually implement the steps needed for CMM Level 2.