Project Charter Template from Pmi

SOP: Project Charter Development (PMI Framework)

1. Executive Summary & Purpose

This SOP establishes the standardized methodology for developing a Project Charter compliant with the Project Management Institute (PMI) Project Management Body of Knowledge (PMBOK). The purpose is to formally authorize the existence of a project, provide the project manager with the authority to apply organizational resources, and align stakeholders on high-level objectives.

2. Scope & Prerequisites

• Scope: Applies to all projects requiring formal executive approval within Template Registry.
• Prerequisites:
  • Approved Project Business Case.
  • Validated Stakeholder Register (Preliminary).
  • Access to the Enterprise Project Management (EPM) repository.
  • Software: Project Management Information System (PMIS) or standardized Markdown-based documentation suite.

3. Roles & Responsibilities (RACI)

• Responsible (R): Performs the work.
• Accountable (A): The decision-maker (only one).
• Consulted (C): Provides input.
• Informed (I): Kept in the loop.

4. Step-by-Step Procedure

Phase I: Data Acquisition

• Collate the Business Case, feasibility studies, and contractual agreements.
• Conduct stakeholder interviews to extract high-level requirements.
• Identify high-level risks, assumptions, and constraints.

Phase II: Charter Drafting

• Define Project Purpose/Justification: Link directly to business strategy.
• Establish Measurable Objectives: Include S.M.A.R.T. criteria (Specific, Measurable, Achievable, Relevant, Time-bound).
• Document High-Level Requirements: Functional and non-functional requirements.
• Define Boundaries: Clearly state what is out of scope to prevent scope creep.
• Outline Key Deliverables: High-level outputs defining project completion.
• Establish Summary Budget & Timeline: Include high-level milestone dates and budgetary cap.

Phase III: Authorization

• Route the draft to the Project Sponsor for review.
• Conduct a Charter Signing Meeting to resolve remaining blockers.
• Obtain physical or digital signature (e-sign) from the Sponsor.
• Publish the final PDF/Markdown to the central PMO repository.

5. Quality Assurance & Pro-Tips

• QA Metric: 100% of Charters must pass the "Alignment Test": Can the project goal be mapped back to a specific line item in the annual corporate budget?
• Pro-Tip (The "Scope Anti-Pattern"): Avoid putting detailed WBS (Work Breakdown Structure) items in the Charter. Keep it at a strategic, high-level view.
• Common Pitfall: Failing to define the exit criteria for the project sponsor. Ensure the "Definition of Done" for the project is universally understood.

6. Frequently Asked Questions

Q: Does the Charter need to be updated during the project life cycle? A: No. The Charter is a static, authorizing document. If fundamental project objectives change significantly, a Project Change Request (PCR) should be filed to revise the Charter, but the original version should remain archived.

Q: How granular should the milestone list be? A: Keep milestones limited to 5-8 major checkpoints (e.g., Phase Gates). Granular task tracking belongs in the Project Management Plan, not the Charter.

Authorized by: Julian Vance Chief Architect, Template Registry