Project Charter Template Dmaic

Standard Operating Procedure: Project Charter Development (DMAIC Framework)

1. Executive Summary & Purpose

This SOP establishes the mandatory protocol for drafting a Project Charter utilizing the DMAIC (Define, Measure, Analyze, Improve, Control) methodology. The objective is to standardize project initiation, ensuring strategic alignment, clearly defined scope, and resource commitment prior to project execution.

2. Scope & Prerequisites

• Scope: Applies to all process improvement initiatives across Template Registry.
• Prerequisites: Access to the Enterprise Project Management Office (EPMO) portal; approved Business Case; baseline performance data (if available).
• Software: Lucidchart/Visio (process mapping), Jira/Confluence, MS Excel (data analytics).
• PPE: N/A (Administrative/Digital environment).

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Problem Definition & Scope

• Define the Business Case (Why now? What is the cost of inaction?).
• Draft the Problem Statement (Quantified gap between current and desired state).
• Articulate the Project Goal/Objective (SMART criteria).
• Establish Scope Boundaries (In-scope vs. Out-of-scope).

Phase 2: Timeline & Milestones

• Map the project schedule against DMAIC phase gates.
• Identify key deliverable dates for the Define, Measure, Analyze, Improve, and Control phases.

Phase 3: Team Formation & Resource Allocation

• List core team members and estimated time commitment (as a % of total hours).
• Secure written sign-off from functional managers for all assigned resources.

Phase 4: Finalization & Approval

• Submit draft for peer review by the PMO Lead.
• Conduct a Charter Signing Meeting with the Sponsor.
• Archive signed version in the central Registry repository.

5. Quality Assurance & Pro-Tips

• Metric Thresholds: Ensure the "Financial Impact" field is vetted by Finance if the expected ROI exceeds $50k.
• Pro-Tip (The "Scope Creep" Filter): If your Problem Statement contains the word "and" more than twice, your scope is likely too broad. Break the project into sub-charters.
• Common Pitfall: Failing to define what is not in scope. Explicitly listing "out-of-scope" items is the primary defense against project bloating.
• Quality Check: Before submission, verify that the Project Objective directly correlates to the Problem Statement metrics.

6. Frequently Asked Questions (FAQ)

Q: Can I modify the Charter template structure? A: No. Any deviation from the institutional template must be approved by the Chief Architect to maintain data normalization across the registry.

Q: What if the Project Sponsor is unavailable to sign? A: Delegation of authority must be submitted in writing. A charter without an authorized signatory is considered a "Draft" and carries zero execution authority.

Q: How do I handle changes to the charter once the project has started? A: Any changes to the scope or team composition after the Define phase require a formal "Charter Amendment Request" (Form TR-MOD-09).

End of Document Authorized by: Julian Vance, Chief Architect, Template Registry.