---

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 (PMO-04.02.05), Schedule (PMO-04.03.08), Cost (PMO-04.04.04)
• Optional / Contextual:
  • Risk Register (PMO-04.08.02)
  • Stakeholder Engagement Plan (PMO-04.10.01)

2. Downstream Dependents

• Mandatory:
  • Project Status Report (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