ISSUE LOG

سجل المشكلات

tasleemat asset PMO-05.01 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 05: Executing

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

Template Markdown (Bilingual)

<!-- LLM INSTRUCTIONS: Populate the Issue Log based on the project context. Ensure the JSON keys map exactly to the corresponding flat markdown fields.

Section-by-Section Instructions:
- Issue Log: Log all project issues including their type, source, priority (Urgent/High/Medium/Low), impacts, responsible party, status (Open/Closed), and resolution. -->

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

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

---

## Issue Log Entries

| ID | Type | Source of Issue | Issue Description | Priority | Impact on Objectives | Impacted Stakeholders | Responsible Party | Status | Resolution Date | Final Resolution | Comments |
| :---: | :--- | :--- | :--- | :---: | :--- | :--- | :--- | :---: | :---: | :--- | :--- |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Issue Owner / Contributor** | {{Issue_Owner_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **PMO Lead** | {{PMO_Lead_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> ISSUE LOG | <strong>Ref:</strong> PMO-05.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: Issue Log

Document Reference: PMO-05.01

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

1. What?

A centralized log documenting all emergent problems, conflicts, and obstacles affecting project execution.

2. Why?

Unresolved issues threaten project deadlines, budget baselines, and quality standards if not systematically addressed.

3. When?

Activated at project kickoff and updated continuously throughout executing and monitoring phases.

4. Who?

Managed by the Project Manager with active collaboration from team leads, contributors, and impacted stakeholders.

Tailoring Tips

Escalate blocking issues immediately to the Sponsor or Change Control Board.
Assign single-point accountability for resolving each logged issue.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Project Management Plan (PMO-04.01.01)
- Approved Baselines (Scope/Schedule/Cost)
Optional / Contextual:
- Risk Register (PMO-04.08.02)
- Stakeholder Engagement Plan (PMO-04.10.01)

2. Downstream Dependents

Mandatory:
- Project Status Reports (PMO-06.01)
- Change Log (PMO-05.04)
- Lessons Learned Summary (PMO-07.01)
Optional / Contextual:
- Variance Analysis (PMO-06.04)
- Decision Log (PMO-05.02)

5. How?

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

ID: Unique identifier for the issue (e.g., ISS-01).
Type: Type or classification of the issue (e.g., Technical, Resource, Schedule).
Source of Issue: Origin or root trigger of the issue (e.g., Vendor delay, Requirement change).
Issue Description: Detailed explanation of the issue and current condition.
Priority: Urgency or priority level (e.g., Urgent, High, Medium, Low).
Impact on Objectives: Potential or realized impact on scope, schedule, cost, or quality.
Impacted Stakeholders: Stakeholders or user groups affected by this issue.
Responsible Party: The person or role assigned to resolve or track the issue.
Status: Current status of the issue (e.g., Open, In Progress, Resolved, Closed).
Resolution Date: Target or actual date by which the issue was resolved.
Final Resolution: Summary of the corrective action taken to resolve the issue.
Comments: Additional notes, context, or escalation details.

6. Reference Example

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

📖 Completed Example: 05_01_Issue_Log_Example.md

LLM Generation Prompt & Agent Instructions

Issue Log - Generation Prompt

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

Context and Definition: A project document where all issues recorded during project execution are tracked, analyzed, and managed until resolution.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Project Management Plan (PMO-04.01.01), Approved Baselines (Scope/Schedule/Cost) * Optional: Risk Register (PMO-04.08.02), Stakeholder Engagement Plan (PMO-04.10.01) * Downstream Dependents: * Mandatory: Project Status Reports (PMO-06.01), Change Log (PMO-05.04), Lessons Learned Summary (PMO-07.01) * Optional: Variance Analysis (PMO-06.04), Decision Log (PMO-05.02)