Project Charter Template Waterfall

Standard Operating Procedure: Waterfall Project Charter Development

Document ID: SOP-PMO-001
Effective Date: 2023-10-27
Version: 1.0
Review Cadence: Annual

1. Executive Summary & Purpose

This SOP defines the standardized workflow for constructing a formal Project Charter for Waterfall-managed initiatives. The purpose is to establish baseline authority, define scope boundaries, identify primary stakeholders, and secure executive sponsorship prior to the initiation of the planning phase.

2. Scope & Prerequisites

• Scope: Applies to all projects within the organization exceeding 400 man-hours or $50k in budget.
• Prerequisites:
  • Completed Business Case.
  • Access to the Enterprise Project Management Office (EPMO) repository.
  • Standard Template: TR-PROJECT-CHARTER-WF-V1.docx.
• Software/Tools: Microsoft Project, Jira (for tracking), Confluence, or internal Template Registry instance.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Data Gathering & Scoping

• Conduct stakeholder interviews to define high-level requirements.
• Identify and document project constraints (time, budget, regulatory).
• Establish the "Definition of Done" for the project lifecycle.

Phase 2: Charter Drafting

• Define the Project Purpose (the "Why").
• Populate the "High-Level Milestone Schedule" (Critical Path identification).
• Assign budget estimation with a defined confidence interval (e.g., ±20%).
• Document preliminary risks, assumptions, and constraints (RAC matrix).

Phase 3: Review & Sign-off

• Circulation of draft for review to the Steering Committee.
• Conduct a formal "Go/No-Go" sign-off meeting.
• Secure wet/digital signatures from the Project Sponsor.
• Upload final artifact to the EPMO central registry.

5. Quality Assurance & Pro-Tips

• Metric Thresholds: A charter is considered "invalid" if the budget variance exceeds 15% during the approval gate.
• Best Practices:
  • The "SMART" Check: Ensure objectives are Specific, Measurable, Achievable, Relevant, and Time-bound.
  • Avoid Scope Creep: Explicitly state what the project will not include (Out-of-Scope list).
• Common Pitfalls:
  • Omitting the resource plan from the Charter leads to immediate friction in the Execution phase.
  • Failing to define "Success Metrics" creates ambiguity at project closure.

6. Frequently Asked Questions (FAQ)

Q: Can the charter be modified after sign-off?
A: No. Once signed, the charter is the project baseline. Any modification requires a formal Change Request (CR) documented through the Change Control Board (CCB).

Q: Who serves as the final arbiter if stakeholders disagree on the scope?
A: The Project Sponsor is the final arbiter for all scope-related disputes. The Project Manager is responsible for escalating these conflicts to the Sponsor within 24 hours of impasse.

Q: What is the minimum documentation required to initiate?
A: A signed Project Charter and a high-level budget breakdown are mandatory prerequisites for project code activation in the financial system.

Authorized by: Julian Vance, Chief Architect, Template Registry