Project Charter Example Six Sigma

Standard Operating Procedure: Six Sigma Project Charter Development

Template Registry | Engineering Division

---

1. Document Control Block

---

2. Executive Summary & Purpose

This SOP defines the standardized protocol for developing a Six Sigma Project Charter. The Charter serves as the definitive contractual agreement between project sponsors and the improvement team. Its purpose is to align strategic objectives, delineate scope boundaries, and establish quantitative baseline metrics to ensure resource allocation is tethered to verifiable ROI.

---

3. Scope & Prerequisites

• Scope: Applicable to all Green Belt and Black Belt initiatives within Template Registry.
• Required Tools: Minitab or JMP (Statistical Analysis), MS Project (Timeline tracking), Enterprise Project Management (EPM) Suite.
• Prerequisites: Completed "Problem Statement" draft, access to raw process data, and verified Project Sponsor approval.
• PPE: N/A (Standard administrative environment).

---

4. Roles & Responsibilities (RACI Matrix)

(R=Responsible, A=Accountable, C=Consulted, I=Informed)

---

5. Step-by-Step Procedure

Phase I: Data Acquisition & Problem Formulation

• Define the Business Case: Articulate the "Why" using quantitative business impact (e.g., cost of poor quality).
• Draft the Problem Statement: Ensure it is time-bound, measurable, and avoids implying a solution.
• Identify the Goal Statement: Use SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound).

Phase II: Scope Definition & Constraint Mapping

• Establish SIPOC boundaries (Supplier, Input, Process, Output, Customer).
• Document In-Scope vs. Out-of-Scope parameters to prevent scope creep.
• Identify project constraints (Budget, HR, Regulatory, Timeline).

Phase III: Validation & Baseline

• Confirm baseline metric values with Process Owners.
• Calculate the Financial Impact (Hard vs. Soft savings).
• Secure physical or digital signatures from the Sponsor.

---

6. Quality Assurance & Pro-Tips

• Metric Thresholds: Ensure baseline data spans a minimum of 30 data points for statistical significance.
• Pro-Tip (The "Scope Trap"): If the project takes longer than 90 days to achieve "Control" phase, the scope is likely too broad. Break it into sub-projects.
• Common Pitfall: Conflating the Problem Statement with the Solution. Always focus on the performance gap, not the missing tool.
• Validation Rule: If the Project Charter does not directly map to a corporate Key Performance Indicator (KPI), it is not a project; it is a task.

---

7. Frequently Asked Questions

Q: At what point is a Project Charter officially "active"? A: The Charter is active only after the Sponsor and the Process Owner have formally signed off. Informal verbal approval is insufficient for resource requisition.

Q: Can the scope be altered after the Charter is signed? A: Yes, via a formal "Scope Change Request" (SCR) document. Changes must be documented, analyzed for impact on ROI, and re-approved by the Sponsor.

Q: Why is "Hard Savings" differentiation required? A: Finance departments require a distinction between cash-flow improvements (Hard) and productivity gains (Soft) to validate budget reallocation for future phases.

---

Authorized by: Julian Vance, Chief Architect, Template Registry.