Select Outcomes for Analysis

Select outcomes for analysis.

This activity could be triggered by an event (reactive) or could be planned periodically, such as at the beginning of a new phase or task (proactive). Example Work Products

1. Data to be used in the initial analysis

2. Initial analysis results data

3. Outcomes selected for further analysis

Subpractices

1. Gather relevant data.

Examples of relevant data include the following: Defects reported by customers or end users Defects found in peer reviews or testing

Productivity measures that are higher than expected

Project management problem reports requiring corrective action Process capability problems

Earned value measurements by process (e.g., cost performance index) Resource throughput, utilization, or response time measurements Service fulfillment or service satisfaction problems

2. Determine which outcomes to analyze further.

When determining which outcomes to analyze further, consider their source, impact, frequency of occurrence, similarity, the cost of analysis, the time and resources needed, safety considerations, etc.

Examples of methods for selecting outcomes include the following: Pareto analysis

Histograms

Box and whisker plots for attributes Failure mode and effects analysis (FMEA) Process capability analysis

3. Formally define the scope of the analysis, including a clear definition of

the improvement needed or expected, stakeholders affected, target affected, etc.

Refer to the Decision Analysis and Resolution process area for more information about analyzing possible decisions using a formal evaluation process that evaluates identified alternatives against established criteria.

Causal Analysis and Resolution (CAR) 130

SP 1.2 Analyze Causes

Perform causal analysis of selected outcomes and propose actions to address them.

The purpose of this analysis is to define actions that will address selected outcomes by analyzing relevant outcome data and producing action proposals for implementation.

Example Work Products

1. Root cause analysis results

2. Action proposal

Subpractices

1. Conduct causal analysis with those who are responsible for performing

the task.

Causal analysis is performed, typically in meetings, with those who understand the selected outcome under study. Those who have the best understanding of the selected outcome are typically those who are responsible for performing the task. The analysis is most effective when applied to real time data, as close as possible to the event which triggered the outcome.

Examples of when to perform causal analysis include the following: When a stable subprocess does not meet its specified quality and process performance objectives, or when a subprocess needs to be stabilized During the task, if and when problems warrant a causal analysis meeting When a work product exhibits an unexpected deviation from its requirements When more defects than anticipated escape from earlier phases to the current phase When process performance exceeds expectations

At the start of a new phase or task

Refer to the Quantitative Project Management process area for more information about performing root cause analysis.

2. Analyze selected outcomes to determine their root causes.

Analysis of process performance baselines and models can aid in the identification of potential root causes.

Depending on the type and number of outcomes, it can be beneficial to look at the outcomes in several ways to ensure all potential root causes are investigated. Consider looking at individual outcomes as well as grouping the outcomes. Examples of methods to determine root causes include the following:

Cause-and-effect (fishbone) diagrams Check sheets

3. Combine selected outcomes into groups based on their root causes.

Examples of cause groups or categories include the following: Inadequate training and skills

Breakdown of communication Not accounting for all details of a task

Making mistakes in manual procedures (e.g., keyboard entry) Process deficiency

Where appropriate, look for trends or symptoms in or across groupings.

4. Create an action proposal that documents actions to be taken to

prevent the future occurrence of similar outcomes or to incorporate best practices into processes.

Process performance models can support cost benefit analysis of action proposals through prediction of impacts and return on investment.

Examples of proposed preventative actions include changes to the following: The process in question

Training Tools Methods Work products

Examples of incorporating best practices include the following:

Creating activity checklists, which reinforce training or communications related to 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, such as task kickoff meetings to review common problems as well as actions to prevent them

An action proposal usually documents the following: Originator of the action proposal

Description of the outcome to be addressed Description of the cause

Cause category Phase identified Description of the action

Time, cost, and other resources required to implement the action proposal Expected benefits from implementing the action proposal

Estimated cost of not fixing the problem Action proposal category

Causal Analysis and Resolution (CAR) 132

SG 2 Address Causes of Selected Outcomes

Root causes of selected outcomes are systematically addressed.

Projects operating according to a well-defined process systematically analyze where improvements are needed and implement process changes to address root causes of selected outcomes.

SP 2.1 Implement Action Proposals

Implement selected action proposals developed in causal analysis.

Action proposals describe tasks necessary to address root causes of analyzed outcomes to prevent or reduce the occurrence or recurrence of negative outcomes, or incorporate realized successes. Action plans are developed and implemented for selected action proposals. Only changes that prove to be of value should be considered for broad implementation. Example Work Products

1. Action proposals selected for implementation

2. Action plans

Subpractices

1. Analyze action proposals and determine their priorities.

Criteria for prioritizing action proposals include the following: Implications of not addressing the outcome

Cost to implement process improvements to address the outcome Expected impact on quality

Process performance models can be used to help identify interactions among multiple action proposals.

2. Select action proposals to be implemented.

Refer to the Decision Analysis and Resolution process area for more information about analyzing possible decisions using a formal evaluation process that evaluates identified alternatives against established criteria.

Examples of information provided in an action plan include the following: Person responsible for implementation

Detailed description of the improvement Description of the affected areas

People who are to be kept informed of status Schedule

Cost expended

Next date that status will be reviewed Rationale for key decisions

Description of implementation actions

4. Implement action plans.

To implement action plans, the following tasks should be performed: Make assignments.

Coordinate the people doing the work. Review the results.

Track action items to closure.

Experiments may be conducted for particularly complex changes. Examples of experiments include the following:

Using a temporarily modified process Using a new tool

Actions may be assigned to members of the causal analysis team, members of the project team, or other members of the organization.

5. Look for similar causes that may exist in other processes and work

products and take action as appropriate.