Project Charter Document is Prepared At

Standard Operating Procedure: Project Charter Preparation Workflow

Document ID: SOP-TR-PM-042
Effective Date: October 24, 2023
Version: 3.1.0
Review Cadence: Semi-Annual
Author: Julian Vance, Chief Architect

---

1. Document Control Block

---

2. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the exact lifecycle phase, trigger events, and procedural mechanics for when a Project Charter document is prepared within Template Registry infrastructure.

The Project Charter serves as the foundational governance artifact authorizing the existence of a project and providing the Project Manager with the authority to apply organizational resources to project activities. Adherence to this protocol ensures programmatic alignment, mitigation of scope creep, and strict traceability from institutional strategy to engineering execution.

---

3. Scope & Prerequisites

3.1 Scope

This procedure applies to all capital-expenditure projects, enterprise software initiatives, and core infrastructure modifications executed across all engineering and product divisions within Template Registry.

3.2 Prerequisites & Tooling

• Software Suite: Jira Portfolio, Confluence Enterprise (Template Registry PM Workspace), Enterprise Architecture Repository (Sparx/LeanIX).
• Templates: Approved Template Registry Project Charter v4.2 Schema.
• Access Control: Project Creator role authorization within the Enterprise Identity and Access Management (IAM) directory.
• Prerequisite Artifacts: Approved Business Case, Preliminary Risk Assessment, High-Level Resource Forecast.

---

4. Roles & Responsibilities

The governance matrix below defines accountability using the RACI framework: Responsible, Accountable, Consulted, Informed.

---

5. Step-by-Step Procedure

The Project Charter is prepared strictly during the Initiation Phase, immediately following the formal approval of the Business Case and prior to the allocation of any development sprints or capital expenditure.

Phase 1: Initiation Trigger & Workspace Provisioning

• 1.1 Verify that the Business Case has achieved an APPROVED status within the enterprise portfolio management system.
• 1.2 Provision a secure, access-controlled workspace within Confluence utilizing the designated Template-Registry-Charter-v4.2 schema.
• 1.3 Assign the Project Manager (PM) and Executive Sponsor access credentials within the project tracking workspace.

Phase 2: Scope & Objective Definition

• 2.1 Draft the Problem Statement utilizing quantifiable metrics extracted from the approved Business Case.
• 2.2 Define high-level project Objectives applying SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound).
• 2.3 Establish explicit Project Boundaries, detailing out-of-scope items to prevent scope expansion during execution phases.

Phase 3: Stakeholder & Resource Mapping

• 3.1 Identify primary stakeholders, categorizing them by influence and interest matrices within the architecture repository.
• 3.2 Input high-level financial forecasts, calculating total cost of ownership (TCO) and return on investment (ROI) thresholds.
• 3.3 Secure preliminary resource allocations via capacity planning tools, obtaining sign-off from functional engineering leads.

Phase 4: Risk Identification & Constraint Analysis

• 4.1 Enumerate top-tier enterprise risks (Technical, Financial, Operational) utilizing the Template Registry Risk Register template.
• 4.2 Formulate initial mitigation strategies for all identified high-severity risks.
• 4.3 Document external dependencies, legacy system integrations, and compliance constraints (e.g., SOC2, GDPR).

Phase 5: Review, Sign-off, and Baseline

• 5.1 Conduct a formal Charter Review walkthrough with the Chief Architect and Lead Systems Engineer.
• 5.2 Incorporate mandatory architectural adjustments and secure baseline approvals.
• 5.3 Route the finalized charter through Jira/Confluence workflow for digital signatures from the Executive Sponsor and Steering Committee.
• 5.4 Transition the project state from Initiation to Planning within the Enterprise Portfolio Management dashboard.

---

6. Quality Assurance & Pro-Tips

6.1 Best Practices

• Early Technical Alignment: Involve the Architecture team during Phase 2 to prevent structural deadlocks later in the engineering lifecycle.
• Quantifiable Metrics: Ensure objectives do not contain ambiguous language (e.g., replace "improve performance" with "reduce API latency to < 120ms at p99").

6.2 Common Pitfalls to Avoid

• Premature Execution: Do not authorize sprint planning or resource onboarding before the Charter is formally signed off by the Executive Sponsor.
• Scope Bloat: Guard against including detailed functional requirements within the charter; reserve deep functional decomposition for the Requirements Definition Phase.

6.3 Metric Thresholds

• Preparation Velocity: The charter must be prepared, reviewed, and signed within 10 business days of Business Case approval.
• Audit Compliance: 100% of initiated projects must exhibit an immutable, signed Charter artifact linked in the master registry.

---

7. Frequently Asked Questions (FAQ)

Q1: What happens if the project scope changes significantly after the charter is signed?
A: Any modification to budget, core objectives, or major milestones requires a formal Project Change Request (PCR). The PCR must be reviewed by the Chief Architect and approved by the Executive Sponsor before updating the baseline charter.

Q2: Can the Project Charter preparation phase overlap with architectural discovery?
A: Light technical discovery is permitted during Phase 1 and Phase 2 to validate assumptions; however, comprehensive technical design must occur downstream in the Planning Phase after the charter is baselined.

Q3: Who holds the ultimate authority to reject a Project Charter draft?
A: The Executive Sponsor holds the authority to reject the charter on financial or strategic grounds, while the Chief Architect holds the authority to reject it on systemic, security, or architectural compliance grounds.