Experiences In Root Cause Analysis And Defect Prevention .
Experiences inRoot Cause Analysis andDefect Prevention MethodsKelly L. LanierRaytheonNetwork Centric Systemsklanier@raytheon.comCopyright 2003 -- Raytheon Company,
Case for ActionDeliver Quality and Reduce Costly Rework!Six Sigma Specialist Project thatfocused in reducing escaping defects.Design defects that escape toIntegration are 10 times moreexpensive than if they were caughtin the Design stage.Another thing to note is that one of thebiggest problems we have found with cost andschedule is in integration.Copyright 2004 -- Raytheon Company,Output of a R6SProjectCharacterization
Set the FoundationDefine and agree to the the following:– DefectA flaw or imperfection that results in incorrect software. Adefect may or may not be detected during software use.A deficiency which has the potential of producing incorrectresponse orundesired effect.– Comment TypeAssignment, checking, performance, etc.– Comment Priority1 through 5Copyright 2004 -- Raytheon Company,
When to Count a DefectCount a defect if:– The requirements documentation could lead toincorrect source codeBy being incorrectOr by leading to incorrect designEtc.– The design documentation could lead to incorrectsource codeBy being incorrect itselfOr by being easy to misunderstand– The source code is incorrectCopyright 2004 -- Raytheon Company,
Defect Analysis and PreventionDefect Analysis is the process of analyzing adefect to determine its root cause.Defect Prevention is the process of addressingroot causes of defects to prevent their futureoccurrence.Copyright 2004 -- Raytheon Company,
Process FocusDefect ContainmentfocusDefect Preventionfocus– Preventing theoccurrence of anindividual defect orgroup of defectsCopyright 2004 -- Raytheon Company,RequirementsStage Detected– Finding defects in thestage they wereintroduced and asearly in the lifecycle aspossible– Eliminating escapingdefectsStage OriginatedDesignCode & TestSWIntegrationQual TestSYSIntegration 0Qual otals9316622525140Code & TestSWIntegration316573510Focus onDefect ContainmentANDDefect Prevention11
Defect Analysis and PreventionProcessDefect Analysis andPreventionSelect Defects forFurther AnalysisCCBs, Peer Reviews,Defect ContainmentMetricPareto ChartsRe-evaluateSelect mprovementCopyright 2004 -- Raytheon Company,ImplementAction PlanGet DetailedDefect Datafrom DefectLogger andSynergyDevelopAction PlanandMeasurementfor SuccessPerformCausalAnalysisIdentify RootCauses y andPrioritizeImprovementOpportunitiesNext Priority
Select Defects forFurther AnalysisCCBs, Peer Reviews,Defect ContainmentMetricPareto ChartsSelect DefectsSelect Defects forFurther AnalysisThe program metrics analysis team regularlyreviews defect data to determine if defectanalysis is necessary– Defect metric has exceeded threshold– Defect data shows a trend– Individual defect is flagged for analysisCopyright 2004 -- Raytheon Company,
Defect Analysis andPreventionGet DetailedDefect Datafrom DefectLogger andSynergyPerformCausalAnalysisAnalysis ToolsIdentify RootCauses tp://homext.ray.com/sixsigmaFive Whys?FishboneDefect Containment MatrixStage OriginatedStage DetectedRequirementsDesignCode & Code & TestSWIntegrationQual TestSYSIntegration Post-ReleaseTotals3165735Qual otals9316622525140Copyright 2004 -- Raytheon Company,1011
MonitorAgainstPlannedMeasurementImplementAction PlanDevelopAction PlanandMeasurementfor provementIdentify andPrioritizeImprovementOpportunitiesNext PriorityContinuousImprovement (1 of 3)Identify and prioritize improvementopportunities based on the potentialsolutions to defect root causeSubmit improvement opportunities to theorganization via the OrganizationalImprovement WebsiteCopyright 2004 -- Raytheon Company,
MonitorAgainstPlannedMeasurementImplementAction PlanDevelopAction PlanandMeasurementfor provementIdentify andPrioritizeImprovementOpportunitiesNext PriorityContinuousImprovement (2 of 3)Organizational Improvement Website– A proposal is a request to have the SWECorganization evaluate, select, and adopt arecommended improvement and to provide a fundingand evaluation path for the proposal.– An advisory is an informational message to the SWECorganization advising that a program is providing afunding and evaluation path for an improved process,method, tool, technology, etc to support its ownbusiness/project goals. However, this improvementmay have relevance to the organization at large andhave strategic importance to the enterpriseCopyright 2004 -- Raytheon Company,
MonitorAgainstPlannedMeasurementImplementAction PlanDevelopAction PlanandMeasurementfor provementIdentify andPrioritizeImprovementOpportunitiesNext PriorityContinuousImprovement (3 of 3)Work as a Six Sigma Project– Create an action plan for the improvementInclude how to measure success of theimprovement– Implement the action plan– Monitor the progress of the action planTrack progress for measurementof success– Communicate the results to theprogram & organizationCopyright 2004 -- Raytheon Company,
MonitorAgainstPlannedMeasurementImplementAction PlanDevelopAction PlanandMeasurementfor provementIdentify andPrioritizeImprovementOpportunitiesNext PriorityDefect PreventionExamples–––––New checklistsModified processesUpdated plansScheduled trainingTool supportCopyright 2004 -- Raytheon Company,
MonitorAgainstPlannedMeasurementImplementAction PlanDevelopAction PlanandMeasurementfor provementIdentify andPrioritizeImprovementOpportunitiesNext PriorityDefect PreventionCheck to mark a defectCheck to analyzeCopyright 2004 -- Raytheon Company,
Organization Defect Analysis andPrevention ProcessDefect Analysis andPreventionSelect Defects forFurther AnalysisOut of Threshold OrgDefect Metric, QuarterlyProcess CapabilityAnalysisGet DetailedProgramDefect DataRe-evaluateSelect DefectsLevel 5 ausalAnalysisIdentify RootCauses andSolutionsIdentify mentProposalNext PriorityContinuousImprovementCopyright 2004 -- Raytheon Company,Program Defect Analysis and Prevention
ResultsSW EC Defect Containm ent T rend100%90%84%81%80%70%60%Upper DROVCopyright 2004 -- Raytheon Company,Nom inal valueLower DROV4Q033Q032Q031Q034Q023Q022Q021Q02Dec011Sep0Jul 01May011Apr 0Mar01Feb0150%M ean P erform anc e
Defect DensitySWEC Defect Density TrendUpper DROVNominal valueLower DROV4Q033Q032Q031Q034Q023Q022Q021Q02CMMI Level 5September 2003Jul 01Sep01Dec0101MayApr 01Mar01Feb01CMM Level 4June 2001Mean PerformanceImproved Defect Density by 44 percentage points, and reduced variation by 31%Copyright 2004 -- Raytheon Company,
SummaryOut of phase defects cause expensive reworkUse common definitions and counting approachFocus on defect detection and preventionAnalyze metrics at least monthly using R6 toolsPrioritize and implement defect preventionactivitiesPromote lessons learned to the organizationCopyright 2004 -- Raytheon Company,
Defect Analysis and Prevention Defect Analysis is the process of analyzing a defect to determine its root cause. Defect Prevention is the process of addressing root
USING SAP ROOT CAUSE ANALYSIS & SYSTEM MONITORING FOR SYBASE UNWIRED PLATFORM 6 2. ROOT CAUSE ANALYSIS FOR SUP IN SOLUTION MANAGER After SMD Managed System Setup and Configuration, the Root Cause Analysis features of SAP Solution Manager Diagnostics are available in the Root Cause Analysis work center of SAP Solution Manager. Find further information about End-to-End Root Cause Analysis on SAP .
WHAT IS ROOT CAUSE ANALYSIS? 2 Root cause analysis (RCA), is a structural step by step technique that focuses on finding the real cause of a problem and deals with it. Root Cause Analysis is a procedure for ascertaining and analyzing the cause of problems, to determine how these problems can be solved or be prevented from occurring. 8.6.2014
"Fishbone" Diagram: Measures Top Primary Root-Cause Primary Root-Cause Second level Root-Cause Third level Root-Cause Fourth level Root-Cause Measures Education & Training To Recognize Fatigue Failure Of IRS Fatigue Management Systems Political Will Regulation & Policy Under-Reporting Hours Of Service (HOS) Recording Device
ROOT CAUSE ANALYSIS AND ACTION PLAN FRAMEWORK TEMPLATE The Joint Commission Root Cause Analysis and Action Plan tool has 24 analysis questions. The following framework is intended to provide a template for answering the analysis questions and aid organizing the steps in a root cause analysis
ROOT CAUSE ANALYSIS GUIDANCE DOCUMENT. 1. SUMMARY. This document is a guide for root cause analysis specified by DOE Order 5000.3A, "Occurrence Reporting and Processing of Operations Information."Causal factors identify program control deficiencies and guide early corrective actions.As such, root cause analysis is central to DOE Order 5000.3A.
The Problem with Root Cause Analysis Method A Method B Method C Method G Method E Method H Method J Method F Method D Method I No‐one can agree on "what is a root cause." Everyone says they do "root cause analysis,"yet everyone is doing something different!
It can be used on its own or in conjunction with the fishbone diagram analysis in moving from the chosen root cause to the true root cause. Simply ask Why 5 times starting with the effect of the problem. 5 Whys focuses the investigation toward true root cause
2013-11-05 Root Cause Analysis Beginner LISA 2013 Stuart Kendrick 16 Why No Root Cause? Why do I claim there is no such thing as a Root Cause? Consider the server which goes down; your monitoring system pages you; you investigate. Turns out the power supply died -you replace the power supply, the server reboots, everyone is happy again.
