Software Development Capability Maturity Model
(Redirected from Software Development Maturity Model)
Jump to navigation
Jump to search
A Software Development Capability Maturity Model is a capability maturity model for an organization's software development process to predictably produce software applications.
- Context:
- It can (typically) involve Software Development Maturity Levels, such as:
- Initial (chaotic, ad hoc, individual heroics) - the starting point for use of a new or undocumented repeat process.
- Repeatable - the process is at least documented sufficiently such that repeating the same steps may be attempted.
- Defined - the process is defined/confirmed as a standard business process
- Capable - the process is quantitatively managed in accordance with agreed-upon metrics.
- Efficient - process management includes deliberate process optimization/improvement.
- …
- It can (typically) involve Software Development Maturity Levels, such as:
- Example(s):
- Counter-Example(s):
- See: Software Development Career Ladder, Continuous Deployment.
References
1997
- (Herbsleb et al., 1997) ⇒ James Herbsleb, David Zubrow, Dennis Goldenson, Will Hayes, and Mark Paulk. (1997). “Software Quality and the Capability Maturity Model.” In: Communications of the ACM Journal, 40(6). doi:10.1145/255656.255692
1993
- (Paulk et al., 2003) ⇒ Mark C. Paulk, Charles V Weber, Bill Curtis, and Mary Beth Chrissis. (1993). “Capability Maturity Model for Software (Version 1.1).” Technical Report. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University. CMU/SEI-93-TR-024 ESC-TR-93-177..
- QUOTE: ... The Capability Maturity Model for Software provides software organizations with guidance on how to gain control of their processes for developing and maintaining software and how to evolve toward a culture of software engineering and management excellence. The CMM was designed to guide software organizations in selecting process improvement strategies by determining current process maturity and identifying the few issues most critical to software quality and process improvement. By focusing on a limited set of activities and working aggressively to achieve them, an organization can steadily improve its organization-wide software process to enable continuous and lasting gains in software process capability. ...