PMO-04.03.08 Phase 04: Planning

PROJECT SCHEDULE

الجدول الزمني للمشروع

tasleemat asset PMO-04.03.08 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.03.08 ./completed_data.json

Template Markdown (Bilingual)

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

Section Instructions:
- Baseline Schedule Summary: Provide comprehensive project data for all required fields in this section.
- Detailed Schedule Data: Provide comprehensive project data for all required fields in this section.
- Critical Path and Float Analysis: 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">PROJECT SCHEDULE</h1>

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

---

## 1. Baseline Schedule Summary

**Project Start and Target Finish Dates:**
[ Add details... ]

**Schedule Data Version and Baseline Status:**
[ Add details... ]

**Total Critical Path Length and Major Phases:**
[ Add details... ]

---

## 2. Detailed Schedule Data

**WBS Code and Activity Schedule Mapping:**
[ Add details... ]

**Planned Start and Finish Dates:**
[ Add details... ]

**Assigned Resources and Effort Allocation:**
[ Add details... ]

---

## 3. Critical Path and Float Analysis

**Critical Path Flag and Dependencies:**
[ Add details... ]

**Total Float and Free Float Values:**
[ Add details... ]

**Schedule Risk and Recovery Considerations:**
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Planner / Scheduler** | {{Scheduler_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Sponsor** | {{Project_Sponsor_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 SCHEDULE | <strong>Ref:</strong> PMO-04.03.08 <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 Schedule

Document Reference: PMO-04.03.08

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

1. What?

The definitive schedule model documenting start/finish dates, critical path, float, and assigned resources for all work.

2. Why?

Serves as the authorized baseline to direct daily work, measure progress, and manage project completion commitments.

3. When?

Baselined upon planning completion and updated at each reporting cycle.

4. Who?

Maintained by Project Scheduler and Project Manager, approved by Project Sponsor and PMO Director.

Tailoring Tips

Represent as sprint and release cadence burndown schedules for agile delivery.
Maintain fully detailed Gantt and CPM schedules for complex multi-party contractual engagements.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Work Breakdown Structure / WBS (PMO-04.02.06)
- Scope Statement (PMO-04.02.05)
Optional / Contextual:
- Resource Requirements (PMO-04.06.02)
- Risk Register (PMO-04.08.02)

2. Downstream Dependents

Mandatory:
- Project Schedule Baseline (PMO-04.03.08)
- Earned Value Analysis / EVA (PMO-06.05)
Optional / Contextual:
- Release Plan (PMO-04.03.09)
- Lookahead Planning Log (PMO-04.03.10)

5. How?

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

Project Start and Target Finish Dates: The authorized baseline start date and targeted project completion date.
Schedule Data Version and Baseline Status: The formal schedule model version number and baseline authorization state.
Total Critical Path Length and Major Phases: Total working days on the critical path and scheduled durations for each major project phase.
WBS Code and Activity Schedule Mapping: Consolidated schedule line items linking WBS code, activity title, and work package.
Planned Start and Finish Dates: Approved baseline start date and baseline completion date for each scheduled activity.
Assigned Resources and Effort Allocation: Designated resource leads, team members, and allocated effort hours per activity.
Critical Path Flag and Dependencies: Clear indicator (Yes/No) identifying critical path activities and predecessor linkages.
Total Float and Free Float Values: Calculated total float and free float values in working days for each schedule activity.
Schedule Risk and Recovery Considerations: Identification of high-risk scheduling bottlenecks and contingency deployment rules.

6. Reference Example

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

📖 Completed Example: 04_03_08_Project_Schedule_Example.md

LLM Generation Prompt & Agent Instructions

Project Schedule - Generation Prompt

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

Context and Definition: The primary schedule output that presents linked activities with planned dates, durations, milestones, and resource allocations.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Work Breakdown Structure / WBS (PMO-04.02.06), Scope Statement (PMO-04.02.05) * Optional: Resource Requirements (PMO-04.06.02), Risk Register (PMO-04.08.02) * Downstream Dependents: * Mandatory: Project Schedule Baseline (PMO-04.03.08), Earned Value Analysis / EVA (PMO-06.05) * Optional: Release Plan (PMO-04.03.09), Lookahead Planning Log (PMO-04.03.10)