Problem with Cmm
Problem with Capability Maturity Model (CMM)
Anbesa Jima Department of Computing Science, Adama Science and Technology University, Ethiopia
Abstract The Capability Maturity Model is an organizational model that describes 5 evolutionary stages (levels) in which an organization manages its processes. The Capability Maturity Model does come with some drawbacks. It is a goal, not a method, being used just as stamp of approval, doesn’t say anything about software, and doesn’t help in a crisis, only for repetitive tasks. In any context in which the CMM is applied, a reasonable interpretation of the practices should be used. The CMM must be appropriately interpreted, using informed professional judgment, when the business environment of the organization differs significantly from that of a large contracting organization. The CMM is not prescriptive; it does not tell an organization how to improve. The CMM describes an organization at each maturity level without prescribing the specific means for getting there.
1. Introduction
One of the most comprehensive software process improvement and assessment framework is the Capability Maturity Model (CMM) developed by the Software Engineering Institute (SEI) at Carnegie Mellon University. Describes an evolutionary improvement path for software organizations from an ad hoc, immature process to a mature, disciplined one. Provides guidance on how to gain control of processes for developing and maintaining software and how to evolve toward a culture of software engineering and management excellence. The Capability Maturity Model categories software process maturity into five levels, starting from an initial level to an optimized level. The Model specifies key process areas (KPAs) for each level, which determine the process maturity in the organization in respect of software development .Building quality software is a process supported by methodology and tools and involves people working over a fairly long period of time.
Anbesa Jima Department of Computing Science, Adama Science and Technology University, Ethiopia
Abstract The Capability Maturity Model is an organizational model that describes 5 evolutionary stages (levels) in which an organization manages its processes. The Capability Maturity Model does come with some drawbacks. It is a goal, not a method, being used just as stamp of approval, doesn’t say anything about software, and doesn’t help in a crisis, only for repetitive tasks. In any context in which the CMM is applied, a reasonable interpretation of the practices should be used. The CMM must be appropriately interpreted, using informed professional judgment, when the business environment of the organization differs significantly from that of a large contracting organization. The CMM is not prescriptive; it does not tell an organization how to improve. The CMM describes an organization at each maturity level without prescribing the specific means for getting there.
1. Introduction
One of the most comprehensive software process improvement and assessment framework is the Capability Maturity Model (CMM) developed by the Software Engineering Institute (SEI) at Carnegie Mellon University. Describes an evolutionary improvement path for software organizations from an ad hoc, immature process to a mature, disciplined one. Provides guidance on how to gain control of processes for developing and maintaining software and how to evolve toward a culture of software engineering and management excellence. The Capability Maturity Model categories software process maturity into five levels, starting from an initial level to an optimized level. The Model specifies key process areas (KPAs) for each level, which determine the process maturity in the organization in respect of software development .Building quality software is a process supported by methodology and tools and involves people working over a fairly long period of time.