|
|
|
|
|
|
|
|
Proudly, an:

Licensed to deliver CMMI SCAMPI and Introduction to CMMI Services.
We abide by the SEI's Ethics and Compliance Standards of Excellence
|
|
©2003, by Hillel Glazer, Entinex, Inc.
Seeking the stability -- and, thanks to the increased spending on Defense and Homeland Security, the opportunity -- of government work, many software companies are facing a rude surprise called the "CMMI."
What is CMMI?
CMMI stands for "Capability Maturity Model - Integration." It’s used to help make business management decisions about how software is developed. The CMMI focuses on the managerial aspects of software development. Whereas a software development model is a way for programmers to code, test, deploy and build on their software, a software management model is a way for software projects to plan, organize and identify what needs to get done to run the project. It’s a business management model used to gain insight into and control over the development, so you can predict and adjust project activities towards success.
Why did it come about?
In the 1980s a Standish Group study found that over 30% of all large software projects failed to be delivered, and, of the remaining, nearly 80% failed to come in on time and budget. These figures, in fact, account for the evidence that smaller companies' success rates were nearly twice as high as the success rates of larger companies. The research also indicated that most of the money in software development was spent on fixing buggy software, rather than on the initial development. In effect, only about 16% of all software projects surveyed were delivered on time, on budget and with the expected functionality, with most of it being developed by smaller companies.
To beat these odds, and to lower the overall cost of buying software, the Department of Defense (who arguably spent the most money on custom-developed software) funded the Software Engineering Institute (SEI) at Carnegie Mellon University to find ways to help defense contractors build software more economically.
The SEI defined a "successful project" in terms of a project's ability to meet cost, schedule and quality objectives. "Quality" was defined as how many post-delivery corrections, fixes and upgrades were required before the product finally did what the customers expected. "Failed projects" were those that were cancelled or significantly overran cost, schedule or quality expectations. Instead of focusing on the mistakes, overruns and what not to do, the SEI focused on what the successful projects had in common. The result became the Capability Maturity Model for software, or CMM.
Subsequent to the original release of the CMM, maturity models for other aspects of managing technical projects were created. In late 2001, the CMMI was released which integrated all the models. The CMMI also included changes to the basic structure of the CMM which made the model more effective and more broadly applicable to companies that might have found the original models too rigid.
Today, the CMM/CMMI are the de facto standard for software management throughout the Federal government and is internationally recognized as a very powerful business tool and competitive differentiator.
Keep reading >>>
Copyright Notice and Reproduction Permission
All Contents © Copyright Entinex, Inc. All rights reserved. These works may be freely reproduced, distributed, or transmitted solely for non-commercial, personal, or educational purposes, provided that they are not modified and any reproduction or transmission contains this copyright notice and the author’s complete bio and company information as provided. Nothing else may otherwise be used, reproduced, published, or disseminated without prior written permission.
|
|