Presentation Script: Evolution of the Capability Maturity
Model (CMM)
Slide 1: Title Slide
"Good morning, everyone. This presentation covers the 'Evolution of the
Capability Maturity Model,' or CMM, a core topic in our VTU Software Quality
Assurance syllabus."
Slide 2: Introduction to Software Quality Assurance (SQA)
"SQA is a planned set of actions to confirm that software processes meet
requirements. For SQA to succeed, process maturity is key. This aligns directly
with the 'Quality Models' module in our BIS714B syllabus, focusing on preventing
defects through strong processes."
Slide 3: Why Process Maturity is Needed
"The challenge in software development is the inherent variability and lack of
standardization. Without maturity models, projects are chaotic, leading to
unpredictable quality and high defects. Models like CMM provide the discipline
needed to control and standardize workflows."
Slide 4: Origin of CMM
"The CMM was developed by the SEI, or Software Engineering Institute, primarily
to assess and improve the processes of US defense contractors. The model
originated in the late 1980s, with the definitive CMM version 1.1 released in 1993."
Slide 5: The Need for CMM Evolution
"The original CMM had two major limitations: it only covered software, and the
creation of multiple CMMs—like SE-CMM and P-CMM—caused industry
confusion. There was a clear demand for a single, integrated model covering the
entire system lifecycle, which paved the way for CMMI."
Slide 6: CMM Five Maturity Levels (Core Model)
"The CMM defines five levels:
1. Initial: Chaotic and success depends on individuals.
2. Repeatable: Basic project management established; cost and schedule
tracked.
3. Defined: Processes are standardized and documented organization-wide.
4. Managed: Quantitative measurement and statistical process control are
used.
5. Optimizing: Focus shifts to continuous process improvement using
quantitative feedback."
Slide 7: Key Concepts in CMM
"CMM provides a process improvement framework defined by Key Process
Areas, or KPAs. KPAs are the specific activities required for each level. The
underlying goal is standardization and control, with SQA ensuring that the
processes defined by the model are actually followed."
Slide 8: Evolution from CMM → CMMI
"CMMI, or Capability Maturity Model Integration, was created to integrate the
separate CMM models into one comprehensive framework. CMMI is an
improvement because it applies to software, systems, and services, offering
flexibility with both Staged and Continuous representations, and aligning with
modern global standards."
Slide 9: CMMI Maturity Levels
"While the levels are similar to the original CMM, CMMI offers updated definitions
focused on measurable goals, not just activities. CMMI is the current industry
benchmark, replacing the original CMM, and is widely applicable across diverse
software and engineering environments."
Slide 10: Benefits of CMM/CMMI in Software Quality Assurance
"Adopting these maturity models is a direct SQA benefit: it ensures predictable
project outcomes, drastically reduces defects through process control,
institutionalizes risk management, and leads to measurably improved customer
satisfaction. This compliance with maturity standards is a core BIS714B
outcome."
Slide 11: CMM/CMMI in Today’s Industry
"Many major global IT companies operate at CMMI Level 5, using certification as
a competitive edge. It is frequently mandated for defense and government
contracts. Critically, the latest CMMI versions integrate well with modern
approaches like Agile and DevOps, confirming its continued relevance."
Slide 12: Conclusion
"In summary, the evolution from CMM to CMMI provided a unified, robust, and
integrated framework for process improvement. Understanding these models is
not just academic; it is essential for anyone practicing Software Quality
Assurance in the professional world."