SP 1.2 Analyze Causes

CMMI for Development, version 1.2

4. Generic Goals and Practices, Process Areas

4.2. CAUSAL ANALYSIS AND RESOLUTION

SG 1 Determine Causes of Defects

SP 1.2 Analyze Causes

Process Area	CAR
Level	5
Goal	SG 1
Practice	SP 1.2

Perform causal analysis of selected defects and other problems and propose actions to address them.

The purpose of this analysis is to develop solutions to the identified problems by analyzing the relevant data and producing action proposals for implementation.

Typical Work Products

1. Action proposal

Subpractices

1. Conduct causal analysis with the people who are responsible for performing the task.

Causal analysis is performed, typically in meetings, with those people who have an understanding of the selected defect or problem under study. The people who have the best understanding of the selected defect are typically those responsible for performing the task.

Examples of when to perform causal analysis include the following:

· When a stable process does not meet its specified quality and process-performance objectives

· During the task, if and when problems warrant a causal analysis meeting

· When a work product exhibits an unexpected deviation from its requirements

Refer to the Quantitative Project Management process area for more information about achieving the project’s quality and process-performance objectives.

2. Analyze selected defects and other problems to determine their root causes.

Depending on the type and number of defects, it may make sense to first group the defects before identifying their root causes.

Examples of methods to determine root causes include the following:

· Cause-and-effect (fishbone) diagrams

· Check sheets

3. Group the selected defects and other problems based on their root causes.

Examples of cause groups, or categories, include the following:

· Inadequate training

· Breakdown of communications

· Not accounting for all details of a task

· Making mistakes in manual procedures (e.g., typing)

· Process deficiency

4. Propose and document actions that need to be taken to prevent the future occurrence of similar defects or other problems.

Examples of proposed actions include changes to the following:

· The process in question

· Training

· Tools

· Methods

· Communications

· Work products

Examples of specific actions include the following:

· Providing training in common problems and techniques for preventing them

· Changing a process so that error-prone steps do not occur

· Automating all or part of a process

· Reordering process activities

· Adding process steps to prevent defects, such as task kickoff meetings to review common defects and actions to prevent them

An action proposal usually documents the following:

· Originator of the action proposal

· Description of the problem

· Description of the defect cause

· Defect cause category

· Phase when the problem was introduced

· Phase when the defect was identified

· Description of the action proposal

· Action proposal category

Keywords : adequate ; causal analysis ; data ; document ; objective ; process ; process area ; product ; project ; quality ; quality and process-performance objectives ; reference ; requirement ; root cause ; stable process ; subpractice