Project Charter Template Green Belt

Standard Operating Procedure: Six Sigma Green Belt Project Charter Execution

Document ID: SOP-TR-SS-GB-402
Effective Date: October 24, 2023
Version: 3.1.0
Review Cadence: Annual
Author: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional protocol for authoring, reviewing, and approving a Six Sigma Green Belt Project Charter within the Template Registry framework. The objective of this procedure is to establish strict alignment between operational defects and organizational strategic goals, ensuring projects maintain a tight scope, quantifiable financial impact, and clear resource allocation before execution of the Define, Measure, Analyze, Improve, Control (DMAIC) lifecycle. Adherence to this SOP mitigates scope creep, prevents resource starvation, and guarantees audit readiness for gate reviews.

---

2. Scope & Prerequisites

2.1 Scope

This procedure applies to all operational, engineering, and administrative personnel undertaking Six Sigma Green Belt certification projects across all business units governed by the Template Registry quality management system.

2.2 Prerequisites & Tools

• Software: Enterprise Process Management Suite (EPMS) v12.4+, Microsoft Excel / Google Sheets for baseline statistical analysis, and Enterprise Portfolio Management (EPM) database access.
• Access Level: Green Belt Practitioner credentials or higher.
• Required Inputs:
  • Voice of the Customer (VoC) feedback logs.
  • Historical defect tracking data (minimum 30 data points or 30 days of continuous operation).
  • Strategic alignment matrix from the local Continuous Improvement Steering Committee.

---

3. Roles & Responsibilities (RACI Matrix)

Legend: R = Responsible, A = Accountable, C = Consulted, I = Informed

---

4. Step-by-Step Procedure

Phase 1: Problem and Business Case Formulation

• 1.1 Access the official Template Registry Green Belt Project Charter template (TR-GB-CHARTER-v3.dotx).
• 1.2 Extract raw performance metrics from enterprise reporting tools to quantify the gap between current state performance and customer requirements.
• 1.3 Draft the Problem Statement adhering strictly to the format: [What is wrong], [Where it is occurring], [When it started/frequency], and [What is the impact] without embedding premature root causes.
• 1.4 Compose the Business Case by tying the problem directly to organizational strategic objectives, outlining the cost of poor quality (CoPQ) if the project is deferred.

Phase 2: Goal Statement and Metric Definition

• 2.1 Define the primary Y (output metric) as a SMART (Specific, Measurable, Achievable, Relevant, Time-bound) objective.
• 2.2 Establish baseline capability metrics ($Z_{bench}$, Defect Per Million Opportunities [DPMO], or First Pass Yield [FPY]) using validated data from the data collection plan.
• 2.3 Set target performance levels derived from customer Specification Limits (USL/LSL) or historical best-in-class performance.

Phase 3: Project Scope and Boundary Setting

• 2.4 Construct a high-level SIPOC (Suppliers, Inputs, Process, Outputs, Customers) diagram to explicitly define process boundaries.
• 2.5 Document a minimum of three explicit "In-Scope" process steps and three "Out-of-Scope" process elements to prevent scope creep.
• 2.6 Identify core project constraints regarding budget, headcount, and regulatory compliance requirements.

Phase 4: Financial Validation and Resource Allocation

• 4.1 Calculate anticipated Hard Savings (direct cost reduction, headcount reallocation, scrap reduction) and Soft Savings (capacity release, risk mitigation) using the Template Registry Financial Calculator.
• 4.2 Submit financial projections to the designated Finance Representative for formal sign-off.
• 4.3 Map project milestones against the standard DMAIC timeline, ensuring gate review dates are locked in the corporate calendar.
• 4.4 Populate the Team and Stakeholder matrix, securing formal capacity commitments from functional line managers.

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices

• Zero Premature Root Cause Assumption: Ensure the Problem Statement describes the symptom, not the suspected solution (e.g., avoid writing "Need to install new software because current software is slow").
• Financial Conservatism: Always utilize conservative estimates for financial savings. Over-promising at Gate 0 leads to operational penalties during post-implementation audits.
• SIPOC Alignment: Ensure the process boundaries defined in the SIPOC match the operational boundaries set in the In-Scope/Out-of-Scope section identically.

5.2 Common Pitfalls

• Vague Metrics: Avoid qualitative goal statements like "improve customer satisfaction." Use quantifiable metrics such as "reduce cycle time from 14 days to $\le 3$ days."
• Scope Creep: Multi-process charters (e.g., attempting to fix both billing and shipping in one Green Belt project) will fail audit gate reviews. Keep the scope restricted to a single value stream.

5.3 Metric Thresholds

• Charter Approval Lead Time: Must be completed within 14 calendar days of project ideation.
• Financial Impact Minimum: Projects must demonstrate a minimum hard savings threshold of $25,000 USD or a 15% efficiency gain in a critical-to-quality (CTQ) metric to secure Sponsor approval.

---

6. Frequently Asked Questions (FAQ)

Q1: What happens if the baseline data required for Section 2 does not exist?
A: If historical data is absent or corrupted, the Green Belt must establish a 2-week interim data collection plan to capture a baseline before submitting the charter for Gate 0 approval. Do not estimate baseline values without empirical backing.

Q2: Can the Project Charter be modified after it receives Gate 0 approval from the Sponsor?
A: Minor scope adjustments require the submission of a Charter Amendment Request form approved by the Black Belt. Major shifts (e.g., changing the primary output metric $Y$ or altering projected savings by >20%) require a formal re-review and re-signing at a revised Gate 0 review.

Q3: Who holds the final authority if the Finance Representative and the Project Sponsor disagree on the projected financial savings?
A: The Finance Representative's validation is a hard prerequisite for submission; however, the Project Sponsor retains ultimate accountability for the business case. Escalation must be routed to the Continuous Improvement Steering Committee for final adjudication.