ACTIVITY LIST

قائمة الأنشطة

tasleemat asset PMO-04.03.02 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 04: Planning

Sizing Tier Requirements

Tier 1

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.02 ./completed_data.json

Template Markdown (Bilingual)

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

Section Instructions:
- Schedule Activity Inventory: Provide comprehensive project data for all required fields in this section.
- Activity Details and Descriptions: Provide comprehensive project data for all required fields in this section.
- Associated WBS Work Packages: 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">ACTIVITY LIST</h1>

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

---

## 1. Schedule Activity Inventory

**Activity Identifier and Name:**
[ Add details... ]

**Activity Scope of Work:**
[ Add details... ]

**Planned Iteration or Release:**
[ Add details... ]

---

## 2. Activity Details and Descriptions

**Activity Execution Method:**
[ Add details... ]

**Estimated Effort and Duration Units:**
[ Add details... ]

---

## 3. Associated WBS Work Packages

**Parent WBS Work Package Mapping:**
[ Add details... ]

**Activity Completion Deliverable:**
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Planner / Scheduler** | {{Scheduler_Name}} | _______________________ | [ .... - .... - .... ] |
| **Technical / Work Package Lead** | {{Work_Package_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_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> ACTIVITY LIST | <strong>Ref:</strong> PMO-04.03.02 <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: Activity List

Document Reference: PMO-04.03.02

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

1. What?

A detailed inventory of project activities containing identifiers, scope of work descriptions, and WBS mappings.

2. Why?

Provides the atomic building blocks needed for schedule network sequencing, resource estimating, and duration analysis.

3. When?

Developed during schedule planning immediately after WBS creation and refined iteratively.

4. Who?

Created by Project Scheduler and Core Technical Team leads, reviewed by Project Manager.

Tailoring Tips

Maintain as backlog tasks during sprint planning for agile deliveries.
Ensure full 1-to-1 WBS traceability for construction and engineering schedules.

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 Activity List, the responsible party must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):

Activity Identifier and Name: Unique activity code and concise action-oriented title for each schedule activity.
Activity Scope of Work: Specific narrative detailing the discrete scope of work to be performed in this activity.
Planned Iteration or Release: The target delivery sprint, wave, or milestone window assigned to this activity.
Activity Execution Method: Technical or managerial execution approach applied to perform the work.
Estimated Effort and Duration Units: Estimated working effort in person-hours and planned calendar duration.
Parent WBS Work Package Mapping: The parent WBS work package identifier and deliverable directly decomposed by this activity.
Activity Completion Deliverable: The tangible or verified intermediate output produced upon activity completion.

6. Reference Example

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

📖 Completed Example: 04_03_02_Activity_List_Example.md

LLM Generation Prompt & Agent Instructions

Activity List - Generation Prompt

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

Context and Definition: A comprehensive table listing all scheduled activities required on the project to decompose WBS work packages into manageable execution units.

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)