Six Sigma Principles and DMAIC

Introduction

Six Sigma is a disciplined, data-based approach for improving process performance and reducing defects, variation, waste, and customer dissatisfaction. It is both a management philosophy and a problem-solving methodology. In production management, Six Sigma connects customer requirements with process measurement, statistical analysis, improvement action, and sustained control.

The central idea is that quality problems are rarely caused by individual effort alone. They usually arise from process design, unclear requirements, unstable inputs, inadequate measurement systems, or uncontrolled variation. Six Sigma therefore focuses on improving the process rather than merely inspecting finished products.

The most widely used Six Sigma improvement cycle is DMAIC: Define, Measure, Analyze, Improve, and Control. DMAIC is used primarily for improving an existing process whose performance is below expectation. It differs from Design for Six Sigma, which is used to create or redesign products and processes.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Explain the principles, terminology, and organizational roles of Six Sigma.
2. Select and prioritize suitable improvement projects.
3. Prepare a project charter and SIPOC analysis.
4. Translate customer requirements into critical-to-quality characteristics.
5. Establish valid operational definitions, baselines, and measurement plans.
6. Analyze process data and validate root causes.
7. Select improvements using evidence, risk assessment, and process knowledge.
8. Establish control plans and track financial and operational benefits.
9. Evaluate the limitations, risks, and governance requirements of DMAIC.

1. Foundations and Principles of Six Sigma

1.1 Meaning of Six Sigma

The word sigma, represented by the Greek letter σ, denotes standard deviation, a measure of dispersion in a population or process. In statistical usage, a process with a smaller standard deviation has less variation relative to its specification limits.

In organizational practice, Six Sigma means the systematic reduction of process variation and defects through disciplined use of data. The objective is not simply to calculate a sigma value. It is to produce reliable outcomes that satisfy customers and support business goals.

A defect is a failure to meet a specified requirement. A defective unit is a unit containing one or more defects. These concepts must not be confused: one unit may contain several defects.

The commonly quoted Six Sigma benchmark is 3.4 defects per million opportunities (DPMO), based on a conventional 1.5-sigma long-term shift assumption. This figure is a benchmark rather than a universal law. The actual relationship between sigma level and defect rate depends on distributional assumptions, specification limits, centring, independence, and the treatment of short-term and long-term variation.

A basic defect-rate calculation is:

The number of opportunities must be defined consistently. If each unit has three possible defect opportunities, 20 defects are found in 2,000 units, then:

DPMO = (20 ÷ (2,000 × 3)) × 1,000,000 = 3,333.3 DPMO.

This calculation assumes that the numerator and denominator refer to the same period, product population, and defect definitions.

1.2 Core principles

Six Sigma projects generally follow these principles:

• Customer focus: Improvement begins with what customers value, not merely what is easy to measure.
• Process thinking: Results are produced by processes; therefore, process inputs and methods must be understood.
• Data-based decisions: Opinions and anecdotal evidence are replaced or tested by reliable evidence.
• Reduction of variation: Stable, predictable processes are preferable to processes that occasionally achieve excellent results.
• Prevention rather than detection: Error-proofing and process control are more effective than relying only on final inspection.
• Root-cause discipline: Symptoms are distinguished from verified causes.
• Financial and operational value: Projects should improve performance in ways that matter to the organization.
• Sustained control: An improvement is incomplete until the new performance becomes routine and benefits are tracked.

1.3 Common terminology

2. Six Sigma Roles and Governance

Six Sigma responsibilities should be explicit. Titles vary among organizations, but the underlying functions are similar.

• Executive champion: Selects strategic priorities, removes organizational barriers, allocates resources, and confirms that the project supports business objectives.
• Process owner: Owns the process and is accountable for maintaining the improved condition after project completion.
• Master Black Belt: Provides advanced technical expertise, coaches project leaders, and supports methodology governance.
• Black Belt: Leads complex cross-functional projects, performs analysis, facilitates decisions, and manages the improvement plan.
• Green Belt: Leads or supports smaller projects while maintaining regular operational responsibilities.
• Yellow Belt or team member: Contributes process knowledge, data, testing, and implementation support.
• Subject-matter expert: Provides specialist knowledge in equipment, materials, engineering, quality, maintenance, or information systems.
• Finance representative: Validates benefit calculations and distinguishes hard savings, cost avoidance, revenue effects, and non-financial benefits.
• Customer or regulatory representative: Clarifies requirements where customer safety, compliance, or contractual obligations are involved.

A project team should not be so large that decisions become difficult, nor so narrow that important process knowledge is excluded. Governance should define the approval authority, escalation routes, data ownership, change-control requirements, and benefit-verification method.

Tollgates are not ceremonial meetings. At each tollgate, the team should demonstrate that the phase outputs are sufficiently reliable to justify proceeding. For example, a team should not begin complex root-cause analysis while the problem definition and measurement system remain unclear.

3. Selecting a Six Sigma Project

A good project addresses a meaningful performance gap and has a manageable scope. Projects are commonly generated from customer complaints, scrap and rework data, delivery failures, warranty claims, audit findings, safety concerns, process instability, or strategic priorities.

A project is generally suitable for DMAIC when:

1. The process already exists.
2. The problem is important and measurable.
3. A performance gap is demonstrated by evidence.
4. The likely scope can be completed with available authority and resources.
5. The process owner is willing to sustain the result.

A project is poorly suited when the problem is only a vague concern, the customer requirement is unknown, data cannot be obtained, the scope covers an entire organization, or the solution has already been chosen without investigation. If a new product or fundamentally new process must be designed, Design for Six Sigma may be more appropriate.

Project selection can use a weighted priority matrix. For each candidate project, management may score strategic alignment, customer impact, financial impact, urgency, feasibility, risk reduction, and resource requirement. Scores should be accompanied by documented assumptions; a numerical ranking does not replace managerial judgement.

3.1 The project charter

The charter creates a shared agreement before detailed analysis begins. A robust charter includes:

• Business case: why the project matters.
• Problem statement: what is wrong, where, and when, without asserting an unverified cause.
• Goal statement: measurable desired performance and completion date.
• Scope: process boundaries, products, locations, and exclusions.
• CTQs or key metrics.
• Project team and roles.
• Process owner and sponsor.
• Milestones and tollgates.
• Assumptions, constraints, risks, and expected benefits.

Weak problem statement: “The operators do not follow the process.”

Stronger problem statement: “Between January and March, final inspection records show that 8.2% of Product X units required rework for dimension Y, compared with the internal target of 2.0%, resulting in extended lead time and additional labour.”

The second statement is measurable and does not prematurely blame operators or declare a cause.

4. Define Phase

The Define phase establishes the purpose and boundaries of the improvement effort. It prevents teams from collecting large amounts of irrelevant data.

4.1 Voice of the customer and CTQs

The voice of the customer may come from interviews, complaints, warranty data, surveys, contracts, service records, market research, or direct observation. Customers may express needs in imprecise language such as “fast,” “reliable,” or “easy to use.” The team must translate these needs into measurable CTQs.

For example:

A CTQ should specify the characteristic, measurement unit, acceptance criterion, and customer or regulatory source. CTQs should not be invented merely because they are convenient.

4.2 SIPOC analysis

SIPOC stands for Suppliers, Inputs, Process, Outputs, and Customers. It is a high-level map used to establish boundaries and shared understanding. It does not replace a detailed process map.

A SIPOC for a machining process might be:

The team should identify start and end points, major handoffs, important inputs, output requirements, and customer groups. The process owner and frontline employees should review the SIPOC because formal documentation alone may omit practical workarounds.

5. Measure Phase

The Measure phase establishes how the process currently performs and whether the data can support decisions. A baseline is not a single impressive or alarming observation; it is a defensible description of current performance over a representative period.

5.1 Operational definitions and measurement plans

An operational definition states exactly what is measured, how it is measured, who measures it, when it is measured, and how borderline cases are classified. For example, “late delivery” might mean a shipment recorded after the confirmed customer-required date in the enterprise system, excluding dates formally changed by an approved customer order revision.

A measurement plan should identify:

• Metric and unit.
• Data source and collection method.
• Sampling frequency and sample size.
• Product, machine, shift, and location fields.
• Responsible person.
• Defect classification.
• Data-storage and traceability rules.

5.2 Measurement system analysis

Before interpreting variation, the team should determine whether the measurement system is adequate. For continuous measurements, repeatability refers to variation when the same appraiser measures the same item repeatedly with the same instrument. Reproducibility refers to variation between appraisers. For attribute inspections, agreement studies examine consistency within and between inspectors.

A measurement system that produces excessive error can conceal process improvement or create false variation. Calibration, resolution, method standardization, training, environmental control, and gauge capability may all be relevant.

5.3 Baseline metrics

For a process with n observations x₁, x₂, …, xₙ, the sample mean is:

The sample standard deviation is:

Here, xᵢ is an observation, x̄ is the sample mean, s is the sample standard deviation, and n is the number of observations. The n − 1 denominator is used when estimating population variation from a sample under ordinary statistical assumptions. Both measures use the same unit as the observations.

For a two-sided specification with upper specification limit USL and lower specification limit LSL, a commonly used capability index is:

The centred capability index is:

These indices assume a stable process, meaningful specification limits, an adequate measurement system, and a standard deviation that appropriately represents within-process variation. Cp describes potential capability if the process is centred; Cpk also reflects off-centre performance. Capability indices must not be interpreted for an unstable process without first investigating the instability.

Worked example. A shaft diameter has LSL = 24.90 mm, USL = 25.10 mm, x̄ = 25.04 mm, and s = 0.025 mm. Then:

Cp = (25.10 − 24.90) ÷ (6 × 0.025) = 0.20 ÷ 0.15 = 1.33.

Cpk = min[(25.10 − 25.04) ÷ (3 × 0.025), (25.04 − 24.90) ÷ (3 × 0.025)]

= min(0.06 ÷ 0.075, 0.14 ÷ 0.075)

= min(0.80, 1.87) = 0.80.

The process has reasonable potential spread relative to the tolerance, but its mean is too close to the upper limit. Centring or variation reduction is required. This example does not prove that the process is stable; stability must be assessed separately.

5.4 Process stability

A control chart distinguishes routine common-cause variation from unusual special-cause signals. The appropriate chart depends on data type and sampling structure. Examples include X̄–R charts for subgrouped continuous measurements, I–MR charts for individual observations, p charts for fraction defective, and c or u charts for count data under suitable assumptions.

Control limits are calculated from process data and represent expected statistical variation; specification limits come from customer, engineering, or regulatory requirements. They are not interchangeable. A process can be stable but incapable, capable on average but unstable, or both stable and capable.

6. Analyze Phase

The Analyze phase identifies and validates causes of the performance gap. Brainstorming is useful for generating hypotheses, but a suspected cause is not a verified root cause.

6.1 Exploring causes

Useful tools include:

• Process maps and value-stream maps.
• Pareto analysis of defect categories.
• Cause-and-effect diagrams covering people, equipment, materials, methods, measurement, and environment.
• Stratification by machine, shift, supplier, product, operator, temperature, or time.
• Scatter plots and regression analysis where relationships are plausible.
• Failure Modes and Effects Analysis.
• Comparative studies between good and poor outcomes.

A Pareto chart can focus effort on the few categories contributing most to the observed problem, but it does not by itself establish causation. Similarly, correlation may indicate association without proving that a factor causes the outcome.

6.2 Root-cause validation

A cause should be considered validated when evidence demonstrates that:

1. The suspected input changes or differs when the output changes.
2. The relationship is practically meaningful, not merely statistically detectable.
3. The measurement system is adequate.
4. The relationship is consistent with process knowledge and time sequence.
5. A controlled trial, natural experiment, or other credible evidence shows that changing the cause changes the outcome.

For categorical comparisons, the team may compare defect proportions across conditions. For continuous outcomes, it may use graphical analysis, analysis of variance, regression, or designed experiments. Statistical tests require attention to independence, sample size, distributional assumptions, multiple comparisons, and practical significance.

A p-value is not the probability that a cause is true. It measures compatibility of the observed data with a specified null model under its assumptions. Decisions should also consider effect size, confidence intervals, cost, risk, and operational significance.

The “five whys” technique can help move from a visible symptom to an underlying process condition. It should not be used mechanically or to assign blame. A credible chain should be supported by evidence and should lead to a controllable process condition.

7. Improve Phase

The Improve phase develops, tests, and implements changes that address validated causes. Possible interventions include revised settings, standard work, poka-yoke error-proofing, fixture redesign, material controls, preventive maintenance, software validation, workplace organization, supplier development, or changes to scheduling and information flow.

7.1 Generating and selecting solutions

Potential solutions should be evaluated against:

• Expected effect on the CTQ.
• Technical feasibility.
• Cost and return.
• Safety and regulatory compliance.
• Environmental and ergonomic effects.
• Implementation time.
• New failure modes.
• Training and maintenance requirements.
• Reversibility and scalability.

FMEA should be updated when the process changes. The team should consider whether the proposed solution merely transfers the problem downstream or creates new risks.

7.2 Pilot testing and design of experiments

A pilot should define the test condition, response measure, comparison condition, duration, acceptance criteria, and rollback plan. Where several factors may interact, a designed experiment can provide stronger evidence than changing one factor at a time. The design must match the available resources and the nature of the process.

A pilot is not automatically successful because the first few units pass inspection. The team should compare performance with the baseline over a sufficiently representative period and examine variation, not only the average.

Illustrative improvement test. A packaging process has a baseline damage rate of 6.0% across 1,000 shipments. After a cushioning change, damage occurs in 25 of 1,000 shipments, or 2.5%. The absolute reduction is 3.5 percentage points, and the relative reduction is:

Relative reduction = (0.060 − 0.025) ÷ 0.060 = 0.5833, or approximately 58.3%.

The result is encouraging, but the team should examine product mix, shipment conditions, measurement consistency, statistical uncertainty, cost of the new material, and possible effects on recycling or handling before claiming a permanent benefit.

8. Control Phase

Control prevents the process from returning to its previous condition. It transfers ownership from the project team to the process owner while preserving evidence of performance.

A control plan normally specifies:

• CTQ and process characteristic.
• Target and specification limits.
• Measurement method and frequency.
• Responsible role.
• Control-chart or dashboard method.
• Reaction plan for an out-of-control signal or defect.
• Escalation route.
• Documentation and record-retention requirements.
• Training and competency requirements.
• Audit frequency.

A reaction plan should state what happens, who acts, how affected product is contained, how the cause is investigated, and when the process may resume. “Monitor closely” is not a sufficient reaction plan.

Control charts can be useful after improvement, but they must be correctly selected and interpreted. A point outside a control limit is a signal for investigation, not automatic proof that every unit is defective. Conversely, all points inside control limits do not guarantee compliance with customer specifications.

8.1 Benefit tracking

Benefits should be defined before implementation. Financial validation should distinguish:

• Hard savings: Reduction in actual expenditure, such as purchased material or external rework.
• Cost avoidance: Avoided future expenditure that may not immediately reduce the budget.
• Capacity release: Time or equipment capacity made available for additional production.
• Revenue impact: Additional sales or retention attributable to improved performance.
• Non-financial benefits: Safety, compliance, morale, lead time, reliability, or customer confidence.

A simple annualized gross benefit estimate may be expressed as:

Net benefit is:

These equations assume that the avoided cost is defined consistently and that the improvement volume is realistic. Finance should validate the calculation, particularly where benefits depend on demand, accounting treatment, or released capacity.

Closure should occur only after the process owner accepts the control plan, training is complete, documentation is updated, performance is sustained for an agreed period, and benefits are verified. Lessons learned should be transferred to similar processes where appropriate.

9. Applied Case: Reducing Rework in a Fabrication Cell

The following is an illustrative case based on a fictional fabrication company.

Background and problem

Alpha Fabrication produces welded frames for industrial equipment. Internal data show that 9.4% of frames require rework because of dimensional misalignment. Rework causes an average delay of 1.5 days and consumes approximately 420 labour hours per quarter. The customer requirement is that the diagonal difference between two frame corners must not exceed 2.0 mm.

The plant manager sponsors a DMAIC project. The process owner is the fabrication supervisor, and a Green Belt leads the project with participation from operators, quality, maintenance, engineering, planning, and finance.

Define

The charter defines the problem as excessive rework for dimensional misalignment during the previous six months. The goal is to reduce the rework rate from 9.4% to below 3.0% within four months without increasing weld defects or compromising safety. The scope begins with frame fixture setup and ends with final dimensional inspection. Upstream steel purchasing and downstream painting are excluded unless evidence shows that they affect the CTQ.

The SIPOC identifies steel and fixture components as inputs, welding and cooling as major process steps, dimensional inspection as the output verification activity, and assembly as the principal internal customer.

Measure

The team defines a defective frame as one whose measured diagonal difference exceeds 2.0 mm at final inspection. The measurement study finds that inspectors agree on classification in 98% of repeated evaluations, and the gauge is calibrated and sufficiently resolved for the tolerance.

A 12-week baseline is stratified by fixture, shift, product family, and operator. The overall rework rate is 9.4%, but the rate is 15.8% on Fixture 3 and 4.1% on the other fixtures. The process map also reveals that Fixture 3 has a worn locating pin. The team does not yet conclude that the pin is the sole cause.

Analyze

Further comparison shows that misalignment is concentrated in frames produced on Fixture 3, especially after long production runs. Inspection of the fixture confirms greater pin movement under load. A controlled trial using a temporary replacement pin reduces the misalignment rate substantially during a matched production run. The team also identifies inconsistent clamping sequence as a contributing factor.

The evidence supports two validated causes: excessive locating-pin movement and variation in clamping sequence. The analysis rejects the initial hypothesis that operator skill alone explains the problem. Operators working on the other fixtures do not show the same rate, and standardized observation shows that the equipment condition strongly influences the result.

Improve

Engineering replaces the locating pin with a hardened component, adds a visual wear indicator, and introduces a defined clamping sequence. A simple interlock prevents welding from starting until the primary clamps are engaged. The team pilots the changes for four weeks across all shifts and product families.

The rework rate falls to 2.6%. No increase occurs in weld defects, cycle time remains within the production plan, and operators report fewer adjustment interruptions. Finance estimates a quarterly benefit from avoided rework labour and reduced delay, while engineering records the cost of the fixture modification.

Control

The process owner receives a control plan requiring:

• Fixture-pin inspection at the beginning of each shift.
• Wear-indicator verification every 500 frames.
• Audit of clamping sequence twice per shift for the first month and weekly thereafter.
• A p chart for rework proportion by weekly production volume.
• Immediate containment and supervisor escalation if the weekly rate exceeds the agreed trigger.
• Updated standard work, training records, maintenance instructions, and spare-part controls.

After eight weeks, the rework rate remains below 3.0%. The benefit is accepted after Finance reconciles production volume, avoided labour, and implementation costs. The project is closed, and the control plan becomes part of the normal production-management system.

Learning points

The case illustrates that DMAIC is not a sequence of disconnected tools. The charter limited the problem, measurement established trustworthy evidence, analysis separated equipment and method causes from blame-based assumptions, improvement tested changes, and control transferred responsibility into daily management. It also shows why a process owner and finance validation are essential.

10. Limitations, Ethics, and Contemporary Practice

Six Sigma is powerful but not universally sufficient. Some problems are caused by strategy, product design, market uncertainty, organizational culture, or interactions too complex for a narrowly scoped project. Excessive emphasis on numerical targets may encourage under-reporting, metric manipulation, or neglect of unmeasured quality attributes. A project may optimize one department while damaging the whole value stream.

Ethical practice requires accurate reporting, protection of employees and customers, appropriate handling of personal data, honest disclosure of uncertainty, and avoidance of unsafe experimentation. Employees should not be punished for reporting defects or special causes. Regulatory, safety, environmental, and contractual requirements take precedence over a project’s cost or schedule objective.

Digital manufacturing systems, sensors, statistical software, and machine-learning tools can accelerate data collection and pattern recognition. However, AI-generated recommendations do not establish causality automatically. Data may be biased, incomplete, or affected by changes in measurement and process conditions. Human review, traceability, cybersecurity, access control, model validation, and change governance remain necessary.

Contemporary improvement systems increasingly combine Six Sigma with Lean, total productive maintenance, process mining, digital twins, and real-time quality monitoring. The combination is useful when roles are clear: Lean commonly emphasizes flow and waste reduction, while Six Sigma provides structured variation reduction and analytical validation. Neither approach should be applied as a collection of fashionable tools without a defined business and customer problem.

Best-Practice Checklist

Before launching a project, confirm that the problem is measurable, important, scoped, and owned. During Define, obtain agreement on the customer requirement and charter. During Measure, verify operational definitions and the measurement system before trusting the baseline. During Analyze, distinguish hypotheses from validated causes. During Improve, pilot changes and assess side effects. During Control, assign ownership, define reaction plans, verify benefits, and update standard work. Finally, communicate results honestly, including limitations and unresolved risks.

Chapter Summary

Six Sigma is a customer-focused, data-based approach for reducing defects and variation in existing processes. Its effectiveness depends on disciplined project selection, clear terminology, capable roles, reliable measurement, and sustained management attention.

DMAIC provides a structured path. Define establishes the business problem, customer requirements, scope, and project charter. Measure creates operational definitions, validates the measurement system, and establishes a representative baseline. Analyze uses process knowledge and data to distinguish symptoms from verified root causes. Improve develops and pilots solutions that address validated causes while considering risk, cost, and unintended effects. Control embeds the new method in standard work, monitoring, reaction plans, ownership, and benefit tracking.

Important quantitative ideas include DPMO, process averages, standard deviation, capability indices, defect proportions, and financial benefit calculations. These measures require appropriate assumptions and must not be confused with specification limits or control limits. Six Sigma roles—from executive champion to process owner, Black Belt, Green Belt, subject-matter expert, and Finance—support governance and sustainability.

The professional value of DMAIC lies not in using every available tool, but in making sound decisions from trustworthy evidence and converting improvement into stable organizational performance.

Key Terms

Six Sigma: A disciplined approach to reducing variation and defects through data and process improvement.

DMAIC: Define, Measure, Analyze, Improve, and Control improvement methodology.

VOC: Voice of the customer.

CTQ: Critical-to-quality characteristic.

Defect: Failure to meet a specified requirement.

DPMO: Defects per million opportunities.

Variation: Differences in process results.

Common cause: Routine variation inherent in a process system.

Special cause: Unusual, identifiable variation.

Project charter: Agreement defining a project’s purpose, scope, goal, and governance.

SIPOC: High-level view of Suppliers, Inputs, Process, Outputs, and Customers.

Baseline: Measured current performance before improvement.

Operational definition: Precise rule for measuring and classifying a result.

Measurement system analysis: Evaluation of measurement reliability and consistency.

Cp: Potential capability index based on specification width and process spread.

Cpk: Capability index accounting for process centring.

Root cause: Underlying condition whose removal prevents recurrence.

Control plan: Document specifying how improved performance will be maintained.

Process owner: Person accountable for ongoing process performance.

Tollgate: Formal review of DMAIC phase outputs.

Review Questions

Short Answer Questions

1. What is the difference between a defect and a defective unit?
2. Why must specification limits be distinguished from control limits?
3. What information should a project charter contain?
4. What is the purpose of a SIPOC analysis?
5. Why should a measurement system be evaluated before baseline analysis?

Long Answer Questions

1. Explain the five phases of DMAIC and describe the principal deliverables of each phase.
2. Discuss the responsibilities of the executive champion, process owner, Black Belt, Green Belt, and Finance representative.
3. Explain how VOC is translated into CTQs, using a production example.
4. Compare common-cause and special-cause variation and explain the management response to each.
5. Discuss how a control plan and benefit-verification process support the sustainability of a Six Sigma project.

Analytical / Application Questions

1. A process produces 30 defects in 5,000 units, with four defect opportunities per unit. Calculate DPMO and explain what additional information would be needed before comparing it with another process.
2. A process has USL = 52, LSL = 48, x̄ = 50.8, and s = 0.5. Calculate Cp and Cpk, interpret the difference, and state why process stability must be checked before using the indices for major decisions.
3. A production team claims that a new machine setting reduced defects because the first 50 units passed inspection. Design a DMAIC-based investigation that tests the claim, addresses measurement reliability, considers confounding factors, and establishes an appropriate control plan.

Multiple Choice Questions with Answers

Question 1

Which DMAIC phase establishes the project charter, scope, business case, and customer requirements?

A. Define

B. Measure

C. Analyze

D. Control

Correct Answer: A. Define

Question 2

A process produces 20 defects in 2,000 units, with three opportunities per unit. What is the DPMO?

A. 333.3

B. 3,333.3

C. 6,666.7

D. 30,000

Correct Answer: B. 3,333.3

Question 3

Which role is primarily accountable for maintaining the improved process after project closure?

A. External auditor

B. Process owner

C. Customer surveyor

D. Equipment supplier

Correct Answer: B. Process owner

Question 4

What is the principal purpose of a SIPOC?

A. To calculate process capability

B. To establish a high-level view of process boundaries and relationships

C. To replace all detailed work instructions

D. To determine annual financial benefits

Correct Answer: B. To establish a high-level view of process boundaries and relationships

Question 5

Which statement correctly distinguishes Cp from Cpk?

A. Cp measures customer satisfaction while Cpk measures cost

B. Cp reflects potential spread capability, while Cpk also reflects process centring

C. Cp applies only to attribute data while Cpk applies only to nominal data

D. Cp is a control limit and Cpk is a specification limit

Correct Answer: B. Cp reflects potential spread capability, while Cpk also reflects process centring

Question 6

Which evidence most strongly supports a validated root cause?

A. A manager’s opinion

B. A brainstorming suggestion

C. A controlled change in the suspected input followed by a corresponding output change

D. A single unusual observation

Correct Answer: C. A controlled change in the suspected input followed by a corresponding output change

Question 7

What is the main purpose of an operational definition?

A. To make a measure precise and consistently classified

B. To increase the number of project team members

C. To eliminate the need for sampling

D. To guarantee that the process is capable

Correct Answer: A. To make a measure precise and consistently classified

Question 8

Which statement about control limits and specification limits is correct?

A. They are two names for the same limits

B. Control limits describe expected process variation, while specification limits reflect requirements

C. Specification limits are calculated only from recent process data

D. Control limits are set by customers in every case

Correct Answer: B. Control limits describe expected process variation, while specification limits reflect requirements

Question 9

A baseline defect rate is 6.0% and the improved rate is 2.5%. What is the approximate relative reduction?

A. 3.5%

B. 42.0%

C. 58.3%

D. 140.0%

Correct Answer: C. 58.3%

Question 10

Which action belongs most directly in the Control phase?

A. Defining the initial problem statement

B. Creating a cause-and-effect diagram before collecting data

C. Testing whether the measurement system is adequate

D. Assigning reaction plans, monitoring responsibilities, and process ownership

Correct Answer: D. Assigning reaction plans, monitoring responsibilities, and process ownership