Capability Maturity Model Integrated Cmmi Lecture - 8: Quality Frameworks

Capability Maturity Model Integrated
CMMI
Lecture - 8
Quality
Frameworks
Outline
• Introduction
• High level overview of CMMI
• Questions and comments
What is CMMI?
• CMMI (Capability Maturity Model Integration) is a proven
industry framework to improve product quality and
development efficiency for both hardware and software.
– CMMI has been established as a model to

improve business results
– Emphasis on business needs, integration

and institutionalization
• CMMI (Capability Maturity Model Integration) not asks What

to do? It asks, How to do?
https://www.sei.cmu.edu/
How can CMMI help?
• CMMI provides a way to focus and manage hardware and
software development from product inception through
deployment and maintenance.
• CMMI is a process improvement model
• Behavioral changes are needed at both management and staff

levels. Examples:
– Increased personal accountability
– Tighter links between Product Management, Development,
Deployment etc.
• Initially a lot of investment required – but, if properly managed,

we will be more efficient and productive while turning out
products with consistently higher quality.
Audience
• The audience for CMMI-DEV includes anyone interested
in process improvement in a development environment.
• Whether you are familiar with the concept of

Capability Maturity Models or are seeking information
to begin improving your development
processes, CMMI-DEV will be useful to you.
• This model is also intended for organizations that want

to use a reference model for an appraisal of their
development related processes
When will you need to implement CMMI?
• Missed Commitments
– Late delivery
– Last minute crunches
– Spiraling costs
• No/Inadequate management visibility

– Too many surprises
• Quality problems
– Too much rework
– Functions not working correctly
– Customer complaints
• Poor morale
– People frustrated
CMMI Projects
CMMI Models within the Framework
• Models:
– Systems Engineering + Software Engineering (SE/SW)
– Systems Engineering + Software Engineering + Integrated Product
and Process Development (IPPD)
– Systems Engineering + Software Engineering + Integrated Product
and Process Development + Supplier Sourcing (SS)
– Software Engineering only

• Representation options:
– Staged
– Continuous
.
Comparing Model Representations
.
CMMI Staged Representation - 5 Maturity Levels
Level 5 Process performance

continually improved through
incremental and innovative
Optimizing
technological improvements.
Level 4
ity
ur Processes are controlled using
Quantitatively
at
statistical and other quantitative
M
Managed
techniques.
e ss
Level 3
oc
Processes are well characterized and

Pr
understood. Processes, standards,

Defined
procedures, tools, etc. are defined at the
Level 2 organizational (Organization X ) level.
Proactive.
Managed Processes are planned, documented, performed,
monitored, and controlled at the project level. Often
Level 1 reactive.
Processes are unpredictable, poorly controlled, reactive.

Initial
Behaviors at the Five Levels
Maturity Level Process Characteristics Reactive processes are

fundamentally about fixing
Focus is on continuous
incidents or analyzing data about
Optimizing quantitative improvement incidents after the event. They
are often described as 'fix after
failure' processes.
Quantitativel Process is measured
y Managed and controlled
Process is characterized
Defined for the organization and Proactive: Creating or controlling
is proactive
a process by causing something
Process is characterized to happen rather than responding
Managed for projects and is often to it after it has happened.
reactive
“Planning to prevent failure”
Process is unpredictable,
Initial poorly controlled, and
reactive
CMMI Levels
CMMI Processes within Each Level
• Causal Analysis and Resolution (CAR)

• Configuration Management (CM)
• Decision Analysis and Resolution (DAR)
• Integrated Project Management (IPM)
• Measurement and Analysis (MA)
• Organizational Process Definition (OPD)
• Organizational Process Focus (OPF)
• Organizational Performance Management (OPM)
• Organizational Process Performance (OPP)
• Organizational Training (OT)
• Product Integration (PI)
• Project Monitoring and Control (PMC)
• Project Planning (PP)
• Process and Product Quality Assurance (PPQA)

• Quantitative Project Management (QPM)

• Requirements Development (RD)
• Requirements Management (REQM)
• Risk Management (RSKM)
• Supplier Agreement Management (SAM)
• Technical Solution (TS)
• Validation (VAL)
• Verification (VER)
Level Wise Process Areas
.
.
CMMI Process Area Categories (Continuous)
CMMI Process Areas (Continuous)
Maturity Level Project Managment Engineering Process Management Support

5 Organizational Innovation & Causal Analysis & Resolution
Optimizing Deployment
4 Quantitative Project Mngt Organizational Process Performance
Quantitativ
ely
Managed
3 Integrated Project Mngt Requirements Development Organizational Process Focus Decision Analysis & Resolution
Defined Risk Management Technical Solution Organizational Process Definition
Product Organizational Training
Integration
Verificati
on
Validation
2 Project Planning Requirements Mngt Measurement & Analysis
Managed Project Monitoring & Process & Product Quality Assurance
Control Configuration Mngt
Supplier Agreement
Mngt
1
Initial
Pitfalls of CMMI implementation
How Long Does it Take?
• Implementing CMMI does not occur overnight.

• Implementing CMMI is not merely a “paper
drill”.
• Typical times for implementation:
– 3-6 months of preparation
– 6-12 months of implementation
– 3 months of assessment preparation
– 12 months for each new level
Pitfalls of CMMI implementation
Is It Perfect?
• No! Some implementations do more harm than

good.
– Complete re-vamp of processes to “get certified”
instead of smartly adapting processes.
– Focusing on specific tasks instead of
improvement suggestions.
Advantage of CMMI implementation
• Defect rates have dropped

• Defect detection occurs earlier
• User requirements are documented, controlled, and managed
with monitoring
• Especially important when users change their minds!
• Estimating improves and becomes more precise
• Risk management is a possible
• Development processes remain agile!

Capability Maturity Model Integrated Cmmi Lecture - 8: Quality Frameworks

Uploaded by

Copyright:

Available Formats

Capability Maturity Model Integrated Cmmi Lecture - 8: Quality Frameworks

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Capability Maturity Model Integrated Cmmi Lecture - 8: Quality Frameworks

Uploaded by

Copyright:

Available Formats

Capability Maturity Model Integrated

– CMMI has been established as a model to

– Emphasis on business needs, integration

• CMMI (Capability Maturity Model Integration) not asks What

• Behavioral changes are needed at both management and staff

• Initially a lot of investment required – but, if properly managed,

• Whether you are familiar with the concept of

• This model is also intended for organizations that want

• No/Inadequate management visibility

– Software Engineering only

Level 5 Process performance

Processes are well characterized and

understood. Processes, standards,

Processes are unpredictable, poorly controlled, reactive.

Maturity Level Process Characteristics Reactive processes are

• Causal Analysis and Resolution (CAR)

• Organizational Performance Management (OPM)

• Organizational Process Performance (OPP)

• Organizational Training (OT)

• Product Integration (PI)

• Project Monitoring and Control (PMC)

• Project Planning (PP)

• Process and Product Quality Assurance (PPQA)

• Quantitative Project Management (QPM)

Maturity Level Project Managment Engineering Process Management Support

How Long Does it Take?

• Implementing CMMI does not occur overnight.

• No! Some implementations do more harm than

• Defect rates have dropped

• User requirements are documented, controlled, and managed

• Especially important when users change their minds!

• Estimating improves and becomes more precise

• Risk management is a possible

• Development processes remain agile!

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.