Project Charter Template for Six Sigma

Standard Operating Procedure: Six Sigma Project Charter Development

Document ID: SOP-TR-SS-001
Effective Date: 2023-10-27
Version: 1.0.0
Review Cadence: Biennial

1. Executive Summary & Purpose

This SOP establishes the mandatory framework for drafting a Six Sigma Project Charter. The purpose is to provide a standardized mechanism for aligning project objectives with organizational strategy, defining scope boundaries, and securing executive sponsorship. Adherence ensures project viability, resource allocation efficiency, and measurable ROI.

2. Scope & Prerequisites

• Scope: Applicable to all Green, Black, and Master Black Belt initiatives within the Template Registry ecosystem.
• Prerequisites:
  • Defined Business Case.
  • Preliminary Value Stream Map (VSM) or SIPOC.
  • Access to the Enterprise Project Management Office (EPMO) Repository.
  • Software: Six Sigma Template Registry Suite (SS-TRS) or authorized MS Excel/Word equivalent.

3. Roles & Responsibilities (RACI Matrix)

4. Step-by-Step Procedure

Phase 1: Problem Definition

• Define the Problem Statement using the "What, Where, When, and How Much" format.
• Quantify the gap between current performance and target metrics.
• Ensure the problem is not a "hidden solution" (e.g., "We need to install Software X").

Phase 2: Goal Setting & Metric Alignment

• Establish SMART (Specific, Measurable, Achievable, Relevant, Time-bound) goals.
• Define the Primary Metric (Y) and specify the measurement system validation (MSV).
• Document the financial impact (Hard vs. Soft savings).

Phase 3: Scoping & Stakeholder Mapping

• Define In-Scope vs. Out-of-Scope boundaries to prevent scope creep.
• Map key stakeholders and their interest levels.
• List high-level milestones using a Gantt-style schedule (DMAIC timeline).

Phase 4: Finalization & Approval

• Review the document for consistency with the organizational "North Star" metrics.
• Obtain formal sign-off from the Process Owner and Financial Controller.
• Upload to the EPMO central repository with version control metadata.

5. Quality Assurance & Pro-Tips

• Metric Thresholds: All projects must demonstrate a minimum expected ROI of 3x the resource cost within 12 months.
• Common Pitfalls:
  • Scope Creep: Avoid "Boiling the Ocean." If the scope is too broad, break into sub-projects.
  • Undefined 'Y': If you cannot measure the problem at the start, you cannot validate the solution at the end.
• Pro-Tip: Utilize the SIPOC tool during the chartering phase to identify hidden process constraints early.
• QA Checklist: If the charter cannot be summarized in a 30-second "Elevator Pitch," the objective is insufficiently refined.

6. Frequently Asked Questions

Q: At what stage should we modify the charter?
A: The charter is a "living" document, but substantial scope changes require a formal "Charter Revision Request" signed by the Project Sponsor. Minor grammatical or timeline adjustments do not require re-approval.

Q: What if the financial impact is qualitative (e.g., Customer Satisfaction)?
A: Convert qualitative metrics into proxies (e.g., Net Promoter Score [NPS] linked to retention/churn revenue). All charters must have at least one hard-currency primary metric to be approved by the EPMO.

Julian Vance
Chief Architect, Template Registry