Quality Management in Projects - Assignment - Group 1
Quality Management in Projects - Assignment - Group 1
Quality Management in Projects - Assignment - Group 1
The philosophy of Quality has traditionally focused upon the development and
implementation of a corporate wide culture that emphasizes a customer focus, continuous
improvement, employee empowerment, and data driven decision making. The drivers of this
philosophy are rooted in the alignment of product and service systems design with customer
expectations, along with the focusing on quality during all phases of development,
production, and delivery. The philosophy is process centric and emphasizes the reduction of
variability as well as a continuous improvement in the functionality of the final product or
service. It is widely recognized that quality cannot be inspected into a product or service; it
needs to be planned for and design into the product or service system. If this exercise is
performed incorrectly, a quality result cannot be achieved.
Quality Trilogy: Juran broke down the requirements for successful TQM into 3 major
activities: Quality Planning, Quality controlling and Quality Improvement.
QP QC
QI
1. Quality Planning: Quality Planning begins with identifying customers both external
n internal, determining their needs and developing product features that respond to those
needs.
2. Quality Controlling: Process involved with –determining what to control, establish
units of measurement to evaluate data objectively establish standards of performance,
measuring actual performance, interpreting the different between actual performance and the
standard and finally corrective action on the difference.
3. Quality Improvement: focuses on long term goal seeking to achieve quality break
through that move the firm to a new level of performance.
PHILLIP CROSBY
Crosby’s philosophy focused upon reducing cost through quality improvement. He stressed
that both high-end and low-end products could have high levels of quality. His philosophy
emphasized;
Quality means conformance to requirements.
There is no such thing as a quality problem.
There is no such thing as the economics of quality; doing the job right the first
time is always cheaper.
The only performance measurement is the cost of quality, which is the
expense of non-conformance.
The only performance standard is “Zero Defects”.
Crosby’s Cost of Quality:
Critical-for-Quality (CoQ) is frequently characterized as the sum of costs associated with
insuring conformance to standards and the costs associated failing creating a quality product
or service on the first pass (e.g. non-conformance). Thus, every time a defective product is
produced, or a less than satisfactory service is delivered, the cost of quality increases.
Examples include reworking a manufactured item, retesting an assembly, rebuilding a tool,
correction of a bank statement, or the reworking of a service, such as the reprocessing of a
loan operation or the replacement of a food order in a restaurant. In other words, any cost
incurred as the result of failing to produce a quality item the first time, contributes to the cost
of quality.
Feigenbaum classified quality costs into three main categories: prevention, appraisal, and
failure. The basic premise of this P-A-F model is that investments in prevention and appraisal
activities will reduce failures, and that continued investments in prevention activities will
lead to reduction in appraisal costs. The costs categories in the P-A-F model are generally
described as follow;
Prevention costs are those costs associated with all activities designed to prevent poor
quality. Examples include;
New product reviews
Quality planning
Supplier capability surveys and certification programs
Process capability evaluations
Quality improvement projects and associated team meetings
Quality education and training
Appraisal costs are those costs associated with the measuring, evaluating or auditing to
assure conformance to quality standards and performance requirements. Examples include;
• Incoming and source inspection/test of purchased material
• In-process and final inspection/test
• Product, process or service monitoring and control systems and audits
• Maintenance and calibration of measuring and test equipment
• Associated supplies and materials
Internal failure costs are those costs resulting from not conforming to specifications. Here,
the defect is caught prior to delivery of the product, or the furnishing of a service, to the
customer. Examples include;
Scrap and its associated opportunity costs
Rework
Re-inspection
Re-testing
Material review
Downgrading of materials or services
External failure costs are those costs associated with the defect being caught after delivery of
the product. In these cases, an additional service has to be provided to the customer.
Examples include;
• Processing customer complaints
• Customer returns
• Warranty claims
• Product recalls
• Lost sales (typically unknowable)
Accepting Crosby’s definition of quality as “conformance to requirements”, CoQ’s can be
calculated as the sum of the price of conformance and the price of non-conformance. The
principle differences of this calculation form the P-A-F model is that price is defined as
including all the benefits, overheads, and whatever else that is associated with the real costs
of the company.
The British Standards Institute, in an effort to extend the concept of quality costing to all
functions of an enterprise and to non-manufacturing organizations, published a model
focused on process costs (BS 6143: Part 1, 1992). In this model, the CoQ’s are collected for a
specific process, as 14 opposed to the whole company. This model pursues a continuous
improvement approach to process management that is reflective of both the Kaizen approach
and to Deming’s (1986) Plan-Do-Check-Act (PDCA) cycle.
ARMAND FEIGENBAUM
Feigenbaum believed that TQM was the most effective method for integrating the various
quality activities of multiple groups in an organization while enabling production and
services to deliver customer satisfaction at its most economical level. Furthermore, he
believed that in the typical non-TQM manufacturing environment there was so much extra
work being performed in correcting mistakes that there was essentially a “hidden” plant
within the factory. Most importantly, he believed that quality was everyone’s job, and
without upper management actively and visibly involved, no one would do it.
Feigenbaum stressed that quality did not mean the best performing, or the best technical
option. Instead, it mean the best for the customer’s usage. In the system that he envisioned,
quality control was a four (4) step management tools involving: setting of quality standards,
appraising conformance to those standards, acting when standards were not meet or were
exceeded, and planning for improvements in the standards. The following tenets sum up the
essences of Feigenbaum’s system of TQM;
• Quality is a companywide process.
• The customer defines quality.
• Effective quality requires both individual and team effort.
• Quality is a management philosophy.
• Quality and innovations are mutually dependent.
• Quality is an ethical standard.
• Quality requires continuous improvement. –quality improvement leads to quantity
improvement.
• Quality is the most cost effective method for improving productivity.
CONCLUSION
Thus, TQM is an operational philosophy where the ultimate focus is customer and their
satisfaction. To fulfil the customer’s need and wants as well as for business growth; all the
quality gurus suggested that to develop a culture for continuous improvement. They also
explained that continuous improvement is a process to build a system that can consistently
produce a quality product / services. Here, both management and the workers role are crucial
because they must identify and eliminate waste and variability through-out system; take the
equal responsibility for proper tools and knowledge uses and team leadership and
empowerment for entire organization. This is not so easy task but it is possible and generic. If
any organization really wants to develop a culture for continuous improvement, the top
management must develop and follow some strategic steps for long term achievement.
DESIGN FOR QUALITY
Design Process
Quality of Design is organized into five major activities, with multiple steps in each. As we
have just noted, the design process has definite elements of linearity, but the specific tools
applied ensure and facilitate collegial work in parallel. The five major activities are:
• Define
• Discover
• Design
• Develop
Define
The first step is to describe in general terms what the product is and what set of customers it
is intended to serve. There may be multiple different target customers. The project charter
includes not only this description of the product and target customers, but also the specific
measured goals for the product. The specific goals adopted will depend on the product and its
role in the enterprise strategy. These goals usually include:
• Market share
• Price point
• Margin
• Lead times
• Launch date
• Performance in terms of quality, cost, cycle time, or the like
• Customer loyalty
Discover
Quality by Design requires the discipline to discover the exact needs of the customer –
expressed in terms of the benefit that the customer is seeking. The needs must be specific and
measurable so that we can design to them and measure our success in meeting them.
There are usually multiple customers – both internal and external – and some of them are
hidden from our usual view of the business
Quality by Design incorporates robust science into the measurement and analysis of needs. In
some cases this will be rather straightforward, but many cases will require the application of
advanced survey and statistical techniques.
At this point, the project begins the completion of a series of planning worksheets that
directly tie:
• Customer to …
• Customer need to …
• Functional feature and goals to …
• Detailed design features and goals to …
• Process features and goals to …
• Control features and goals.
This systematic structure ensures that we meet all-important customer needs and that every
feature in the design, production, and control of the delivery has a useful role and can be
related unambiguously to the customers’ needs.
Design
Once we know what the customer needs, we must design the product that will meet those
needs better than competitors’ and preceding products. Design, of course, encourages
creativity and insight to meet needs in new and exciting ways that will appeal to the
customer. While it may seem contradictory to insist on structure to achieve creativity that is
exactly what is required. The proper structure encourages creativity and provides a safety net
that allows the team to push the limits of creative ideas without running unnecessary risks.
Quality Design encourages multiple approaches to designing, including:
• Benchmarking
• Creative thinking techniques
• Competitive assessment
• Multiple alternative evaluation
The designs are solidly tied to reality through the application of …
• Market competitive analysis
• Deconstruction competitive analysis
• Salability analysis
• Multiple tools to assess failure modes and probability of failure
• Explicit trade-off analysis
• Design reviews at several stages
• Advanced techniques when needed, such as design of experiments, including non-
linear response surfaces
• Value analysis to ensure that every dollar spent brings a return on the investment
Develop
Once the product is designed then the designers turn to the equally important job of
developing the process for delivery. Process design is strongly rooted in a full understanding
of the effects of variability and the need to measure and optimize process capability.
Finally, no design is complete without a rigorous control plan that will assure that the process
will continue to run free of defects indefinitely.
Deliver
The job is not done until the product is in production, meeting all the goals set out in the
charter, and delighting the customers. Effective delivery relies on strong planning from
transfer to operations, a scale-up strategy, and validation of the transfer.
SERVICE DESIGN
Service design is the activity of planning and organizing a business’s resources (people,
props, and processes) in order to (1) directly improve the employee’s experience, and (2)
indirectly, the customer’s experience.
Components of service design
There are three components of service design i.e.
People. This component includes anyone who creates or uses the service, as well as
individuals who may be indirectly affected by the service.
Examples include:
• Employees
• Customers
• Fellow customers encountered throughout the service
• Partners
Props. This component refers to the physical or digital artifacts (including products) that are
needed to perform the service successfully.
Examples include:
• Physical space: storefront, teller window, conference room
• Digital environment through which the service is delivered
• Webpages
• Blogs
• Social Media
• Objects and collateral
• Digital files
• Physical products
Processes. These are any workflows, procedures, or rituals performed by either the employee
or the user throughout a service.
Examples include:
• Withdrawing money from an ATM
• Getting an issue resolved over support
• Interviewing a new employee
• Sharing a file
Benefits of Service Design
Most organizations’ resources (time, budget, and logistics) are spent on customer-facing
outputs, while internal processes (including the experience of the organization’s employees)
are overlooked. This disconnect triggers a common, widespread sentiment that one hand does
not know what the other is doing.
Service design bridges such organizational gaps by:
Surfacing conflicts. Business models and service-design models are often in conflict because
business models do not always align with the service that the organization delivers. Service
design triggers thought and provides context around systems that need to be in place in order
to adequately provide a service throughout the entire product’s life cycle (and in some cases,
beyond).
Fostering hard conversations. Focused discussion on procedures and policies exposes weak
links and misalignment and enable organizations to devise collaborative and cross functional
solutions.
Reducing redundancies with a bird’s-eye view. Mapping out the whole cycle of internal
service processes gives companies a bird’s-eye view of its service ecosystem, whether within
one large offering, or across multiple sub offerings. This process helps pinpoint where
duplicate efforts occur, likely causing employee frustration and wasted resources. Eliminating
redundancies conserves energy, improves employees’ efficiency, and reduces costs.
Forming relationships. Service design helps align internal service provisions like roles,
backstage actors, processes, and workflows to the equivalent frontstage personnel. To come
back to our initial example, with service design, information provided to one agent should be
available to all other agents who interact with the same customer.
QUALITY FUNCTION DEPLOYMENT (QFD)
Quality Function Deployment (QFD) is a process and set of tools used to effectively define
customer requirements and convert them into detailed engineering specifications and plans to
produce the products that fulfil those requirements.
Benefits of quality function deployment
Customer Focused: QFD methodology places the emphasis on the wants and needs of the
customer, not on what the company may believe the customer wants. The Voice of the
Customer is translated into technical design specifications. During the QFD process, design
specifications are driven down from machine level to system, sub-system and component
level requirements. Finally, the design specifications are controlled throughout the production
and assembly processes to assure the customer needs are met.
Voice of Customer Competitor Analysis: The QFD “House of Quality” tool allows for
direct comparison of how your design or product stacks up to the competition in meeting the
VOC. This quick analysis can be beneficial in making design decisions that could place you
ahead of the pack.
Shorter Development Time and Lower Cost: QFD reduces the likelihood of late design
changes by focusing on product features and improvements based on customer requirements.
Effective QFD methodology prevents valuable project time and resources from being wasted
on development of non-value added features or functions.
Structure and Documentation: QFD provides a structured method and tools for recording
decisions made and lessons learned during the product development process. This knowledge
base can serve as a historical record that can be utilized to aid future projects.
Companies must bring new and improved products to market that meet the customer’s actual
wants and needs while reducing development time. QFD methodology is for organizations
committed to listening to the Voice of the Customer and meeting their needs.
How to Implement Quality Function Deployment (QFD)
The Quality Function Deployment methodology is a 4-phase process that encompasses
activities throughout the product development cycle.
Product Definition: The Product Definition Phase begins with collection of Voice of the
Customer and translating the customer wants and needs into product specifications. It may
also involve a competitive analysis to evaluate how effectively the competitor’s product
fulfils the customer wants and needs. The initial design concept is based on the particular
product performance requirements and specifications.
Product Development: During the Product Development Phase, the critical parts and
assemblies are identified. The critical product characteristics are cascaded down and
translated to critical or key part and assembly characteristics or specifications. The functional
requirements or specifications are then defined for each functional level.
Process Development: During the Process Development Phase, the manufacturing and
assembly processes are designed based on product and component specifications. The process
flow is developed and the critical process characteristics are identified.
Process Quality Control: Prior to production launch, the QFD process identifies critical part
and process characteristics. Process parameters are determined and appropriate process
controls are developed and implemented. In addition, any inspection and test specifications
are developed. Full production begins upon completion of process capability studies during
the pilot build.
Effective use of QFD requires team participation and discipline inherent in the practice of
QFD, which has proven to be an excellent team-building experience.
FAILURE MODE AND EFFECTIVE ANALYSIS
Failure Mode and Effects Analysis (FMEA) is a structured approach to discovering potential
failures that may exist within the design of a product or process.
Failure modes are the ways in which a process can fail. Effects are the ways that these
failures can lead to waste, defects or harmful outcomes for the customer. Failure Mode and
Effects Analysis is designed to identify, prioritize and limit these failure modes.
There are two broad categories of FMEA, Design FMEA (DFMEA) and Process FMEA
(PFMEA).
Design FMEA
Design FMEA (DFMEA) explores the possibility of product malfunctions, reduced product
life, and safety and regulatory concerns derived from:
• Material Properties
• Geometry
• Tolerances
• Interfaces with other components and/or systems
• Engineering Noise: environments, user profile, degradation, systems interactions
Process FMEA
Process FMEA (PFMEA) discovers failure that impacts product quality, reduced reliability of
the process, customer dissatisfaction, and safety or environmental hazards derived from:
• Human Factors
• Methods followed while processing
• Materials used
• Machines utilized
• Measurement systems impact on acceptance
• Environment Factors on process performance
Why Perform Failure Mode and Effects Analysis (FMEA)
FMEA is one of many tools used to discover failure at its earliest possible point in product or
process design. Discovering a failure early in Product Development (PD) using FMEA
provides the benefits of:
i. Multiple choices for Mitigating the Risk
ii. Higher capability of Verification and Validation of changes
iii. Collaboration between design of the product and process
iv. Improved Design for Manufacturing and Assembly (DFM/A)
v. Lower cost solutions
vi. Legacy, Tribal Knowledge, and Standard Work utilization
Ultimately, this methodology is effective at identifying and correcting process failures early
on so that you can avoid the nasty consequences of poor performance.
When to Perform Failure Mode and Effects Analysis (FMEA)
There are several times at which it makes sense to perform a Failure Mode and Effects
Analysis:
i. When you are designing a new product, process or service
ii. When you are planning on performing an existing process in a different way
iii. When you have a quality improvement goal for a specific process
iv. When you need to understand and improve the failures of a process
How to Perform Failure Mode and Effects Analysis (FMEA)
FMEA is performed in seven steps, with key activities at each step. The steps are separated to
assure that only the appropriate team members for each step are required to be present. The
FMEA approach used by Quality-One has been developed to avoid typical pitfalls which
make the analysis slow and ineffective.
There are Seven Steps to Developing an FMEA i.e.
FMEA Pre-Work and Assembly of the FMEA Team
Pre-work involves the collection and creation of key documents. FMEA works smoothly
through the development phases when an investigation of past failures and preparatory
documents is performed from its onset. Preparatory documents may include:
i. Failure Mode Avoidance (FMA) Past Failure
ii. Boundary/Block Diagram (For the DFMEA)
iii. Parameter Diagram (For the DFMEA)
iv. Process Flow Diagram (For the PFMEA)
v. Characteristics Matrix (For the PFMEA)
A pre-work Checklist is recommended for an efficient FMEA event. Checklist items may
include:
i. Requirements to be included
ii. Design and / or Process Assumptions
iii. Preliminary Bill of Material / Components
iv. Known causes from surrogate products
v. Potential causes from interfaces
vi. Potential causes from design choices
vii. Potential causes from noises and environments
viii. Family or Baseline FMEA (Historical FMEA)
ix. Past Test and Control Methods used on similar products
Path 1 Development- (Requirements through Severity Ranking)
Path 1 consists of inserting the functions, failure modes, effects of failure and Severity
rankings. The pre-work documents assist in this task by taking information previously
captured to populate the first few columns (depending on the worksheet selected) of the
FMEA.
Functions should be written in verb-noun context. Each function must have an associated
measurable. Functions may include:
• Wants, needs and desires translated
• Specifications of a design
• Government regulations
• Program-specific requirements
• Characteristics of product to be analyzed
• Desired process outputs
Failure Modes are written as anti-functions or anti-requirements in five potential ways:
• Full function failure
• Partial / degraded function failure
• Intermittent function failure
• Over function failure
• Unintended function failure
Path 2 Development – (Potential Causes and Prevention Controls through Occurrence
Ranking)
Causes are selected from the design / process inputs or past failures and placed in the Cause
column when applicable to a specific failure mode. The columns completed in Path 2 are:
• Potential Causes / Mechanisms of Failure
• Current Prevention Controls (i.e. standard work, previously successful designs, etc.)
• Occurrence Rankings for each cause
• Classification of Special Characteristics, if indicated
• Actions are developed to address high risk Severity and Occurrence combinations,
defined in the Quality-One Criticality Matrix
Path 3 Development- (Testing and Detection Controls through Detection Ranking)
Path 3 Development involves the addition of Detection Controls that verify that the design
meets requirements (for Design FMEA) or cause and/or failure mode, if undetected, may
reach a customer (for Process FMEA).
The columns completed in Path 3 are:
• Detection Controls
• Detection Ranking
Actions are determined to improve the controls if they are insufficient to the Risks
determined in Paths 1 and 2. Recommended Actions should address weakness in the testing
and/or control strategy.
Review and updates of the Design Verification Plan and Report (DVP&R) or Control Plans
are also possible outcomes of Path 3.
4. Action Priority & Assignment
The Actions that were previously determined in Paths 1, 2 or 3 are assigned a Risk Priority
Number (RPN) for action follow-up.
RPN is calculated by multiplying the Severity, Occurrence and Detection Rankings for each
potential failure / effect, cause and control combination. Actions should not be determined
based on an RPN threshold value. This is done commonly and is a practice that leads to poor
team behaviour. The columns completed are:
• Review Recommended Actions and assign RPN for additional follow-up
• Assign Actions to appropriate personnel
• Assign action due dates
5. Actions Taken / Design Review
FMEA Actions are closed when counter measures have been taken and are successful at
reducing risk. The purpose of an FMEA is to discover and mitigate risk. FMEAs which do
not find risk are considered to be weak and non-value added. Effort of the team did not
produce improvement and therefore time was wasted in the analysis.
6. Re-Ranking Risk Priority Number (RPN) and Closure
After successful confirmation of Risk Mitigation Actions, the Core Team or Team Leader
will re-rank the appropriate ranking value (Severity, Occurrence or Detection). The new
rankings will be multiplied to attain the new RPN. The original RPN is compared to the
revised RPN and the relative improvement to the design or process has been confirmed.
Columns completed in Step 7:
• Re-ranked Severity
• Re-ranked Occurrence
• Re-ranked Detection
• iRe-ranked RPN
• Generate new Actions, repeating Step 5, until risk has been mitigated
• Comparison of initial RPN and revised RPN
FMEA Relationship to Problem Solving
The Failure Modes in a FMEA are equivalent to the Problem Statement or Problem
Description in Problem Solving. Causes in a FMEA are equivalent to potential root causes in
Problem Solving. Effects of failure in a FMEA are Problem Symptoms in Problem Solving.
More examples of this relationship are:
i. The problem statements and descriptions are linked between both documents.
Problem solving methods are completed faster by utilizing easy to locate, pre-brainstormed
information from an FMEA.
ii. Possible causes in an FMEA are immediately used to jump start Fishbone or Ishikawa
diagrams. Brainstorming information that is already known is not a good use of time or
resources.
iii. Data collected from problem solving is placed into an FMEA for future planning of
new products or process quality. This allows an FMEA to consider actual failures,
categorized as failure modes and causes, making the FMEA more effective and complete.
iv. The design or process controls in an FMEA are used in verifying the root cause and
Permanent Corrective Action (PCA).
v. The FMEA and Problem Solving reconcile each failure and cause by cross
documenting failure modes, problem statements and possible causes.
4. Data management
Organisations should have adequate data management systems to avoid scenarios of
operational inefficiencies, poor customer experience, and other compliance risks. Data
management procedures should address documentation and records, collection methods,
sources, disposal, and storage.
5. Internal Processes
The QMS requires organisations to define all processes involved in transforming inputs to
finished products and services. There should be an effort to illustrate how different internal
processes interact with machines and human resources. This way, you can link every activity
within the company to a particular process.
7. Improvement Opportunities
Organisations need to design clear documentation of their intentions to meet QMS continuous
improvement standards. The documentation should contain safety designs, corrective action,
quality planning procedures, and compliance requirements.
8. Quality Instruments
Corporations should have quality tools to measure the progress and success of the QMS. If
you rely on these instruments to validate products, you must ensure they are well-calibrated
and controlled to meet industrial specifications.