PMO-04.06.05 Phase 04: Planning

TEAM CHARTER

ميثاق الفريق

tasleemat asset PMO-04.06.05 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 04: Planning

Sizing Tier Requirements

Validation Contract

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

tasleemat validate PMO-04.06.05 ./completed_data.json

Template Markdown (Bilingual)

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

Section Instructions:
- Team Values and Shared Vision: Provide comprehensive project data for all required fields in this section.
- Operating Agreements and Guidelines: Provide comprehensive project data for all required fields in this section.
- Communication and Meeting Protocols: Provide comprehensive project data for all required fields in this section.
- Decision-Making and Conflict Resolution: Provide comprehensive project data for all required fields in this section.
-->

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

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |

---

## 1. Team Values and Shared Vision

**Core Team Values:**
[ Add details... ]

**Shared Project Mission and Vision:**
[ Add details... ]

---

## 2. Operating Agreements and Guidelines

**Working Norms and Ground Rules:**
[ Add details... ]

**Core Working Hours and Availability:**
[ Add details... ]

---

## 3. Communication and Meeting Protocols

**Meeting Cadence and Rules:**
[ Add details... ]

**Communication Channels Usage:**
[ Add details... ]

---

## 4. Decision-Making and Conflict Resolution

**Decision-Making Framework:**
[ Add details... ]

**Conflict Escalation and Resolution Steps:**
[ Add details... ]

**Team Signatures and Commitment:**
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Team Lead / Scrum Master** | {{Team_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
| **Team Representative** | {{Team_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> TEAM CHARTER | <strong>Ref:</strong> PMO-04.06.05 <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: Team Charter

Document Reference: PMO-04.06.05

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

1. What?

A team social contract defining ground rules, meeting expectations, decision rules, and conflict resolution mechanisms.

2. Why?

Fosters psychological safety, reduces interpersonal friction, enhances team cohesion, and promotes mutual accountability.

3. When?

Created early during project team onboarding and revisited during retrospectives and major team transitions.

4. Who?

Authored collaboratively by the Entire Project Team with facilitator guidance from Project Manager or Scrum Master.

Tailoring Tips

Incorporate agile team working agreements, sprint cadence norms, and mob programming guidelines.
Define multi-site, multi-timezone virtual collaboration standards for distributed teams.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Work Breakdown Structure / WBS (PMO-04.02.06)
- Project Schedule (PMO-04.03.08)
Optional / Contextual:
- Resource Capacity Matrix (PMO-00.04)
- Cost Management Plan (PMO-04.04.01)

2. Downstream Dependents

Mandatory:
- Responsibility Assignment Matrix / RAM (PMO-04.06.04)
- Team Charter (PMO-04.06.05)
- Team Performance Assessment (PMO-05.06)
Optional / Contextual:
- Team Onboarding Checklist (PMO-05.12)
- Training Plan & Log (PMO-04.11.02)

5. How?

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

Core Team Values: Guiding moral, professional, and behavioral values agreed upon by the team.
Shared Project Mission and Vision: Collective vision articulating the team's commitment to delivering quality project outcomes.
Working Norms and Ground Rules: Standard rules governing daily conduct, accountability, punctuality, and mutual respect.
Core Working Hours and Availability: Agreed overlapping collaboration hours, remote working standards, and response timeframes.
Meeting Cadence and Rules: Protocols for daily standups, status meetings, retrospectives, agendas, and note taking.
Communication Channels Usage: Guidelines defining appropriate use of instant messaging, email, ticketing, and documentation repositories.
Decision-Making Framework: Agreed decision methodology (e.g., consensus, majority vote, or technical lead authority).
Conflict Escalation and Resolution Steps: Constructive step-by-step process for resolving interpersonal and technical disputes.
Team Signatures and Commitment: Formal acknowledgment and commitment signed by all active project team members.

6. Reference Example

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

📖 Completed Example: 04_06_05_Team_Charter_Example.md

LLM Generation Prompt & Agent Instructions

Team Charter - Generation Prompt

System Instructions: This document contains instructions for generating the «Team 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 collaborative document that establishes the team values, agreements, communication norms, and operating guidelines for the project team.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Work Breakdown Structure / WBS (PMO-04.02.06), Project Schedule (PMO-04.03.08) * Optional: Resource Capacity Matrix (PMO-00.04), Cost Management Plan (PMO-04.04.01) * Downstream Dependents: * Mandatory: Responsibility Assignment Matrix / RAM (PMO-04.06.04), Team Charter (PMO-04.06.05), Team Performance Assessment (PMO-05.06) * Optional: Team Onboarding Checklist (PMO-05.12), Training Plan & Log (PMO-04.11.02)