Lean Six Sigma Project Charter Development Standard Operating Procedure

Standard Operating Procedure: Lean Six Sigma (LSS) Project Charter Development

Document ID: SOP-LSS-001
Effective Date: 2023-10-27
Version: 1.0.0
Review Cadence: Annual

---

1. Executive Summary & Purpose

This SOP dictates the standardized creation, validation, and archival of a Lean Six Sigma (LSS) Project Charter. The purpose is to define the boundaries, objectives, and financial justification of improvement initiatives, ensuring alignment with organizational strategy before resource allocation.

2. Scope & Prerequisites

• Scope: Applies to all DMAIC (Define, Measure, Analyze, Improve, Control) project charters within the Template Registry ecosystem.
• Prerequisites:
  • Approved Business Case.
  • Access to the Project Management Information System (PMIS).
  • Validated baseline performance data (if available).
  • Authorized LSS Green Belt or Black Belt certification/oversight.

3. Roles & Responsibilities (RACI)

---

4. Step-by-Step Procedure

Phase I: Charter Drafting

• Define the Business Case: Articulate the 'Why' using fiscal impact (cost of poor quality).
• Define the Problem Statement: Draft a SMART (Specific, Measurable, Achievable, Relevant, Time-bound) statement; eliminate "blame" language.
• Define the Goal Statement: Establish the target outcome (e.g., "Reduce cycle time from X to Y by Z date").
• Identify Scope Boundaries: List strictly what is IN-scope and OUT-of-scope to prevent scope creep.

Phase II: Stakeholder Alignment

• Identify Milestones: Map high-level DMAIC gates to a calendar.
• Define the Team: Document names, roles, and percentage of time committed.
• Review with Finance: Validate projected savings or efficiency metrics.

Phase III: Authorization

• Conduct a formal Charter Review Meeting with the Sponsor.
• Secure physical or electronic signature of the Project Charter.
• Upload final PDF to the centralized Template Registry Repository.

---

5. Quality Assurance & Pro-Tips

Quality Assurance Criteria

• Financial Integrity: All savings must be validated by the Finance lead.
• Metric Baseline: Every project must have a baseline period (e.g., last 6 months of performance).
• SMART Audit: If the Problem Statement contains a solution (e.g., "We need to install X"), it fails the audit. Focus on the defect, not the fix.

Pro-Tips

• The "So What?" Test: If you cannot explain the benefit to the bottom line in two sentences, the charter is too technical.
• Scope Realism: A common pitfall is attempting to boil the ocean. If the project duration exceeds 6 months, consider splitting into two phases.

---

6. Frequently Asked Questions (FAQ)

Q: Can I change the charter after it has been signed?

• A: Yes, but it requires a formal "Charter Amendment" document signed by the Sponsor if the scope or the primary objective changes by >15%.

Q: What if the baseline data is unavailable?

• A: The first phase of your project must be "Measure." The charter should reflect a preliminary estimate, to be updated once the baseline is established at the end of the Measure phase.

Q: How do I handle conflicts between the Process Owner and the Sponsor?

• A: Escalation must occur via the PMO. Document the dispute in the project risk log; the Charter remains in "Draft" status until the conflict is resolved in writing.

---

Authorized by: Julian Vance, Chief Architect