Study guide
5.1 The Project Charter & Problem Statements
ASQ Certified Six Sigma Yellow Belt CSSYB
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About the ASQ CSSYB Exam How to Use This Study Guide
2 Chapter 1: Six Sigma & Lean Fundamentals
1.1 Six Sigma Foundations, Principles & History 1.2 Lean Foundations, Principles & The 8 Wastes 1.3 Six Sigma Roles & Responsibilities
3 Chapter 2: Team Basics & Dynamics
2.1 Team Types & Stages of Team Evolution 2.2 Team Decision-Making & Idea Generation Tools 2.3 Communication Methods & Meeting Management
4 Chapter 3: Quality Tools & Six Sigma Metrics
3.1 The 7 Basic Quality Tools 3.2 Six Sigma Process Performance Metrics & COPQ
5 Chapter 4: Define Phase — Project Identification & Scope
4.1 Voice of the Customer (VOC) & Critical-to-Quality (CTQ) 4.2 Project Selection & Stakeholder Analysis 4.3 Process Definition with SIPOC & Supply Chain Basics
6 Chapter 5: Define Phase — Project Management Basics
5.1 The Project Charter & Problem Statements 5.2 Project Planning: WBS, Gantt Charts & Communication Plans 5.3 Project Management Tools & Tollgate Reviews
7 Chapter 6: Measure Phase — Data Collection & Statistics
6.1 Basic Statistics: Central Tendency & Dispersion 6.2 Data Types & Classification 6.3 Data Collection Plans, Operational Definitions & Sampling 6.4 Data Collection Techniques: Check Sheets, Checklists, Surveys & Interviews
8 Chapter 7: Measure Phase — Measurement System Analysis
7.1 Measurement System Fundamentals: Precision, Accuracy & Bias 7.2 Gauge Repeatability & Reproducibility (GR&R)
9 Chapter 8: Analyze Phase — Process & Root Cause Analysis
8.1 Process Analysis: 5S & Value Analysis 8.2 Failure Mode and Effects Analysis (FMEA) 8.3 Root Cause Analysis: 5 Whys, Process Mapping, 8D, Force-Field & Matrix Charts
10 Chapter 9: Analyze Phase — Corrective Action & Variation
9.1 Corrective & Preventive Action Processes 9.2 Common Cause vs Special Cause Variation 9.3 Basic Distribution Types: Normal, Binomial & Poisson
11 Chapter 10: Analyze Phase — Relationships & Hypothesis Testing
10.1 Correlation & Scatter Plots 10.2 Simple Linear Regression & Prediction 10.3 Hypothesis Testing Concepts: Hypotheses, Errors & P-Values
12 Chapter 11: Improve Phase — Implementation Techniques
11.1 Kaizen & Kaizen Blitz Events 11.2 Plan-Do-Check-Act (PDCA) & Solution Selection 11.3 Cost-Benefit Analysis & Financial Validation
13 Chapter 12: Control Phase — Sustaining Improvements
12.1 Control Plans & Process Monitoring 12.2 Statistical Process Control: X-bar & R Charts 12.3 Document Control, Standard Operating Procedures & Project Hand-off
5.1 The Project Charter & Problem Statements
Key Takeaways Explain This Topic AI
The project charter functions as a formal contract and living agreement between the project team, sponsor, and champion, authorizing the expenditure of organizational resources.
A comprehensive charter contains six core elements: the Business Case, Problem Statement, Goal Statement, Project Scope, Milestones, and Team Roles and Resources.
An effective problem statement objectively quantifies what is defective, where and when it occurs, and the baseline performance gap, without assuming root causes or prescribing solutions.
Project goal statements must follow the SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound), defining the baseline metric, target metric, and completion deadline.
Establishing explicit in-scope and out-of-scope process boundaries protects project resources from scope creep and prevents milestone slippage.
Last updated: September 2026
The Project Charter & Problem Statements
Quick Answer: The project charter is a formal document and living contract that establishes executive sponsorship, authorizes resource allocation, and aligns project goals with organizational strategy. A comprehensive charter contains six core elements: Business Case, Problem Statement, Goal Statement, Project Scope, Milestones, and Team Roles. A critical formulation rule is that problem statements must describe the observable defect, baseline performance, and quantified gap without assuming root causes or prescribing solutions. Independent CSSYB study guide by ExamFinch.
Purpose and Strategic Role of the Project Charter
A Six Sigma initiative cannot succeed without formal executive backing, access to process data, and dedicated team time. The project charter fulfills this need by serving as the foundational governance agreement of the Define phase, establishing a binding contract between the project team, the Project Champion , and the Process Owner .
The charter accomplishes three vital objectives:
Resource Authorization: Grants the project leader (Black or Green Belt) and team members (including Yellow Belts) explicit authority to expend organizational resources—such as work hours, capital, equipment time, and statistical software.
Strategic Alignment: Links localized process defects directly to high-level organizational goals, such as operating cost reduction, regulatory compliance, customer retention, or margin growth.
Operational Consensus: Establishes shared boundaries, preventing misunderstandings regarding what the project will and will not deliver.
Although formally signed at the conclusion of the Define phase, the charter functions as a living document . As the team collects empirical data during Measure and Analyze, newly uncovered facts may warrant refining parameters—such as tightening scope or adjusting milestone targets—subject to formal review and re-approval by the Project Champion.
The Six Core Elements of a Robust Charter
A comprehensive Six Sigma charter integrates six interconnected components:
Business Case: Answers the executive question, "Why does this project matter now?" It details the strategic and financial justification for the initiative, highlighting the Cost of Poor Quality (COPQ) , regulatory mandates, or customer satisfaction trends. It establishes operational urgency by framing the business risks of inaction.
Problem Statement: Provides an objective, data-driven description of the operational pain point. It articulates four specific dimensions:
What: The specific defect, error, or metric variance observed.
Where: The physical facility, production line, customer segment, or software application.
When: The timeframe, shift pattern, or duration of observation.
Magnitude / Baseline Gap: Baseline performance compared against the expected standard, including financial consequences.
The Cardinal Rule: A problem statement must never state suspected root causes, assign personal blame, or prescribe solutions. Prematurely speculating on causes biases data collection and circumvents DMAIC rigor.
Goal Statement: Adheres to the SMART framework (Specific, Measurable, Achievable, Relevant, Time-bound). It specifies the baseline metric ( Y 0 Y_0 Y 0 ), the quantified target metric ( Y target Y_{\text{target}} Y target ), and the target completion deadline (e.g., "Reduce invoice processing errors from 8.4% to under 2.0% by December 15, 2026, generating $65,000 in annual COPQ savings" ).
Project Scope: Demarcates project boundaries by explicitly documenting both in-scope and out-of-scope activities, processes, and geographic sites. Defining clear limits prevents scope creep —the uncontrolled expansion of project boundaries without corresponding increases in time or budget.
Milestones / Project Plan: Outlines target completion deadlines for the five DMAIC phase tollgates (Define, Measure, Analyze, Improve, and Control), establishing clear accountability.
Team Roles & Resources: Identifies key participants and responsibilities, including the Champion, Process Owner, Black/Green Belt project leader, Yellow Belt frontline contributors, and financial analysts who audit cost savings.
BoK checkpoint: The CSSYB Body of Knowledge names four charter components you must be able to describe: problem statement, project scope, baseline data, and project goal . Baseline data is the measured current performance (for example, an 8.4% invoice error rate over the last six months). It supplies the magnitude in the problem statement and the starting point ( Y 0 Y_0 Y 0 ) of the goal statement, so a charter without baseline data cannot show how much improvement the goal requires.
Formulating Rigorous Problem Statements
Effective problem statements isolate observable symptoms from unverified assumptions. The table below illustrates common formulation errors and their data-driven corrections:
Flawed Problem Statement Fatal Flaw Effective Problem Statement Operational Rationale
"Customer call wait times are unacceptable because CRM software is defective; management must purchase additional server licenses." Assumes an unverified root cause (software failure) and dictates an expensive capital solution before data collection. "Between June 1 and August 31, 2026, Midwest call center average wait times increased from 4.5 to 12.8 minutes, producing a 16.2% abandonment rate and $85,000 in lost revenue." Quantifies the observation timeframe, site, baseline metric, actual gap, and financial impact without speculation.
"Line 3 scrap is excessive due to careless operator handling, requiring mandatory retraining." Assigns blame to frontline personnel and predetermines training as the solution prior to investigating equipment or materials. "During Q2 2026, Line 3 component scrap averaged 7.8%, exceeding the historical 1.5% baseline and creating $120,000 in unbudgeted scrap expense." Defines the specific line, timeline, baseline tolerance, and COPQ, leaving root cause analysis to the Analyze phase.
"Freight delivery delays are out of control because drivers are not following routing guidelines." Uses vague emotional terms ( "out of control" ) and presumes driver non-compliance without operational proof. "From January to May 2026, on-time regional freight deliveries from the Dallas hub dropped from 97.4% to 83.1%, impacting 2,400 orders and incurring $52,000 in SLA penalties." Specifies origin, exact percentage decline, shipment volume, and contractual penalty costs without bias.
Scope Management & Charter Governance
Uncontrolled project expansion, or scope creep , represents a primary failure mode for continuous improvement projects. If stakeholders attempt to append additional processes or software systems to an active initiative, the project leader must prepare a formal charter amendment. This amendment evaluates the proposed addition against project timelines, budget, and Yellow Belt resource availability, requiring formal sign-off from the Project Champion before any operational boundaries are altered.