Project Charter Template Atlassian

Standard Operating Procedure: Project Charter Standardization

Document ID: SOP-TR-PM-042
Effective Date: 2023-10-27
Version: 2.1.0
Review Cadence: Semi-Annual (Q2/Q4)

1. Executive Summary & Purpose

This SOP mandates the standardization of Project Charters within the Template Registry ecosystem using Atlassian Confluence. The purpose is to ensure cross-departmental alignment, define fiscal/resource boundaries, and establish objective success criteria for all incoming high-impact projects.

2. Scope & Prerequisites

• Scope: All projects initiated under the Template Registry governance model.
• Tools: Atlassian Confluence (Cloud/Data Center), Jira (Integration linked).
• Prerequisites:
  • Active Atlassian Cloud site permissions.
  • Access to the 'Template Registry Space' template library.
  • Completed Project Concept Note (PCN) approval.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Initiation & Template Deployment

• Navigate to the specific Confluence Space designated for the project.
• Select Create > Template > Project Charter (TR-Standard).
• Apply the relevant labels: status-draft, dept-project, fy-current.

Phase II: Execution of Charter Content

• Define Business Case: Articulate the 'Why' using the 3-point alignment model (Strategic, Financial, Operational).
• Establish Scope Parameters: Explicitly document 'In-Scope' and 'Out-of-Scope' buckets.
• Milestone Mapping: Link the Jira project board to the Confluence page via the Jira Roadmap macro.
• Resource Procurement: List FTE requirements and capital expenditure (CapEx) requests.

Phase III: Validation & Formal Sign-off

• Tag the Project Sponsor and Portfolio Lead in the 'Approvals' section using the @{Name} function.
• Verify that all 'Risk & Dependency' logs have been updated.
• Publish the page to signal the transition from Draft to Baseline status.

5. Quality Assurance & Pro-Tips

• Metric Thresholds: A Charter is rejected if it lacks a defined "Exit Criteria" or "Primary Success Metric" (e.g., ROI target or time-to-market reduction).
• Pro-Tip 1: Use the Page Properties Report macro at the space level to aggregate charter status across all projects automatically.
• Pro-Tip 2: Never define a date-driven milestone without an associated "Dependency" check in Jira.
• Common Pitfall: Over-complicating the 'Background' section. Keep history brief; focus on the future-state.

6. Frequently Asked Questions (FAQ)

Q: Should I create a new Confluence page or a sub-page of an existing Project Space?
A: Always create it at the root of the designated Project Space to maintain a clean breadcrumb trail for compliance audits.

Q: Can I modify the template fields provided by the Registry?
A: No. Mandatory fields are immutable to ensure standardized data extraction for the Portfolio Office. Custom info should be added in a separate 'Addendum' section.

Q: What if the Sponsor is unresponsive during the approval phase?
A: Escalation is permitted after 72 hours of no activity. Flag the page with the status-stalled label and notify the PMO Director.

Authorized by: Julian Vance, Chief Architect