Copyright © 2003 by Cooliemon TM, LLC 1 Causal Analysis & Resolution (CAR) at Level 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead.

Slides:



Advertisements
Similar presentations
Copyright The Info-Tech Research Group Inc. All Rights Reserved. D1-1 by James M. Dutcher Strategic IT Planning & Governance Creation H I G H.
Advertisements

Implementing CMMI® for Development Version 1.3
Roadmap for Sourcing Decision Review Board (DRB)
Kai H. Chang COMP 6710 Course NotesSlide CMMI-1 Auburn University Computer Science and Software Engineering Capability Maturity Model Integration - CMMI.
27-Feb-01 1 Implementing Effective Requirements Practices Presented by Dr. Ralph R. Young Director, Software Engineering Systems and Process Engineering.
National Cheng-Kung University
Capability Maturity Model Integration CMMI®
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
Copyright 2005 CMMI and ITIL Alison Adams & Kieran Doyle.
Copyright 2003 CMMI: Executive Briefing Presented by Kieran Doyle
Copyright 2003, ProcessVelocity, LLP. CMM and Capability Maturity Model are registered in the U.S. Patent and Trademark Office. CMMI and SCAMPI are service.
SEI White Paper: Process Maturity Model Present by Hui Huang November 16, 2000 ® CMM is Registered in the US Patent and Trademark Office.
SE 450 Software Processes & Product Metrics 1 Quality Systems Frameworks.
Chapter 10 Quality Improvement.
CMMI Overview Quality Frameworks.
Organizational Project Management Maturity: Roadmap to Success
Roadmap for Breakthrough Change
Overview of DMAIC A Systematic Framework for Problem Solving
Space and Airborne Systems NDIA/SEI CMMI Technology Conference Presented by N. Fleischer 1 Raytheon’s Six Sigma Process and Its Application for CMMI By.
Managing Project Quality
Project Management Methodology More about Quality Control.
Using Six Sigma to Achieve CMMI Levels 4 and 5
Program Participants: Department Managers, Project Leaders, Senior officers, Black Belt candidates and anyone who desires an understanding of Lean Six.
QUALITY These slides have been added to the standard MRU PM Cert materials and are made available to students who have attended my class. Robin Hornby.
Tools for Process Improvement
CMMI Course Summary CMMI course Module 9..
Capability Maturity Model Integration
Integrated Capability Maturity Model (CMMI)
Comparing CMMI® and OPM3®
Model-Based Process Improvement Module 2. Module Objectives This module will enable students to recall information about the history of CMMI fundamentals.
© 2001 Carnegie Mellon University S8A-1 OCTAVE SM Process 8 Develop Protection Strategy Workshop A: Protection Strategy Development Software Engineering.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
Process Management Process Management in software started in late 1960’s (but informally and inconsistently) Software Engineering Institute (SEI) is the.
EngMat/JWS.PPT 10/17/ CMMI ® Today – The Current State CMMI ® Technology Conference 2003 November 18, 2003 Ron Paulson Vice President, Engineering.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Managing CMMI® as a Project
Application of the CMMI SM to Plan and Control Life Cycle Costs Dr. Mary Anne Herndon Science Applications International Corporation (SAIC) November, 2003.
@2002 Copyright, Itreya Technologies CMMI kick off July 2005.
Software Engineering - I
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
CSE4002CMMI Capability Maturity Model Integration (CMMI) CMMI is replacing the well established CMM rating for software developers and systems engineers.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
COPYRIGHT 2010 GENERAL DYNAMICS ADVANCED INFORMATION SYSTEMS Published and used by TwinSPIN with permission CMMI Level 5 Journey (A.K.A. Things I Wish.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Copyright © 2003 by Cooliemon TM, LLC 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead Assessor (CMM ® ) SCAMPI Lead Appraiser SM (CMMI.
An Introduction. Objective - Understand the difference between CMM & CMMI - Understand the Structure of CMMI.
Pittsburgh, PA CMMI Acquisition Module - Page M5-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
MSA Orientation – v203a 1 What’s RIGHT with the CMMI?!? Pat O’Toole
UNIT 5.
Copyright © by Quality Improvement Consultants, Inc. (QIC) Slide 1 World-Class Quality Measurably Improving Your Requirements Based on the CMMI.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
© 2004 Tangram Hi-Tech Solutions Project Management According to the CMMI1 Project Management according to the Capability Maturity Model (CMMI)
Certification: CMMI Emerson Murphy-Hill. Capability Maturity Model Integration (CMMI) Creation of the Software Engineering Institute (SEI) at Carnegie.
Staged or Continuous: Which Model Should I Choose?
A Program of Training for CMMI®-based Process Improvement
Successful Verification
Six Sigma Approach.
Compliance and Audit Block 17 Block 17.
CMMI Overview Quality Frameworks.
Process Maturity Profile
CMMI Overview.
CMMI – Staged Representation
Quality management standards
Interpretive Guidance Project: What We Know CMMI User’s Conference
Integrated Processes: On the Horizon
Acknowledgment of achievement
Copyright © by Quality Improvement Consultants, Inc. (QIC) 1 World-Class Quality Staged or Continuous: Which Model Should I Choose? ® CMM is.
Requirements Development in CMMI
Capability Maturity Model
Presentation transcript:

Copyright © 2003 by Cooliemon TM, LLC 1 Causal Analysis & Resolution (CAR) at Level 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead Assessor (CMM ® ) SCAMPI Lead Appraiser SM (CMMI ® ) ® CMM and CMMI is registered in the U.S. Patent and Trademark Office. SM IDEAL is a service mark of Carnegie Mellon University.

Copyright © 2003 by Cooliemon TM, LLC 2 Special Permission Special permission to reproduce and adapt portions of: Software Engineering Process Group Guide, CMU/SEI-90-TR-024, (c) 1990 by Carnegie Mellon University Capability Maturity Model ® Integration (CMMI ® ), Version 1.1 (CMMI SM - SE/SW/IPPD/SS, V1.1) Continuous Representation, CMU/SEI-2002-TR-011, (c) 2002 by Carnegie Mellon University Capability Maturity Model ® Integration (CMMI ® ), Version 1.1 (CMMI SM - SE/SW/IPPD/SS, V1.1) Staged Representation, CMU/SEI-2002-TR-012, (c) 2002 by Carnegie Mellon University Standard CMMI SM Assessment Method for Process Improvement: Method Definition, Version 1.1 (SCAMPI SM, V1.1), CMU/SEI-2001-HB-2001, (c) 2001 by Carnegie Mellon University is granted by the Software Engineering Institute. ® CMMI, CMM and Capability Maturity Model are registered in the U.S. Patent and Trademark Office. SM IDEAL and SCAMPI are service marks of Carnegie Mellon University.

Copyright © 2003 by Cooliemon TM, LLC 3 About Cooliemon, LLC The mission of Cooliemon, LLC is: helping organizations achieve excellence through process improvement Our goal is to focus your process improvement efforts to: improve quality and productivity reduce operating costs (i.e., reduce rework, waste and duplicate effort) capture the market with high quality products and services help you become the industry standard by which your competitors measure themselves

Copyright © 2003 by Cooliemon TM, LLC 4 Causal Analysis and Resolution Purpose: To identify causes of defects and other problems and take action to prevent them from occurring in the future. CMMI V1.1 SG 1: Determine Causes of Defects Root causes of defects and other problems are systematically determined. SG 2: Address Causes of Defects Root causes of defects and other problems are systematically addressed to prevent their future occurrence. SG = Specific Goal

Copyright © 2003 by Cooliemon TM, LLC 5 Objectives Describe how CAR can be used to build Senior Management commitment for Quality. Overview of Jurans Quality Improvement Process - a practical example of the CAR a CMMI ® Process Area (PA). When to use Quality Tools (e.g., Pareto, Cause & Effect diagrams, Brainstorming, etc.) Answer any of your questions.

Copyright © 2003 by Cooliemon TM, LLC 6 Agenda Proof of the Need Selecting a Strategy, Problem & PAT Determine Causes of Defects Address Causes of Defects Holding The Gains Summary

Copyright © 2003 by Cooliemon TM, LLC 7 Proof of the Need The cost of poor quality (COPQ): COPQ is the sum of all costs that would disappear if there were no quality problems. - Juran You can easily spend % of your sales dollars on the COPQ. - Crosby In most companies the costs of poor quality runs at %. - Juran

Copyright © 2003 by Cooliemon TM, LLC 8 List Potential Problems Compile a list of improvement opportunities. Example sources: Accounting data on COPQ Benchmarking reports External customer complaints Internal customer complaints Process improvement suggestions Surveys Simply talk to people etc.

Copyright © 2003 by Cooliemon TM, LLC 9 Agenda Proof of the Need Selecting a Strategy, Problem & PAT Determine Causes of Defects Address Causes of Defects Holding The Gains Summary

Copyright © 2003 by Cooliemon TM, LLC 10 Select: Strategy,Problem to be solved & PAT Review/Verify Charter, Mission & Team Membership PATs Report Status: Understand, Support, Direct & Recognize Team Implement Solution & Controls Execute Process QC Updates Phase Out Team Process Recognize Team Monitor Solution to Hold the Gains Lessons Learned Adapted from Juran, Leadership for Quality, 1989 QC CAR Roadmap PAT(s) Organization

Copyright © 2003 by Cooliemon TM, LLC 11 Discover Root Causes (Diagnostic Journey): 1. analyze the symptoms 2. formulate theories 3. test theories 4. identify root causes Develop Solutions & Controls (Remedial Journey): 5. consider alternative solutions 6. design solutions and controls 7. address resistance to change 8. implement solutions and controls Holding the gains 9. design effective quality controls 10. audit the controls Juran's Quality Improvement Process Adapted from Juran, Leadership for Quality, 1989

Copyright © 2003 by Cooliemon TM, LLC 12 Selecting a Problem to Solve Selection Criteria to be considered: Chronic (a continuing problem) Vital Few (significant impact on company) Size (manageable problem <12 months) Measurable (impact must be measured) Urgency (how urgent is the problem to the organization?) Risk (what are the risks?) Resistance to Change (how high is resistance to change?)

Copyright © 2003 by Cooliemon TM, LLC 13 Example: Selection Criteria

Copyright © 2003 by Cooliemon TM, LLC 14 Select: Strategy,Problem to be solved & PAT Review/Verify Charter, Mission & Team Membership Develop Solutions & Controls Discover Root Causes Implement Solution & Controls Phase Out Team Recognize Team Monitor Solution to Hold the Gains Lessons Learned PATs Report Status: Understand, Support, Direct & Recognize Team Adapted from Juran, Leadership for Quality, 1989 QC CAR Roadmap PAT(s) Organization

Copyright © 2003 by Cooliemon TM, LLC 15 Team Charters Charters can include the following information: name of team mission statement and desired results activities and functions deliverables authorization (QC - signatures) team members estimated return on investment start date and end date team ground-rules

Copyright © 2003 by Cooliemon TM, LLC 16 Agenda Proof of the Need Selecting a Strategy, Problem & PAT Determine Causes of Defects Address Causes of Defects Holding The Gains Summary

Copyright © 2003 by Cooliemon TM, LLC 17 Select: Strategy,Problem to be solved & PAT Review/Verify Charter, Mission & Team Membership Develop Solutions & Controls Discover Root Causes Implement Solution & Controls Phase Out Team Recognize Team Monitor Solution to Hold the Gains Lessons Learned PATs Report Status: Understand, Support, Direct & Recognize Team Adapted from Juran, Leadership for Quality, 1989 QC CAR Roadmap PAT(s) Organization

Copyright © 2003 by Cooliemon TM, LLC 18 Discover Root Causes (Diagnostic Journey): 1. analyze the symptoms 2. formulate theories 3. test theories 4. identify root causes Develop Solutions & Controls (Remedial Journey): 5. consider alternative solutions 6. design solutions and controls 7. address resistance to change 8. implement solutions and controls Holding the gains: 9. design effective quality controls 10. audit the controls Juran's Quality Improvement Process Adapted from Juran, Leadership for Quality, 1989

Copyright © 2003 by Cooliemon TM, LLC 19 Definitions: Symptom: A symptom is the outward observable evidence of a problem. Juran Institute, Inc. Root Cause: A root cause is the source of the problem, which, when removed, will sharply reduce or eliminate the deficiency. Juran Institute, Inc. A root cause is an antecedent source of a defect such that if it is removed, the defect is decreased or removed itself. CMMI V1.02 Discover Root Causes - 1

Copyright © 2003 by Cooliemon TM, LLC Analyze the Symptoms: understand fully the nature and extent of the problem to be solved. Tools: Flow Diagram, Data Collection, Pareto Analysis 2. Formulate Theories: a PAT should speculate about the cause of the problem versus jumping to a solution. Tools: Brainstorming, Cause-Effect Discover Root Causes - 2 Adapted from Juran, Leadership for Quality, 1989

Copyright © 2003 by Cooliemon TM, LLC 21 Example: Flow/Block Diagram Role Purpose: The process ends with... Role CUSTOMER(S) Output SUPPLIER(S) Input(s) The process begins with...

Copyright © 2003 by Cooliemon TM, LLC Test Theories: Before accepting any theory as true, a PAT should systematically test it with data. Tools: Data Collection, Graph/Charts, Histogram, Pareto Analysis, Scatter Diagram, Stratification 4. Identify Root Cause(s): Does the data help determine the root cause of the problem? Tools: Data Collection, Graph/Charts, Histogram, Pareto Analysis, Scatter Diagram, Stratification Discover Root Causes - 3 Adapted from Juran, Leadership for Quality, 1989

Copyright © 2003 by Cooliemon TM, LLC 23 Example: Data Collection 1. Formulate good questions 2. Consider appropriate data analysis tool 3. Define data collection points 4. Select unbiased collector 5. Understand data collectors & their environment 6. Design data collection forms 7. Document instructions 8. Pilot/test forms and instructions 9. Train data collectors 10. Audit the collection process & validate results Adapted from Juran Institute, Inc.

Copyright © 2003 by Cooliemon TM, LLC 24 Agenda Proof of the Need Selecting a Strategy, Problem & PAT Determine Causes of Defects Address Causes of Defects Holding The Gains Summary

Copyright © 2003 by Cooliemon TM, LLC 25 Select: Strategy,Problem to be solved & PAT Review/Verify Charter, Mission & Team Membership Develop Solutions & Controls Discover Root Causes Implement Solution & Controls Phase Out Team Recognize Team Monitor Solution to Hold the Gains Lessons Learned PATs Report Status: Understand, Support, Direct & Recognize Team Adapted from Juran, Leadership for Quality, 1989 QC CAR Roadmap PAT(s) Organization

Copyright © 2003 by Cooliemon TM, LLC 26 Discover Root Causes (Diagnostic Journey): 1. analyze the symptoms 2. formulate theories 3. test theories 4. identify root causes Develop Solutions & Controls (Remedial Journey): 5. consider alternative solutions 6. design solutions and controls 7. address resistance to change 8. implement solutions and controls Holding the gains: 9. design effective quality controls 10. audit the controls Juran's Quality Improvement Process Adapted from Juran, Leadership for Quality, 1989

Copyright © 2003 by Cooliemon TM, LLC Consider Alternative Solutions: identify possible remedies and evaluate each alternative solution in terms of impact on the problem. Tools: Brainstorming, Data Collection, Selection Matrix 6. Design Solutions & Controls: design the remedy which will entail documentation of the solution (e.g., process, procedures, standards) and controls. Tools: Control Spreadsheet, Control Chart Develop Solutions & Controls - 1 Adapted from Juran, Leadership for Quality, 1989

Copyright © 2003 by Cooliemon TM, LLC 28 Example: Control Spreadsheet Juran Institute

Copyright © 2003 by Cooliemon TM, LLC Address Resistance to Change: identify likely sources of resistance (barriers) and support (aids). Identify counter measures to the vital few barriers. Tools: Barriers/Aids, Brainstorming 8. Implement Solutions & Controls: implementing a change includes: developing a plan - involving relevant stakeholders, training and explaining why the change. Tools: Planning Matrix, Tree Diagram Develop Solutions & Controls - 2 Adapted from Juran, Leadership for Quality, 1989

Copyright © 2003 by Cooliemon TM, LLC 30 Agenda Proof of the Need Selecting a Strategy, Problem & PAT Determine Causes of Defects Address Causes of Defects Holding The Gains Summary

Copyright © 2003 by Cooliemon TM, LLC 31 Select: Strategy,Problem to be solved & PAT Review/Verify Charter, Mission & Team Membership Develop Solutions & Controls Discover Root Causes Implement Solution & Controls Phase Out Team Recognize Team Monitor Solution to Hold the Gains Lessons Learned PATs Report Status: Understand, Support, Direct & Recognize Team Adapted from Juran, Leadership for Quality, 1989 QC CAR Roadmap PAT(s) Organization

Copyright © 2003 by Cooliemon TM, LLC 32 Discover Root Causes (Diagnostic Journey): 1. analyze the symptoms 2. formulate theories 3. test theories 4. identify root causes Develop Solutions & Controls (Remedial Journey): 5. consider alternative solutions 6. design solutions and controls 7. address resistance to change 8. implement solutions and controls Holding the gains: 9. design effective quality controls 10. audit the controls Juran's Quality Improvement Process

Copyright © 2003 by Cooliemon TM, LLC Design Effective Quality Controls: determine how actual performance will be compared to the standard (i.e., record data) in order to evaluate the effect of the change. Tools: Control Chart, Control Spreadsheet, Flow Diagram 10. Audit The Controls: develop systems for reporting results. Tools: Control Chart, Control Spreadsheet, Data Collection, Graphs/Charts, Pareto, Stop Light Charts Holding the Gains Adapted from Juran, Leadership for Quality, 1989

Copyright © 2003 by Cooliemon TM, LLC 34 Agenda Proof of the Need Selecting a Strategy, Problem & PAT Determine Causes of Defects Address Causes of Defects Holding The Gains Summary

Copyright © 2003 by Cooliemon TM, LLC 35 Summary The Language of Senior Management is $money$ - CAR can be used to grab management's attention. A practical example of CAR Process Area is the Jurans Quality Improvement Process: Discover Root Causes (CAR SG 1) Develop Solution & Controls (CAR SG 2) Holding the Gains (CAR SG 2) Look for low hanging fruit for the first few problems to solve. Know when to use the appropriate tool in the Quality Improvement journey.

Copyright © 2003 by Cooliemon TM, LLC 36

Copyright © 2003 by Cooliemon TM, LLC 37 One to Grow On The competitor to be feared is one who never bothers about you at all, but goes on making his own business better all the time. (Henry Ford, Sr.)

Copyright © 2003 by Cooliemon TM, LLC 38 Contact Information Ralph Williams, President 129 Liberty Road, Harmony, PA Tel: Fax: