Study guide
Project Scope Tools
ASQ Certified Six Sigma Green Belt CSSGB
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
CSSGB Exam Facts & Logistics How to Study for an Open-Book ASQ Exam
2 Six Sigma Foundations
Value of Six Sigma & Quality Leaders Organizational Goals & Six Sigma Projects Organizational Drivers, KPIs & Scorecards
3 Lean Principles in the Organization
Lean Concepts Value Stream Mapping & Waste
4 Design for Six Sigma
DFSS Road Maps: DMADV & IDOV FMEA Basics & Risk Priority Number Design FMEA vs Process FMEA
5 Define: Project Identification
Project Selection & DMAIC Fit Process Elements & Boundaries Benchmarking Types SIPOC & Process Inputs/Outputs
6 Stakeholders & Voice of the Customer
Owners & Stakeholders Customer Identification Customer Data Collection CTQ, QFD & Kano
7 Project Management Core
Agile & Top-Down Project Methods Project Charter & Problem Statements Project Scope Tools Primary & Consequential Metrics
8 Planning, Risk & Closure
WBS, Gantt, CPM, PERT & Tollgates Project Documentation Project Risk Analysis & Management Project Closure & Lessons Learned
9 Management Tools & Business Results
Eight Management & Planning Tools DPU, RTY, CoPQ, DPMO & Sigma Level Organizational Communication
10 Team Dynamics & Performance
Team Stages & Negative Dynamics Six Sigma Roles & RACI Brainstorming, NGT & Multivoting Team Communication
11 Measure: Process & Probability
Process Maps & Documentation Basic Probability Concepts Central Limit Theorem
12 Distributions & Data Collection
Statistical Distributions Data Types & Measurement Scales Sampling & Data Collection Plans Descriptive Statistics
13 Graphical Methods & MSA
Graphical Methods Measurement System Analysis & Gage R&R Bias, Linearity, Stability & P/T
14 Process & Performance Capability
Process Performance vs Specifications Process Capability Studies Cp, Cpk, Pp, Ppk & Cpm Short-Term vs Long-Term Capability & Sigma Shift
15 Analyze: Exploratory Data Analysis
Multi-Vari Studies Correlation & Linear Regression
16 Hypothesis Testing
Hypothesis Testing Basics Tests for Means, Variances & Proportions
17 Gap & Root Cause Analysis
Gap Analysis Root Cause Analysis Tools
18 Design of Experiments
DoE Basic Terms Main Effects & Interaction Plots
19 Implementation Planning & Lean Tools
Implementation Planning & Pilots Waste Elimination Tools Cycle-Time Reduction & SMED Kaizen & Kaizen Blitz
20 Statistical Process Control
SPC Basics: Common vs Special Cause Rational Subgrouping Control Chart Selection & Construction
21 Sustaining Improvements & Lean Control
Control Plans Document Control, Training & Audits Plan-Do-Check-Act (PDCA) TPM & Visual Factory
Project Scope Tools
Key Takeaways Explain This Topic AI
Project scope tools—especially process maps and Pareto charts—convert opinions into visible, data-backed in/out boundaries for the charter.
High-level process maps set start/stop events, handoffs, and focus zones before detailed Analyze mapping.
Pareto analysis concentrates the project on the vital few defect types, products, or reasons that drive most of the primary-metric pain.
SIPOC, CTQ trees, stratification, affinity methods, and macro VSMs also support scoping when they change the boundary or data plan.
Explicit outs, Champion approval, and willingness to re-scope after Measure prevent boil-the-ocean projects and tool theater.
Last updated: July 2026
Project Scope Tools
Quick Answer: Use process maps , Pareto charts , and related quality tools in Define to set a finishable project boundary: map the work, quantify where pain concentrates, and deliberately place items in or out of scope. Scope tools prevent “boil the ocean” charters and focus the team on the vital few process steps or defect types.
Scope Is a Decision, Not a Feeling (BoK II.C.3)
ASQ’s CSSGB BoK asks Green Belts to apply project scope tools —not merely recite definitions. After a draft problem statement exists, you still must answer: Which process segment, defect codes, products, sites, and customers are inside this project? Scope tools turn opinions into visible, data-backed boundaries that Champions can approve.
Poor scope shows up as:
- Projects that never finish because every exception is “in”
- Analysis that drowns in hundreds of Xs with no focus
- Improvements that move a local metric while the customer’s pain sits elsewhere
- Political fights mid-Measure when stakeholders discover they were excluded—or included without capacity
- Process Maps for Scoping
Process maps show the sequence of steps, decisions, and handoffs from start to stop. In Define, prefer a high-level map (often SIPOC-linked, 5–10 steps) before detailed swimlanes. Mapping for scope is different from mapping for Analyze root causes:
- Mapping purpose Level of detail Scope decision it supports
- Charter / SIPOC alignment Macro steps Start/stop events; major handoffs
- In/out listing Swimlane or deployment chart Which functions own which steps
- Later Measure/Analyze Detailed flowchart, VSM Where to measure, where waste sits
- How maps set scope
Mark start and stop with observable events (order entered; order shipped).
Highlight cross-functional handoffs — queues often hide here; decide if handoffs are in scope.
Color or annotate candidate focus zones — e.g., only “pick–pack–ship,” not order entry.
List explicit outs — engineering change process, supplier qualification, pricing policy.
Confirm with process owner that the map matches reality (Gemba check).
A map that includes every enterprise system and every product family is a scope risk , not a badge of thoroughness. Cut until a Green Belt team can finish in months, not years.
Worked example — hospital discharge
A team maps admission → treatment → discharge medication reconciliation → transport → bed turnover. Pareto and cycle-time data show most delay after “medically ready.” Scope decision: start = medically ready for discharge; stop = patient left unit; out of scope = inpatient clinical protocols and ED boarding. The map made the cut legible to physicians and bed management.
Pareto Charts for Scoping
A Pareto chart ranks categories by frequency or impact (often 80/20: vital few vs. useful many). For scoping, Pareto answers: Which defect types, product lines, shifts, or failure modes create most of the pain?
- Typical Pareto uses in Define
- Defect codes by count or cost
- Complaint themes by volume
- SKUs contributing to scrap dollars
- Reasons for late orders
- Sites or channels driving CoPQ
Scope implication: Charter the vital few categories first. Example: five defect codes cause 82% of rework hours—scope the project to those codes on Line 2, and park the long tail for a later project or just-do-it fixes.
- Cautions
- Pareto on counts can hide expensive rare defects; consider dual Paretos (count and cost)
- Bad category definitions create fake “vital few”
- Do not Pareto randomly without linking categories to the primary Y
- Pareto focuses what/where , not why (root cause waits for Analyze)
- Other Quality Tools That Shape Scope
Green Belts should recognize a toolkit beyond maps and Pareto:
- Tool Scope contribution
- SIPOC High-level suppliers/inputs/outputs/customers; boundary framing
- CTQ tree / requirements cascade Keeps scope tied to customer-critical Ys, not pet metrics
Cause-and-effect (fishbone) early, lightly Lists candidate factor families to bound data collection—not to lock root cause in Define
- Affinity diagrams Groups VOC or brainstormed issues so scope themes emerge
- Interrelationship digraphs Shows which problem themes drive others when priorities conflict
- Check sheets / stratification Early counts by shift, product, machine to decide focus strata
- Run charts / trend charts Shows whether the problem is chronic (good project) or a one-spike (maybe not)
- Value stream map (macro) Lead-time and inventory focus for cycle-time scopes
- Stakeholder map Who must be in the communication/scope boundary to implement later
Use tools to decide boundaries , not to decorate the Define deck. Each tool should change an in/out list, a metric definition, or a data-collection plan.
A Practical Scope-Setting Sequence
Draft problem and primary Y with baseline.
Build SIPOC + high-level process map; mark start/stop.
Stratify available data; run Pareto on defect/reason/product.
Propose in-scope steps, products, sites, and time window.
List outs explicitly (and why).
Check feasibility: data access, authority, timeline, consequential risks.
Update charter scope section; get Champion approval.
Revisit after Measure if new data show the pain lives elsewhere—formally.
In-Scope vs. Out-of-Scope Examples
Project Y: Reduce packaging defects causing customer returns.
- In scope Out of scope
- Pack-out cells 1–3, SKU family K Product design change of the primary carton geometry
- Defect codes crush, open seal, wrong insert Marketing copy errors on website
- Day and night shifts at Plant West Plant East (different equipment)
- Process and training changes, poka-yoke within $15k Full warehouse WMS replacement
Clarity here prevents Improve from becoming an unbounded IT program.
- Common Scope Failures
- Map without cutting — Beautiful flowchart, infinite project
- Pareto ignored — Team works the pet defect that is 3% of impact
- Scope = organization chart — “All of Operations” instead of a process
- Hidden outs — Stakeholders assume their area is included
- Tool theater — Affinity walls and fishbones that never change the charter
- Refusing to re-scope after Measure proves the original boundary was wrong
- Green Belt Checklist
Can you point to start/stop on a process map?
Does a Pareto (or stratified data) justify the focus categories?
Are outs written, not only implied?
Does scope still allow the goal on the primary Y to be achievable?
Did the Champion approve the boundary?
When scope tools drive a finishable, data-justified boundary—not a vague aspiration—you meet BoK II.C.3 at the Apply level.