Essence of the capability maturity model
The CMM (Capability Maturity Model) wasn't intended to be all things to all people or cover all possible aspects of software and systems development. CMM was intended to provide one set of guidelines for managing software development projects and making improvements over time. This set of guide...
Saved in:
Published in | Computer (Long Beach, Calif.) Vol. 30; no. 6; pp. 112 - 114 |
---|---|
Main Author | |
Format | Journal Article |
Language | English |
Published |
New York
IEEE
01.06.1997
The Institute of Electrical and Electronics Engineers, Inc. (IEEE) |
Subjects | |
Online Access | Get full text |
Cover
Loading…
Summary: | The CMM (Capability Maturity Model) wasn't intended to be all things to all people or cover all possible aspects of software and systems development. CMM was intended to provide one set of guidelines for managing software development projects and making improvements over time. This set of guidelines was based on best practices, software engineering discipline, real world experience and extrapolation from other industries. These guidelines were only meant to be tailored and applied within the culture and context of each unique organization. |
---|---|
Bibliography: | ObjectType-Article-2 SourceType-Scholarly Journals-1 ObjectType-Feature-1 content type line 23 |
ISSN: | 0018-9162 1558-0814 |
DOI: | 10.1109/2.587560 |