PMO-04.03.03 Phase 04: Planning

ACTIVITY ATTRIBUTES

سمات النشاط

tasleemat asset PMO-04.03.03 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.03 ./completed_data.json

Template Markdown (Bilingual)

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

Section Instructions:
- Activity Identification and Overview: Provide comprehensive project data for all required fields in this section.
- Activity Predecessors and Successors: Provide comprehensive project data for all required fields in this section.
- Resource and Skill Requirements: Provide comprehensive project data for all required fields in this section.
- Execution Constraints and Imposed Dates: 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 ATTRIBUTES</h1>

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

---

## 1. Activity Identification and Overview

**Activity Code and Title:**
[ Add details... ]

**Activity Description and Scope Summary:**
[ Add details... ]

**Assigned Work Package Reference:**
[ Add details... ]

---

## 2. Activity Predecessors and Successors

**Predecessor Activities and Logic:**
[ Add details... ]

**Successor Activities and Logic:**
[ Add details... ]

---

## 3. Resource and Skill Requirements

**Required Team Roles and Headcount:**
[ Add details... ]

**Technical Skills and Equipment Needed:**
[ Add details... ]

---

## 4. Execution Constraints and Imposed Dates

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

**Activity Assumptions and Location Constraints:**
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Planner / Scheduler** | {{Scheduler_Name}} | _______________________ | [ .... - .... - .... ] |
| **Technical Lead** | {{Technical_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 ATTRIBUTES | <strong>Ref:</strong> PMO-04.03.03 <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 Attributes

Document Reference: PMO-04.03.03

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

1. What?

A comprehensive data sheet capturing technical parameters, logical dependencies, and resource assignments for scheduled activities.

2. Why?

Provides the precise technical data necessary for accurate critical path calculation and schedule modeling.

3. When?

Elaborated during activity sequencing and resource estimating within schedule planning.

4. Who?

Created by Project Scheduler with input from Lead Engineers and Task Owners.

Tailoring Tips

Capture story points, dependencies, and assignees directly in agile sprint tracking tools.
Maintain exhaustive attribute documentation for safety-critical path activities in infrastructure projects.

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

Activity Code and Title: Unique identifier code and full descriptive title of the schedule activity.
Activity Description and Scope Summary: Detailed technical narrative of the specific scope executed under this activity.
Assigned Work Package Reference: Corresponding parent WBS code and deliverable component mapping.
Predecessor Activities and Logic: List of preceding activities with dependency relationships (FS, SS, FF, SF) and lead/lag times.
Successor Activities and Logic: List of succeeding activities dependent upon the completion or start of this activity.
Required Team Roles and Headcount: Specific staffing roles, technical disciplines, and quantity of resources required.
Technical Skills and Equipment Needed: Specialized skill sets, machinery, software licenses, or facilities required for performance.
Imposed Start and Finish Dates: Contractual or management-mandated fixed start/finish constraint dates.
Activity Assumptions and Location Constraints: Critical assumptions regarding execution conditions, performance location, and physical constraints.

6. Reference Example

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

📖 Completed Example: 04_03_03_Activity_Attributes_Example.md

LLM Generation Prompt & Agent Instructions

Activity Attributes - Generation Prompt

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

Context and Definition: An artifact detailing the multiple descriptive components associated with each schedule activity, including predecessor/successor relationships, resource requirements, and constraints.

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)