INTLAND

SOFTWARE

Achieving Capability Maturity

Model Integration (CMMI)

maturity
level 2
Achieving Capability
Maturity Model Integration
(CMMI) maturity level 2

CMMI for Development at Level 2 - also called Managed Processes Level - can
be easily achieved by smaller enterprises. Capability Maturity Model Integration
According
(CMMI) is a process improvement and appraisal program implemented by to industry
Carnegie Mellon University. An approved level of Capability Maturity is required
by many US and European customers especially in government or larger
statistics,
software development projects, where small companies may be involved as CMMI Level 2
suppliers. Of CMMI’s 5 maturity levels, Level 5 is especially dedicated for
large organizations. A common misunderstanding among small companies
via Managed
is that it’s only for large organizations with hundreds of developers. That is Processes
not true! CMMI Level 2 and 3 can be easily achieved by smaller organizations
as well. For them, CMMI provides new business potential by enabling them
can be easily
to participate in large tenders or projects where CMMI compliance is a achieved by
requirement. Besides, CMMI can be used to guide process improvement
across projects, divisions, or an entire organization specialized on software
development, to deliver cost savings and eventually, higher quality software.
70%
Capability maturity is a measure for a company’s ability to deliver as
promised, on time, to cost. Increased maturity means significantly
of smaller
reduced risks, time and cost of software development. The formal organizations by
method used to evaluate an organization’s performance is the Standard
CMMI Appraisal Method for Process Improvement (SCAMPI).
implementing
As CMMI is especially focused on the software development
the defined
industry, ALM tools have to be ready to support the management of processes and
processes along CMMI for Development Reference Guide.
managing them
At CMMI Level 2, the following areas need to be defined and accurately
managed along specific goals and practices defined in the CMMI Guide.
accordingly.

Configuration Measurement Project Monitoring Project

Management and Analysis and Control Planning

Process and Product Requirements Supplier Agreement

Quality Assurance Management Management
Intland prepared a compliance matrix to support
companies using the codeBeamer ALM to understand
CMMI Level 2 requirements, and use the corresponding
codeBeamer features to achieve CMMI Level 2
compliance. This guide can be used for SCAMPI
audits or just for preparation of self-assessment.

Map of features of
codeBeamer to CMMI:
Maturity Level 2 - Managed

The following tables show the

references to CMMI Level 2 main
categories, SGs and SPs defined
in the CMMI Guide, and collects
recommendations and feature sets
of codeBeamer on how to fulfill
requirements defined in the
CMMI Guide to achieve
Level 2 Maturity.
CMMI Level 2 Categories
Estimates of project planning
PROJECT PLANNING
The purpose of Project Planning
(PP) is to establish and maintain
plans that define project activities.
Commitments to the project plan
are established and maintained.
Specific Goals Specific Practices codeBeamer features
SP 1.1
Establish a top-level work
breakdown structure (WBS) to
estimate the scope of the project.
SP 1.2
Establish and maintain estimates of
SG 1 work product and task attributes.
parameters are established
and maintained. SP 1.3
Define project lifecycle phases on
which to scope the planning effort.
Under the project definition
description/scope can be edited and
SP 1.4 shared. Built-in wiki page supports
Estimate the project’s effort and WBS definition and sharing.
cost for work products and tasks
based on estimation rationale.
Requirements
Management – Task definition.
SP 2.1
Establish and maintain the
project’s budget and schedule. Workflow definition
Resource planning under
SP 2.2 task definition.
Identify and analyze project risks.
Project Planner – Release
and Sprint planning.
SP 2.3
Plan for the management
of project data. Built-in wiki page dedicated to
project risk definition and analysis.
SG 2
A project plan is established SP 2.4 Define and share under built-
and maintained as the basis Plan for resources to in wiki page of the project.
for managing the project. perform the project.
Resource planning.
SP 2.5
Plan for knowledge and skills
needed to perform the project. Define and share under built-
in wiki page of the project.
SP 2.6 Wiki and trackers’ change
Plan the involvement of management. Collaborative
identified stakeholders. editing ensured.
SP 3.1-3.3 practices can be realized
via approval workflow and project wiki
SP 2.7 pages to define and share relevant
Establish and maintain the data. The document management
overall project plan. feature can also be used for sharing
information in all document formats.
SP 3.1
Review all plans that affect the project
to understand project commitments.
SG 3 SP 3.2
Adjust the project plan to reconcile
available and estimated resources.
SP 3.3
Obtain commitment from relevant
stakeholders responsible for performing
and supporting plan execution.
Reference: cmmiinstitute.com/assets/CMMI-DEV_Quick_Ref.pdf
CMMI Level 2 Categories Specific Goals Specific Practices codeBeamer features

SP 1.1
Monitor actual values of
project planning parameters
against the project plan.

SP 1.2
Monitor commitments against those
identified in the project plan.

SP 1.3
Monitor risks against those
identified in the project plan.

Project monitoring needs to be

SG 1
Actual project performance
and progress are monitored
against the project plan.
defined in the project plan, and can be
shared as a document or wiki page
SP 1.4
Monitor the management of project Risk management can be tracked
data against the project plan. via specific risk trackers where only
risk items are defined and a specific
workflow is added on how to manage
risk along the project lifecycle.

SP 1.5 Project data management

Monitor stakeholder involvement and stakeholder involvement
against the project plan. – including data sharing – is a
PROJECT MONITORING basic feature of the codeBeamer
AND CONTROL collaborative environment.
The purpose of Project Monitoring
and Control (PMC) is to provide
Project progress can be
an understanding of the project’s SP 1.6 traced on different levels:
progress so that appropriate Periodically review the project’s
corrective actions can be taken progress, performance, and issues.
in case the project’s performance
• Project Browser
deviates significantly from the plan.
(main dashboard)
• Release and sprint dashboard
SP 1.7 – Team task board
Review the project’s • Kanban board- tasks
accomplishments and results at status monitoring
selected project milestones.
• And via other customizable
reports for the specific project.

SP 2.1
Collect and analyze issues
and determine corrective
actions to address them.

SG 2
Corrective actions are managed SP 2.2
to closure when the project’s Take corrective action on
performance or results deviate identified issues.
significantly from the plan.

SP 2.3
Manage corrective actions to
closure.

Reference: cmmiinstitute.com/assets/CMMI-DEV_Quick_Ref.pdf
CMMI Level 2 Categories
REQUIREMENTS
MANAGEMENT
The purpose of Requirements
Management (REQM) is to manage
requirements of the project’s products
and product components and to
ensure alignment between those
requirements and the project’s
plans and work products.
CMMI Level 2 Categories
CONFIGURATION
MANAGEMENT
The purpose of Configuration
Management (CM) is to establish
and maintain the integrity of work
products using configuration
identification, configuration control,
configuration status accounting,
and configuration audits.
Specific Goals
SG 1
Requirements are managed and
inconsistencies with plans and
work products are identified.
Specific Goals
SG 1
Baselines of identified work
products are established.
SG 2
Changes to the work products
under configuration management
are tracked and controlled.
SG 3
Integrity of baselines is
established and maintained.
Reference: cmmiinstitute.com/assets/CMMI-DEV_Quick_Ref.pdf
Specific Practices codeBeamer features
SP 1.1
Develop an understanding with the Requirements definition, requirements
requirements providers on the meaning trackers, round trip engineering
and aim of the requirements. features to exchange requirements list
with customers and other stakeholders.
SP 1.2 Requirements verification and
Obtain commitment to requirements approval process can be defined
from project participants. via the workflow engine.
All changes to requirements can be
SP 1.3 tracked in the trackers’ item history.
Manage changes to requirements
as they evolve during the project.
All requirements dependences
and requirements attached to
the product or its release can be
SP 1.4 tracked in the traceability browser.
Maintain bidirectional
traceability among requirements
and work products.
Requirements verification and approval
during definition and in case of
changes can go through an approval
SP 1.5 process to ensure this alignment. This
Ensure that project plans and is supported by the workflow engine.
work products remain aligned
with the requirements.
Specific Practices codeBeamer features
SP 1.1
Identify configuration items,
components, and related work
products to be placed under
configuration management.
In codeBeamer each work item and
SP 1.2 configuration item can be base lined.
Establish and maintain a configuration All of them have unique ID numbers.
management and change management
system for controlling work products.
Change and configuration
management has to be executed
SP 1.3 through defined workflows.
Create or release baselines for internal
use and for delivery to the customer.
Baselines with the appropriate
permission can be done any time
and for all artifacts in codeBeamer.
SP 2.1
Track change requests for
All changes are also tracked in the
configuration items.
trackers history of configuration items.
SP 2.2 Controlling can be done via
Control changes to pre-defined workflows.
configuration items.
All items defined and changed under
configuration items can be tracked.
SP 3.1
Establish and maintain records
describing configuration items.
SP 3.2
Perform configuration audits
to maintain the integrity of
configuration baselines.
CMMI Level 2 Categories Specific Goals Specific Practices codeBeamer features

SP 1.1
Establish and maintain measurement
objectives derived from identified
information needs and objectives.

SP 1.2
Specify measures to address
measurement objectives.

SG 1
Measurement objectives and
activities are aligned with identified
information needs and objectives.

SP 1.3
Specify how measurement data
are obtained and stored.

Process and product quality

measurement and other project
specific measurement rules
SP 1.4 can be defined and shared
Specify how measurement data are via the project wiki.
analyzed and communicated.

Measurement-related activities
can be managed as tasks with
pre-defined workflows.
MEASUREMENT
AND ANALYSIS
Plug-ins and customizable
The purpose of Measurement
and Analysis (MA) is to develop SP 2.1 reports support the continuous
Obtain specified measurement data. collection of data to be analyzed.
and sustain a measurement
capability used to support
management information needs.
Result of the analysis can be
shared via wiki. Comments and
collaborative editing is also
ensured via built-in wiki.

SP 2.2
Analyze and interpret
measurement data.

SG 2
Measurement results addressing
identified information needs
and objectives are provided.
SP 2.3
Manage and store measurement
data, measurement specifications,
and analysis results.

SP 2.4
Communicate results of
measurement and analysis activities
to all relevant stakeholders.

Reference: cmmiinstitute.com/assets/CMMI-DEV_Quick_Ref.pdf
CMMI Level 2 Categories Specific Goals
SG 1
Select suppliers based on an evaluation
Agreements with suppliers are
established and maintained.
requirements and established criteria.
SUPPLIER AGREEMENT
MANAGEMENT
Perform activities with the supplier as
The purpose of Supplier Agreement
Management (SAM) is to manage
the acquisition of products and
services from suppliers. SG 2
Agreements with suppliers are
satisfied by both the project
and the supplier.
CMMI Level 2 Categories Specific Goals
SG 1
Adherence of the performed
processes and associated work
products to applicable process
descriptions, standards, and
procedures is objectively evaluated.
PROCESS AND
PRODUCT QUALITY
The purpose of Process and Product
Quality Assurance (PPQA) is to
provide staff and management with
objective insight into processes
and associated work products.
SG 2
Noncompliance issues
are objectively tracked
and communicated, and
resolution is ensured.
Reference: cmmiinstitute.com/assets/CMMI-DEV_Quick_Ref.pdf
Specific Practices
SP 1.1
Determine the type of acquisition
for each product or product
component to be acquired.
SP 1.2
of their ability to meet the specified
SP 1.3
Establish and maintain
supplier agreements.
SP 2.1
specified in the supplier agreement.
SP 2.2
Ensure that the supplier agreement
is satisfied before accepting
the acquired product.
SP 2.3
Ensure the transition of products
acquired from the supplier.
Specific Practices
SP 1.1
Objectively evaluate selected
performed processes against
applicable process descriptions,
standards, and procedures.
SP 1.2
Objectively evaluate selected
work products against
applicable process descriptions,
standards, and procedures.
SP 2.1
Communicate quality issues and
ensure the resolution of
noncompliance issues with
the staff and managers.
SP 2.2
Establish and maintain records
of quality assurance activities.
codeBeamer features
Acquisition rules need to be defined
in Special Procedures descriptions
shared via the document management
system or built-in wiki. Supplier
agreements can be saved and shared
via the document management
system ensuring access to the latest
versions and monitoring all changes.
Testing and QA processes regarding
delivered software parts or
components by the suppliers can be
defined and tests can be planned, run
and documented in codeBeamer.
Quality criteria of each product
or component delivered by
suppliers need to be defined under
requirements’ items as acceptance
criteria. Test cases can be defined
based on those requirements.
codeBeamer features
Quality Assurance measurements can
be shared via codeBeamer document
management or built-in wiki. All reports,
protocols, non-conformity checks
can be documented in codeBeamer.
Product quality criteria can be
described in test cases attached to
requirements. Requirements-based
testing ensures that the product
fully complies with expectations.
Test and QA results can be
reported from codeBeamer wiki
plug-ins that work like dashboards
for performed activities.
 www.intland.com
sales@intland.com
© 2014 Intland Software

Sales: (EU) +49-711-2195420, (US) 1-866-468-5210