# ML Process Area

1 2 Requirements Management

2 2 Requirements Management

3 2 Requirements Management

3 2 Requirements Management
5 2 Project Planning

6 2 Project Planning

7 2 Project Planning

8 2 Project Planning

9 2 Configuration Management
9 2 Configuration Management

9 2 Configuration Management

9 2 Configuration Management

9 2 Configuration Management
10 2 Configuration Management
 CMMI MATURITY IN

Questions

Understand Requirments
1. Establish criteria for distinguishing appropriate requirements providers.
2. Establish objective criteria for the evaluation and acceptance of requirements.
3. Analyze requirements to ensure that established criteria are met.
4. Reach an understanding of requirements with requirements providers so that
project participants can commit to them.

Obtain Commitment to requirments

1. Assess the impact of requirements on existing commitments.
2. Negotiate and record commitments. Changes to existing commitments should
be negotiated before project participants commit to a new requirement or
requirement change.

Manage Requirements Changes

1. Document all requirements and requirements changes that are given to or
generated by the project.
2. Maintain a requirements change history, including the rationale for changes.
3. Evaluate the impact of requirement changes from the standpoint of relevant
stakeholders. Requirements changes that affect the product architecture can
affect many stakeholders.
4. Make requirements and change data available to the project.

Maintain Bidirectional Traceability of Requirements

1. Maintain requirements traceability to ensure that the source of lower level
(i.e., derived) requirements is documented.
2. Maintain requirements traceability from a requirement to its derived
requirements and allocation to work products.
Work products for which traceability may be maintained include the architecture,
product components, development iterations (or increments), functions,
interfaces, objects, people, processes, and other work products.
3. Generate a requirements traceability matrix.
Estimate the Scope of the Project
1. Develop a WBS.
2. Define the work packages in sufficient detail so that estimates of project
tasks, responsibilities, and schedule can be specified.
3. Identify products and product components to be externally acquired.
4. Identify work products to be reused.

Define Project Lifecycle Phases

Define the project lifecycle phases on which to scope the planning effort.

The project lifecycle phases need to be defined depending on the scope of

requirements, the estimates for project resources, and the nature of the project.
Larger projects can contain multiple phases, such as concept exploration,
development, production, operations, and disposal. Within these phases,
subphases may be needed. A development phase can include subphases such
as requirements analysis, design, fabrication, integration, and verification. The
determination of project phases typically includes selection and refinement of
one or more development models to address interdependencies and appropriate
sequencing of the activities in the phases.
Depending on the strategy for development, there can be intermediate phases
for the creation of prototypes, increments of capability, or spiral model cycles. In
addition, explicit phases for “project startup” and “project close-out” can be
included.

Estimates Effort and Cost

1. Collect models or historical data to be used to transform the attributes of work
products and tasks into estimates of labor hours and costs.
2. Include supporting infrastructure needs when estimating effort and cost.
3. Estimate effort and cost using models, historical data, or a combination of
both.

Develop a Project Plan

A project plan is established and maintained as the basis for managing the
project.
1. Establish the Budget and Schedule
2. Identify Project Risks
3. Plan the Project resources
4. Plan Needed Knowledge and Skills

Identify Configuration Items

Identify the configuration items, components, and related work products that will
be placed under configuration management.
Establish a Configuration Management System
1. Establish a mechanism to manage multiple levels of control.
The level of control is typically selected based on project objectives, risk, and
resources. Control levels can vary in relation to the project lifecycle, type of
system under development, and specific project requirements.
2. Provide access control to ensure authorized access to the configuration
management system.
3. Store and retrieve configuration items in a configuration management system.
4. Store, update, and retrieve configuration management records.
5. Preserve the contents of the configuration management system.
6. Revise the configuration management structure as necessary.

Create or release baselines for internal use and for delivery to the
customer.
1. Obtain authorization from the CCB before creating or releasing baselines of
configuration items.
2. Create or release baselines only from configuration items in the configuration
management system.
3. Document the set of configuration items that are contained in a baseline.
4. Make the current set of baselines readily available.

Track Change Requests

1. Initiate and record change requests in the change request database.
2. Analyze the impact of changes and fixes proposed in change requests.
3. Categorize and prioritize change requests.
Emergency requests are identified and referred to an emergency authority if
appropriate.Changes are allocated to future baselines.
4. Review change requests to be addressed in the next baseline with relevant
stakeholders and get their agreement.

Perform configuration audits to maintain integrity of the configuration

baselines.
1. Assess the integrity of baselines.
2. Confirm that configuration management records correctly identify
configuration items.
3. Review the structure and integrity of items in the configuration management
system.
4. Confirm the completeness, correctness, and consistency of items in the
configuration management system.
Completeness, correctness, and consistency of the configuration management
system’s content are based on requirements as stated in the plan and the
disposition of approved change requests.
5. Confirm compliance with applicable configuration management standards and
procedures.
6. Track action items from the audit to closure.
Establish and maintain records describing configuration items.
1. Record configuration management actions in sufficient detail so the content
and status of each configuration item is known and previous versions can be
recovered.
2. Ensure that relevant stakeholders have access to and knowledge of the
configuration status of configuration items.
3. Specify the latest version of baselines.
4. Identify the version of configuration items that constitute a particular baseline.
5. Describe differences between successive baselines.
6. Revise the status and history (i.e., changes, other actions) of each
configuration item as necessary.
 CMMI MATURITY INDEX
0 1
“There is absolutely no evidence of any activities “There are ad-hoc activities present, but we are
supporting not aware of
the process” how they relate to each other within a single
process”

0
1
 2 3
“We are aware of the process but some activities “The process is well defined, understood and
are still implemented”
incomplete or inconsistent; there is no overall
measuring or
control”

2
 3

2 3

3
2

3
3