Project Charter Template Harvard

SOP-PMO-042: Institutional Project Charter Formulation (Harvard Standard)

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the systematic methodology for drafting a Project Charter consistent with Harvard Business School (HBS) management frameworks. The purpose is to provide a standardized, rigorous foundation for project initiation, ensuring strategic alignment, scope clarity, and institutional authorization.

2. Scope & Prerequisites

• Scope: Applicable to all enterprise-level projects requiring formal executive sponsorship.
• Required Tools: MS Word (Template v.2.1), Enterprise PMIS (e.g., Jira/Asana), Financial Model (Excel/BI integration).
• Prerequisites: Completed "Pre-Initiation Brief," approved Business Case, and identified Project Sponsor.

3. Roles & Responsibilities (RACI Matrix)

4. Step-by-Step Procedure

Phase I: Strategic Alignment & Definition

• Define the Business Need: Explicitly state the problem or opportunity.
• Establish Objectives: Apply SMART (Specific, Measurable, Achievable, Relevant, Time-bound) criteria.
• Articulate Strategic Fit: Map the project to the organization’s current fiscal-year goals.

Phase II: Scope & Resource Constraints

• Define In-Scope/Out-of-Scope boundaries to prevent scope creep.
• Identify Key Milestones: Define high-level deliverable dates.
• Draft Budgetary Estimates: Identify hard costs, soft costs, and contingency reserves.

Phase III: Institutional Authorization

• Document Assumptions & Constraints: List technical, legal, and operational limitations.
• Formalize Governance Structure: Define the escalation path for conflict resolution.
• Secure Sign-off: Obtain physical or digital signatures from the Sponsor and key stakeholders.

5. Quality Assurance & Pro-Tips

Quality Thresholds:

• Alignment Index: 100% of milestones must map back to an identified business objective.
• Approval Cycle: Maximum 3 business days for final sign-off once the final draft is circulated.

Pro-Tips:

• Pitfall Avoidance: Never draft a charter without first quantifying the "Cost of Inaction."
• Clarity Rule: If a stakeholder cannot identify their role within 30 seconds of reading the document, the Governance section is too complex.
• The "Why" Test: Every item in the scope must answer: "Does this advance the project's strategic mission?"

6. Frequently Asked Questions (FAQ)

Q: What if the Project Sponsor refuses to sign due to budget ambiguity? A: Escalate to the PMO Steering Committee for a scope re-evaluation. Do not initiate project activities until the Charter is ratified.

Q: How do I handle evolving requirements post-approval? A: Any change to the approved charter requires a formal Change Request (CR) documented as an addendum to this document.

Q: Is this template compatible with Agile workflows? A: Yes. The Harvard Charter defines the "North Star." Agile epics and user stories are derived from these high-level objectives during the planning phase.

Authorized by: Julian Vance Chief Architect, Template Registry