CMM (Capability Maturity Model)

Project management
Can someone please tell me briefly what CMM is? And could he/she would also lead me to a site where I can read further indepth on CMM - Thanks!

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi Kanada,
The Capability Maturity Model was first developed in the late 1980s by the Software Engineering Institute at Carnegie Mellon University. It takes the premise that software development capability is built on people, process and technology. It suggests that if you have a more mature process, you have less liklihood of a project failure. The theory follows that you can still deliver if your process is immature, but you will rely on “heroes” to get you there. The CMM defines 5 levels of maturity, and within each level, a set of key process areas. In order to progress to the next level, you must achieve a level of proficiency in all the preceding level KPAs. That is, it is pointless reading Harvard Business Review, grabbing the latest management theory, and building onto a broken foundation layer. In essence, it is a tool to help you crawl before you walk, walk before you run, and run before you fly. It is difficult to get up through the levels without serious analytical effort, and deep thought about what you and your team have to achieve. Try looking at this is home of CMM

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Liberty
    The Capability Maturity Model can be found by visiting Carnegie Mellon Institute for Software Development. It's main purpose was to help software developers, testers, and Q/A people to better understand structured design, development, test & implementation procedures for the new software design and implementation process. When a developer can master repeatedly the steps of meeting with the customer and identifying the needs of the customer, then flow through the software design, review, development, test, review, install/implement, and follow-up process repeatedly, then this will help reduce project scope changes, project install date creep, etc. It teaches developers the way to do software changes in a structured way, when followed by all involved in the life cycle of software changes/new development, it helps all in the process. Identifying meetings with the customer, when to hold them, how to handle meetings (at differents stages of the life cycle), which implements a better understanding of the required changes for all involved, (user, developer, testers, Q/A & managers). Study it, learn the process flow, implement it and reduce your project creep issues tremendously. I was involved with Tinker Air Force Base, Software Quality Assurance group, and utilized this process which allowed the base to help implement CMM standards, the base went from a grade 0 to grade level 5 in less than 4 years for Software Q/A, (improved project control and implementation) using this practice, with 5 being the highest, with Tinker being the Leader in Quality control of software changes over 5 other bases being monitored and tested. Believe in it, it works! REN
    5 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: