PROJECT CHARTER

ميثاق المشروع

tasleemat asset PMO-03.01 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 03: Initiating

Sizing Tier Requirements

Tier 1 Tier 2 Tier 3

Validation Contract

This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.

tasleemat validate PMO-03.01 ./completed_data.json

Template Markdown (Bilingual)

<!--  LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.

Section Instructions:
*   **Project purpose:** The reason the project is being undertaken. May refer to a business case, the organization’s strategic plan, external factors, a contract agreement, or any other reason for performing the project.
*   **High-level project description:** A summary-level description of the project.
*   **Project boundaries:** Limits to the project scope. May include scope exclusions, or other limitations.
*   **Key deliverables:** The high-level project and product deliverables. These will be further elaborated in the project scope statement.
*   **High-level requirements:** The high-level conditions or capabilities that must be met to satisfy the purpose of the project. Describe the product features and functions that must be present to meet stakeholders’ needs and expectations. These will be further elaborated in the requirements documentation.
*   **High-level assumptions and constraints:** High-level assumptions are factors considered to be true, real, or certain without proof or demonstration. Constraints are limiting factors that affect the execution of a project, program, portfolio, or process.
*   **Overall project risk:** An assessment of the overall riskiness of the project. Overall risk can include the underlying political, social, economic, and technological volatility, uncertainty, complexity, and ambiguity. It pertains to the stakeholder exposure to variations in the project outcome.
*   **Project objectives and related success criteria:** Project objectives are usually established for at least scope, schedule, and cost. The success criteria identify the metrics or measurements that will be used to measure success.
*   **Summary milestone schedule:** Significant events in the project. Examples include the completion of key deliverables, the beginning or completion of a project phase, or product acceptance.
*   **Preapproved financial resources:** The amount of funding available for the project. May include sources of funding and annual funding limits.
*   **Key stakeholder list:** An initial, high-level list of people or groups that have influenced or can influence project success, as well as those who are influenced by its success.
*   **Project exit criteria:** The performance, metrics, conditions, or other measurements that must be met to conclude the project.
*   **Project approval requirements:** Defines what constitutes project success, who determines whether the project is successful, and who signs off on the project.
*   **Project manager authority - Staffing Decisions:** The authority of the project manager to hire, fire, discipline, accept, or not accept project staff.
*   **Project manager authority - Budget management and Variance:** The authority of the project manager to commit, manage, and control project funds, and the variance level that requires escalation.
*   **Project manager authority - Technical Decisions:** The authority of the project manager to make technical decisions about deliverables or the project approach.
*   **Project manager authority - Conflict resolution:** The degree to which the project manager can resolve conflict within the team, within the organization, and with external stakeholders.
*   **Name and authority of the sponsor:** Name and authority of the sponsor or other person(s) authorizing the project charter.
-->

<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">PROJECT CHARTER</h1>

| **Project Sponsor:** {{Project_Sponsor_Name}} | **Date Prepared:** {{Current_Date}} |
| :--- | :--- |
| **Project Manager:** {{Project_Manager_Name}} | **Project Customer:** {{Client_Customer_Name}} |  

---

## Project purpose
<!-- The reason the project is being undertaken. May refer to a business case, the organization’s strategic plan, external factors, a contract agreement, or any other reason for performing the project. -->
[ Add details... ]

---

## High-level project description
<!-- A summary-level description of the project. -->
[ Add details... ]

---

## Project boundaries
<!-- Limits to the project scope. May include scope exclusions, or other limitations. -->
[ Add details... ]

---

## Key deliverables
<!-- The high-level project and product deliverables. These will be further elaborated in the project scope statement. -->
[ Add details... ]

---

## High-level requirements
<!-- The high-level conditions or capabilities that must be met to satisfy the purpose of the project. Describe the product features and functions that must be present to meet stakeholders’ needs and expectations. These will be further elaborated in the requirements documentation. -->
[ Add details... ]

---

## High-level assumptions and constraints
<!-- High-level assumptions are factors considered to be true, real, or certain without proof or demonstration. Constraints are limiting factors that affect the execution of a project, program, portfolio, or process. -->
[ Add details... ]

---

## Overall project risk
<!-- An assessment of the overall riskiness of the project. Overall risk can include the underlying political, social, economic, and technological volatility, uncertainty, complexity, and ambiguity. It pertains to the stakeholder exposure to variations in the project outcome. -->
[ Add details... ]

---

## Project objectives and related success criteria
<!-- Project objectives are usually established for at least scope, schedule, and cost. The success criteria identify the metrics or measurements that will be used to measure success. -->
| Item | Project objectives | Success criteria |
| :--- | :--- | :--- |
| **Scope** | [ Add details... ] | [ Add details... ] |
| **Schedule** | [ Add details... ] | [ Add details... ] |
| **Cost** | [ Add details... ] | [ Add details... ] |
| **Other** | [ Add details... ] | [ Add details... ] |

---

## Summary milestone schedule
<!-- Significant events in the project. Examples include the completion of key deliverables, the beginning or completion of a project phase, or product acceptance. -->
| # | Summary milestones | Due Date |
| :---: | :--- | :---: |
| 1 | [ Add details... ] | [ Add details... ] |
| 2 | [ Add details... ] | [ Add details... ] |
| 3 | [ Add details... ] | [ Add details... ] |

---

## Preapproved financial resources
<!-- The amount of funding available for the project. May include sources of funding and annual funding limits. -->
[ Add details... ]

---

## Key stakeholder list
<!-- An initial, high-level list of people or groups that have influenced or can influence project success, as well as those who are influenced by its success. -->
| Stakeholder(s) | Role(s) |
| :--- | :--- |
| [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] |

---

## Project exit criteria
<!-- The performance, metrics, conditions, or other measurements that must be met to conclude the project. -->
[ Add details... ]

---

## Project approval requirements
<!-- Defines what constitutes project success, who determines whether the project is successful, and who signs off on the project. -->
[ Add details... ]

---

## Project manager authority level
<!-- The authority of the project manager with regard to staffing, budget management and variance, technical decisions, and conflict resolution. -->
| Authority Area | Description |
| :--- | :--- |
| Staffing decisions | [ Add details... ] |
| Budget management and variance | [ Add details... ] |
| Technical decisions | [ Add details... ] |
| Conflict resolution | [ Add details... ] |

---

## Name and authority of the sponsor
<!-- Name and authority of the sponsor or other person(s) authorizing the project charter. -->
| Name / Position | Authority Level |
| :--- | :--- |
| [ Add details... ] | [ Add details... ] |

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Sponsor** | {{Project_Sponsor_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Key Stakeholder / Client** | {{Client_Representative_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> PROJECT CHARTER | <strong>Ref:</strong> PMO-03.01 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

User Guide & Practitioner Instructions

Tasleemat Forms Guide

Project Artifact: Project Charter

Document Reference: PMO-03.01

This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Project Charter in alignment with the Tasleemat framework.

1. What?

A formal document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.

2. Why?

It establishes a direct link between the project and the strategic objectives of the organization, creates a formal record of the project, and shows the organizational commitment to the project.

3. When?

Developed in the Initiating Process Group at the very beginning of the project or phase.

4. Who?

Issued by the Project Sponsor, authored/drafted with the Project Manager, and signed off by key authorizing executives.

Tailoring Tips

Scale the level of detail to project complexity and investment size.
Ensure clear boundaries and explicit scope exclusions to avoid early misalignment.
Define measurable success criteria across scope, schedule, cost, and quality.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Business Case (PMO-01.01)
- Strategic Plan
Optional / Contextual:
- Program Charter (PMO-00.02)
- Portfolio Roadmap (PMO-00.01)
- AI Use Case Canvas (PMO-02.04)

2. Downstream Dependents

Mandatory:
- Project Management Plan (PMO-04.01.01)
- Stakeholder Register (PMO-03.04)
- Assumption Log (PMO-03.03)
- Scope Statement (PMO-04.02.05)
Optional / Contextual:
- Tailoring Plan (PMO-02.01)
- Team Charter (PMO-04.06.05)
- Product Vision (PMO-03.02)

5. How?

To accurately and professionally complete the Project Charter, the responsible party must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):

Project purpose: The reason the project is being undertaken. May refer to a business case, the organization’s strategic plan, external factors, a contract agreement, or any other reason for performing the project.
High-level project description: A summary-level description of the project detailing its core scope and business context.
Project boundaries: Limits to the project scope. May include scope exclusions, or other limitations.
Key deliverables: The high-level project and product deliverables. These will be further elaborated in the project scope statement.
High-level requirements: The high-level conditions or capabilities that must be met to satisfy the purpose of the project. Describe the product features and functions that must be present to meet stakeholders’ needs and expectations. These will be further elaborated in the requirements documentation.
High-level assumptions and constraints: High-level assumptions are factors considered to be true, real, or certain without proof or demonstration. Constraints are limiting factors that affect the execution of a project, program, portfolio, or process.
Overall project risk: An assessment of the overall riskiness of the project. Overall risk can include the underlying political, social, economic, and technological volatility, uncertainty, complexity, and ambiguity. It pertains to the stakeholder exposure to variations in the project outcome.
Project objectives and related success criteria: Project objectives are usually established for at least scope, schedule, and cost. The success criteria identify the metrics or measurements that will be used to measure success.
Summary milestone schedule: Significant events in the project. Examples include the completion of key deliverables, the beginning or completion of a project phase, or product acceptance.
Preapproved financial resources: The amount of funding available for the project. May include sources of funding and annual funding limits.
Key stakeholder list: An initial, high-level list of people or groups that have influenced or can influence project success, as well as those who are influenced by its success.
Project exit criteria: The performance, metrics, conditions, or other measurements that must be met to conclude the project.
Project approval requirements: Defines what constitutes project success, who determines whether the project is successful, and who signs off on the project.
Project manager authority level: The authority of the project manager with regard to staffing decisions, budget management and variance, technical decisions, and conflict resolution.
Name and authority of the sponsor: Name and authority of the sponsor or other person(s) authorizing the project charter.

6. Reference Example

A fully completed, gold-standard reference example illustrating this artifact in practice is available:

📖 Completed Example: 03_01_Project_Charter_Example.md

LLM Generation Prompt & Agent Instructions

Project Charter - Generation Prompt

System Instructions: This document contains instructions for generating the «Project Charter». When asked to fill this template, follow the section-by-section instructions below. Refer to parameters.md for project variables.

Context and Definition: A document issued by the project sponsor that formally authorizes the existence of a project and provides the project manager with authority to apply organizational resources to project activities.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Business Case (PMO-01.01), Strategic Plan * Optional: Program Charter (PMO-00.02), Portfolio Roadmap (PMO-00.01), AI Use Case Canvas (PMO-02.04) * Downstream Dependents: * Mandatory: Project Management Plan (PMO-04.01.01), Stakeholder Register (PMO-03.04), Assumption Log (PMO-03.03), Scope Statement (PMO-04.02.05) * Optional: Tailoring Plan (PMO-02.01), Team Charter (PMO-04.06.05), Product Vision (PMO-03.02)

Project purpose

Instruction: The reason the project is being undertaken. May refer to a business case, the organization’s strategic plan, external factors, a contract agreement, or any other reason for performing the project.