Introduction to CMMI - Dev L3

Introduction to
CMMI for Development V1.3
Maturity Level 3
Adaptive Processes Consulting (P) Ltd.
Experience World Class Processes!
An ISO 9001:2008 Certified Company

© Adaptive Processes Simpler, Faster, Better 4
Course Objective
• To provide an overview of CMMI
• Understand maturity levels of CMMI
• Understand various process areas
including goals and practices
• Discuss practical implementation
aspects
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/introduction-to-cmmi-dev-l3-1551

CMMI Model Components
Commitment to Perform: creates policies and secures sponsorship for process improvement efforts
Ability to Perform: ensures that the project and/or organization has the resources it needs to pursue process improvement
Directing Implementation: collects, measures, and analyzes data related to processes
Verification: verifies that the projects and/or organization’s activities conform to requirements, processes, and procedures
Maturity Level
Process Area Process Area Process Area
Generic Goals Specific Goals
Commitment
to Perform
Ability to
Perform
Directing
Implementation
Verification
Common
Features
Generic
Practices
Specific
Practices

Maturity Levels

Level 1 Initial Contd…
In spite of this ad hoc, chaotic
environment, maturity level 1
organizations often produce
products and services that work;
however, they frequently exceed the
budget and schedule of their
projects
Maturity level 1 organizations are
characterized by a tendency to over
commit, abandon processes in the
time of crisis, and not be able to
repeat their past successes

Level 3: Defined
Initial
• Processes are well characterized and
understood, and are described in
standards, procedures, tools, and methods
• Organization’s set of standard processes,
which is the basis for ML 3, is established
and improved over time
• These standard processes are used to
establish consistency across the
organization
• Projects establish their defined processes
by tailoring the organization’s set of
standard processes according to tailoring
guidelines

Level 4 Quantitatively
Managed…Contd.
Initial
Detailed measures of process
performance are collected and
statistically analyzed
Special causes of process variation are
identified and, where appropriate, the
sources of special causes are corrected to
prevent future occurrences
Quality and process performance
measures are incorporated into the
organization’s measurement repository to
support fact-based decision making in
the future

Project Management Process Areas
Project Planning
Project Monitoring and Control
Requirements Management
Supplier Agreement Management
Integrated Project Management
Risk Management

Process Management Process Areas
Organizational Process Focus
Organizational Process Definition
Organizational Training
Organizational Process Performance
Organizational Innovation and Deployment

Project Planning – Goals and Practices
Goal 2:
A project plan is established and maintained as the
basis for managing the project.
Specific Practices
• Establish and maintain project’ s budget and
schedule
• Identify and analyze project risks
• Plan for management of project data
• Plan for necessary resources to perform project
• Plan for knowledge and skills needed to perform the
project
• Plan the involvement of identified stakeholders
• Establish and maintain the overall project plan
content

Goal 1:
Actual performance and progress of the
project are monitored against the project plan
Specific Practices
• Monitor the actual values of the project planning parameters
against the project plan
• Monitor commitments against those identified in the project plan
• Monitor risks against those identified in the project plan
• Monitor the management of project data against the project plan
• Monitor stakeholder involvement against the project plan
• Periodically review project's progress, performance, and issues
• Review the accomplishments and results of the project at
selected project milestones
Project Monitoring and Control – Goals
and Practices

Requirements Management – Goals
and Practices
Goal 1:
Requirements are managed and inconsistencies with
project plans and work products are identified.
Specific Practices
• Develop an understanding with the requirements
providers on the meaning of the requirements
• Obtain commitment to requirements from project
participants
• Manage requirements changes
• Maintain bidirectional traceability of requirements
• Ensure that project plans and work products remain
aligned with requirements

Supplier Agreement Management -
Goals and Practices
Goal 2: Agreements with the suppliers are satisfied by
both the project and the supplier
Specific Practices
• Perform activities with the supplier as specified in the
supplier agreement
• Ensure that the supplier agreement is satisfied before
accepting the acquired product.
• Ensure the transition of acquired products from the
supplier to the project as appropriate

Integrated Project Management –
Implementation
Integrate other plans that affect the project
with the project plan (Lower level plans)
Identify and analyze product and project
interface risks
Establish objective entry and exit criteria to
authorize the initiation and completion of
the tasks described in the work breakdown
structure (WBS)
Identify how conflicts will be resolved that
arise among relevant stakeholders
Propose improvements to the
organizational process assetsThis document is a partial preview. Full document download can be found on Flevy:

Goal 1:
Preparation for risk management is conducted.
Specific Practices
• Determine risk sources and categories
• Define the parameters used to analyze and
categorize risks, and to control the risk
management effort
• Establish and maintain the strategy to be used for
risk management
Risk Management – Goals and
Practices

Risk Management – Implementation
Detailed analysis on risk sources and
categories
Define bounds on the extent to which
thresholds are applied against or within a
category
Review all elements of the work
breakdown structure and project plan as
part of identifying risks to help ensure
that all aspects of the work effort have
been considered
Develop contingency plans for selected
critical risks in the event their impacts are
realized
Collect performance measures on the risk-
handling activities

Software Configuration Management –
Goals and Practices
Goal 1:
Baselines of identified work products are
established.
Specific Practices
• Identify the configuration items, components,
and related work products to be placed under
configuration management.
• Establish and maintain a configuration
management and change management system
for controlling work products.
• Create or release baselines for internal use and
for delivery to the customer.

Software Configuration Management –
Evidences
Configuration Management Plan
Establish Configuration Control Board
All CIs should be stated in the CM plan,
control to be evidenced as per the CM
system in place (manual or CM tool)
Physical presence of the CI will be
checked
CM Audit reports to be evidenced
Change requests, Status reports to be
checked in conjunction with CM registers
and baselines
Bi-directional trace ability in the project,
as applicable

Goal 1:
Adherence of the performed process and associated
work products and services to applicable process
descriptions, standards, and procedures is objectively
evaluated.
Specific Practices
• Objectively evaluate designated performed
processes against applicable process descriptions,
standards and procedures.
• Objectively evaluate designated work products and
services against applicable process descriptions,
standards, and procedures.
Process and (Associated Work) Product
Quality Assurance – Goals and Practices

Goal 1:
Decisions are based on an evaluation of alternatives using established
criteria.
Specific Practices
• Establish and maintain guidelines to determine which issues are
subject to a formal evaluation process.
• Establish and maintain the criteria for evaluating alternatives, the
relative ranking of these criteria.
• Identify alternative solutions to address issues.
• Select evaluation methods.
• Evaluate alternative solutions using the established criteria and
methods.
• Select solutions from alternatives based on the evaluation criteria.
Decision Analysis and Resolution –
Goals and Practices

Engineering Process Areas

Requirement Development - Goals and
Practices
Goal 3:
The requirements are analyzed and validated.
Specific Practices
• Establish and maintain operational concepts and associated
scenarios.
• Establish and maintain a definition of required functionality
and quality attributes.
• Analyze requirements to ensure that they are necessary and
sufficient.
• Analyze requirements to balance stakeholder needs and
constraints.
• Validate requirements to ensure the resulting product will
perform as intended in the user's environment using multiple
techniques as appropriate.

Technical Solutions - Goals and
Practices
Goal 2: Product or product component designs are
developed.
Specific Practices
• Develop a design for the product or product
component.
• Establish and maintain a technical data package.
• Design product component interfaces using
established criteria.
• Evaluate whether the product components
should be developed, purchased, or reused based
on established criteria.

Product Integration - Goals and
Practices
Goal 1:
Preparation for product integration is conducted.
Specific Practices
• Establish and maintain a product integration strategy.
• Establish and maintain the environment needed to
support the integration of the product components.
• Establish and maintain procedures and criteria for
integration of the product components.

Product Integration- Evidences
• Integration Test Plan that includes
integration sequence : In case there are
more than one integration options then the
best option is arrived at based on DAR
guidelines
• Reviewed, approved and base-lined SDD /
HDD documents
• Formal control on changes to SDD / HDD
• Verification (Reviews) & Validation
(System Test) Records
• Product certification / Release Audit as
applicable
• Release notes as applicable

Verification – Goals and Practices
Goal 3
Selected work products are verified against
their specified requirements.
Specific Requirements
• Perform verification on the selected work
products.
• Analyze results of all verification activities
and identify corrective action

Validation – Goals and Practices
Goal 2
The product or product components
are validated to ensure that they are
suitable for use in their intended
operating environment.
Specific Practices
• Perform validation on selected
products and product components.
• Analyze the results of validation
activities

Goal 1:
Strengths, weaknesses, and improvement opportunities
for the organization's processes are identified
periodically and as needed.
Specific Practices
• Establish and maintain description of the process
needs and objectives for the organization.
• Appraise the processes of the organization’s
periodically and as needed to maintain an
understanding of their strengths and weaknesses.
• Identify improvements to the organization's
processes and process assets.
Organizational Process Focus – Goals
and Practices

Organizational Process Definition –
Goals and Practices
Goal 1:
A set of organizational process assets is established and
maintained.
Specific Practices
• Establish and maintain the organization's set of standard
processes
• Establish and maintain descriptions of the lifecycle models
approved for use in the organization
• Establish and maintain the tailoring criteria and guidelines for
the organization's set of standard processes
• Establish and maintain the organization's measurement
repository
• Establish and maintain the organization's process asset library.

Goal 2:
Training necessary for individuals to perform
their roles effectively is provided.
Specific Practices
• Deliver training following the organizational
tactical training plan.
• Establish and maintain records of
organizational training.
• Assess the effectiveness of the organization’ s
training program.
Organization Training – Goals and
Practices

1
Flevy (www.flevy.com) is the marketplace
for premium documents. These
documents can range from Business
Frameworks to Financial Models to
PowerPoint Templates.
Flevy was founded under the principle that
companies waste a lot of time and money
recreating the same foundational business
documents. Our vision is for Flevy to
become a comprehensive knowledge base
of business documents. All organizations,
from startups to large enterprises, can use
Flevy— whether it's to jumpstart projects, to
find reference or comparison materials, or
just to learn.
Contact Us
Please contact us with any questions you may have
about our company.
• General Inquiries
support@flevy.com
• Media/PR
press@flevy.com
• Billing
billing@flevy.com

Introduction to CMMI - Dev L3

Recommended

Recommended

More Related Content

More from Flevy.com Best Practices

More from Flevy.com Best Practices (20)

Recently uploaded

Recently uploaded (20)

Introduction to CMMI - Dev L3