Causal Analysis and Resolution Procedure
description
Transcript of Causal Analysis and Resolution Procedure
Causal Analysis and Resolution Procedure
Document Revision History
Document Status (e.g. Draft, Final, Release #):
Change Request# (Optional)
Document Version
Approval Date Modified By Section, Page(s) and Text Revised
Note: Template Revision History can be found in Hidden Text.
Template Revision History (Hidden Text)
Saved 14 March 2011 HP Restricted Page 1 of 4© 2011 Hewlett-Packard Development Company, L.P. All rights reserved.
document.doc
Causal Analysis and Resolution Procedure
Saved 14 March 2011 HP Restricted Page 2 of 4© 2011 Hewlett-Packard Development Company, L.P. All rights reserved.
document.doc
Causal Analysis and Resolution Procedure
Causal Analysis and Resolution Procedure
PURPOSE
The purpose of causal analysis and resolution includes the following:
Prevent the introduction of defects or problems before a task begins, or leverage sucesses
Analyze outcomes relating to the performance of any type of project/work
Determine and record causes
Initiate action on high priority causes to eliminate the causes and prevent the occurrence in the future
Monitor the effectiveness of the implementation of the action(s)
SELECTION CRITERIA
The causal analysis and resolution procedure is applicable for analyzing selected outcomes. It will be
performed as part of on-going work and at the end of major verification and validation activities, or
such intervals as determined by the Project Manager and documented in the Quality Plan for the
program, project or function.
RESPONSIBLE
Program, Project or function Manager [Responsible]
Team Member [Responsible]
Project Quality Engineer [Support]
Infrastructure Team [Support]
Business Process Team [Support]
INPUTS/OUTPUTSInputs Outputs
QA Audit Data
Work Product Review Report
Issues/Decisions Log
Variance Analysis Report
Problem Data
Incident Data
Test Defects Log
Project Process Baselines
Quality Plan
Survey Data (Client feedback)
Causal Analysis Report
Corrective Action Report
Saved 14 March 2011 HP Restricted Page 3 of 4© 2011 Hewlett-Packard Development Company, L.P. All rights reserved.
document.doc
Causal Analysis and Resolution Procedure
Step Action
1. 1 Review and Prioritize Problems and Defects
During the program, project or other support/work, according to the project schedule and the Causal Analysis Addendum of the Quality Plan, review defects and problems to determine which outcomes to analyze in a priority order based on the criteria and defined objectives. The results of this evaluation should include outcomes referred by other groups to the team and direct attention on the outcomes which have the highest priority due to importance to the client, cost or other factors considered during this prioritizing step.
2. Problem Description
Once an area has been prioritized and the description of the outcome being investigated has been documented, assign appropriate resources to execute the causal analysis and resolution activities.
3. Identify Supporting Data Sources
Identify the sources of data to support the analysis.
4. Complete Problem Analysis
Use appropriate root cause analysis tools and methods to determine the root cause.
One method is to identify and assign a cause to each selected outcome by conducting a facilitated meeting with team members responsible for the work product or activity involved. Other methods, such as reviewing graphs, Kano or 5 Whys, should also be considered for determining causes. Document the results of the analysis in the Causal Analysis Report.
5. Document Recommendations
Identify action proposal(s) based on the causal analysis and document in the Corrective Action Report. Rank actions according to a set of predetermined criteria used to prioritize all actions.
6. Implement Actions
Address actions in order of priority. If the cause is at the project or team level, implement the action(s). If the cause is outside the project or team, address the need for resolution through the mechanism appropriate to the group responsible for the cause. This could include change request(s) to the appropriate group.
7. Monitor and Document Results
Monitor implementation. Produce tracking reports to measure and show the effect of the action. Track the action to closure.
8. Evaluate
Based on the causal analysis plan, documented in the Causal Analysis Addendum of the Quality Plan, periodically review the effectiveness of the actions taken and provide feedback to the team on the causal analysis conducted and the results achieved. If the action did not have the expected result, determine if further analysis and additional actions are necessary. Communicate causal analysis data for use across the team/project and the organization.
Saved 14 March 2011 HP Restricted Page 4 of 4© 2011 Hewlett-Packard Development Company, L.P. All rights reserved.
document.doc