The term common cause refers to a deviation from the normal in a project management system, but a deviation that is inherent and predictable. While this may seem contradictory, it actually makes tremendous sense. An example of a common cause, also referred to as a random cause, could be as follows: lightening strikes. Lightening strikes are inherently unpredictable. The location in which they strike is completely deviant. There is no consistency and no predictability in determining where they will strike. However, the fact that their strike locations cannot be predicted is predictable. And the fact that lightening will strike during a storm is predictable. Common causes, when displayed on a control chart, are indicated by random patterns of points within the otherwise set control limits. Common causes, when expected and prepared for, are rarely of any real negative consequence to a project team. However, if they are not taken into consideration during the project planning process, they can be more than a simple nuisance. They can cost time and money.
Quality Management
Common Cause
1 min read
Updated Jul 27, 2017
Project Victor archive
Keep reading
Related answers from the library.
Marginal Analysis vs. Cost-Benefit Analysis
Marginal analysis and cost-benefit analysis are related but distinct concepts, particularly when applied to quality management in projects. While both are decision-making…
Quality Checklists
Understanding Quality Checklists in Project Management Quality checklists are essential tools in project management that help ensure deliverables meet predefined standards and…
Verified Deliverables
Verified deliverables are a key concept in project management, specifically within the Control Quality and Validate Scope processes. These deliverables refer to…
Verification
Verification is a critical quality assurance process in project management, focused on evaluating whether a product, component, or service has been built…