Project Charter Development Standard Operating Procedure

Standard Operating Procedure: Project Charter Development

Template Registry Engineering Standards

---

1. Document Control Block

---

2. Executive Summary & Purpose

The Project Charter serves as the authoritative document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. The purpose of this SOP is to standardize the creation, validation, and archival of project charters to ensure alignment with organizational objectives and risk tolerance.

---

3. Scope & Prerequisites

• Scope: Applies to all Tier-1 and Tier-2 engineering initiatives within Template Registry.
• Required Tools: Template Registry Project Management Suite (PMS), Confluence (documentation), Slack (stakeholder communication).
• Prerequisites: Completed Business Case, approved budget allocation, and defined Sponsor.
• PPE/Security: Standardized VPN access and MFA-protected document repositories are mandatory.

---

4. Roles & Responsibilities (RACI)

---

5. Step-by-Step Procedure

Phase 1: Initiation & Data Gathering

• Define the business problem or opportunity statement (Max 150 words).
• Extract high-level requirements from the Project Request Form (PRF).
• Conduct a stakeholder analysis to identify key influencers and blockers.

Phase 2: Definition of Boundaries

• Define In-Scope activities and deliverables.
• Define Out-of-Scope activities to prevent scope creep.
• Identify top 3 critical path risks and initial mitigation strategies.

Phase 3: Resource & Timeline Calibration

• Define high-level milestones (Quarterly or Monthly).
• Establish initial budget constraints and CAPEX/OPEX classifications.
• Define Success Criteria (Key Performance Indicators).

Phase 4: Finalization & Approval

• Perform a peer review for technical accuracy.
• Obtain formal digital sign-off from the Project Sponsor.
• Archive document in the Master Registry and notify stakeholders.

---

6. Quality Assurance & Pro-Tips

• Metric Thresholds: A charter is considered "High Quality" if it defines at least one measurable KPI that is tied to a specific financial or efficiency outcome.
• Pro-Tip (The Julian Vance Method): Never start a project without an explicit "Exit Criteria" section. Knowing how to kill a project is just as important as knowing how to launch one.
• Common Pitfall: Avoiding "Assumptions." If you don't list your assumptions (e.g., resource availability, vendor timelines), they will inevitably become "hidden constraints."

---

7. Frequently Asked Questions (FAQ)

Q: Can the charter be modified after approval? A: Yes, via a formal "Change Request" (CR) process. Minor administrative edits require internal team notice; scope or budget changes require re-signing by the Sponsor.

Q: What is the recommended length for an institutional-grade charter? A: For Template Registry projects, the target is 3–5 pages. If it exceeds 5 pages, it is a Project Management Plan (PMP), not a Charter.

---

End of Document. Authorized by Julian Vance, Chief Architect.