The document discusses using the Capability Maturity Model Integration (CMMI) as a framework for organizing software development processes. It describes CMMI's five levels of maturity from initial to optimized. It provides an overview of the key process areas covered at Levels II and III, including requirements management, project planning, project monitoring and control, supplier management, measurement and analysis, process and product quality assurance, configuration management, technical solution, and risk management. The document states that while CMMI assessment is not needed, it can serve as a guide for improving processes and the organization.

1. Using CMMI as a
Framework for
Organizing Software
Development Processes

2. CMMI’s 5 Levels of Maturity
1. Initial
• Starting point for
any new process
• Processes are ad
hoc
• Few procedures
• Success depends
on individuals
Basic Control
2. Repeatable
• Processes
defined and
documented
• Basic project
management
techniques track
cost, schedule,
and functionality
• Success can be
repeated
• Specific
implementation
differ between
projects
Definition
3. Defined
• Processes meet
organizations
specific needs
• Attention paid to
documentation,
standardization
and integration
• Projects follow
defined
processes
• Management
recognizes these
processes are
the quickest
route to
completion
Measurement
4. Managed
• Processes are
predictable
• Detailed,
quantitative
measurements of
process and
product quality
are collected.
• Management can
adjust and adapt
the process to
specific projects
without losing
quality or
deviating from
specifications
Control
5. Optimized
• Process are
continually
improving
• Processes are
improved through
quantitative
feedback and
shared ideas.
• Managers
introduce
innovative
processes to
better serve the
organizations
particular needs
• Pilot projects are
common
Optimization

3. CMMI Relationships

4. CMMI Guidance
While the previous figure is complex, it is
the full coverage diagram for a software
development process that provides high
performance, high quality, agile delivery in
a rapidly changing business and technical
environment
This does not mean that CMMI
assessment or compliance is needed at
this point
But CMMI can be our guide in improving
the organization and processes

5. CMMI Level II Process Areas (PA)
The Level II process areas provide
guidance for asking questions about:
Governance
Development and support project
management
Core roles and responsibilities
Areas of improvement
The Level II PA’s are not enough to
operate GWHIS, but they are a starting
point

6. Level II Process Areas
Requirements Management (REQM)
Manage the requirements of the project's
products and product components and to
identify inconsistencies between those
requirements and the project's plans and work
products
Project Planning (PP)
Establish and maintain plans that define
project activities

7. Level II Process Areas
Project Monitoring and Control (PMC)
Provide an understanding of the project’s
progress so that appropriate corrective actions
can be taken when the project’s performance
deviates significantly from the plan
Supplier Management Agreement (SMA)
Manage the acquisition of products from
suppliers for which there exists a formal
agreement.
This can include subcontract labor

8. Level II Process Areas
Measurement and Analysis (MA)
Develop and sustain a measurement
capability that is used to support management
information needs
Process and Product Quality Assurance
(PPQA)
Provide staff and management with objective
insight into processes and associated work
products

9. Level II Process Areas
Configuration Management (CM)
Establish and maintain the integrity of work
products using configuration identification,
configuration control, configuration status
accounting, and configuration audits

10. Level III Process Areas
There are several Level III process areas
that must be included in the initial
Organizational Change Management
initiative
Technical Solution – the development of
software
Risk Management – the management of risks
associated with developing software

11. Level III Process Areas
Technical Solution (TS)
Design, develop, and implement solutions to
requirements. Solutions, designs, and
implementations encompass products,
product components, and product–related life–
cycle processes either singly or in
combinations as appropriate
Risk Management (RM)
Identify potential problems before they occur,
so that risk–handling activities may be
planned and invoked as needed across the life
of the product or project to mitigate adverse
impacts on achieving objectives

12. What CMMI Provides
Coverage of processes for software
development
Base line roles and responsibilities
Goal based descriptions
Relationships between process areas
Dependencies
Supportive synergies
A conversation based process
“What would CMMI have to say about this
idea?”