PMO-05.07 Phase 05: Executing

LESSONS LEARNED REGISTER

سجل الدروس المستفادة

tasleemat asset PMO-05.07 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 05: Executing

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

Template Markdown (Bilingual)

<!-- LLM INSTRUCTIONS: Populate the Lessons Learned Register based on the project context. Note: This log must output an array of objects matching the flat table headers. -->

<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">LESSONS LEARNED REGISTER</h1>

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

---

## Lessons Learned Entries

| ID | Category | Trigger | Lesson | Responsible Party | Identifier/Submitter | Next Implementation Opportunity & Date | Organizational Impact (Y/N) | 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... ] |

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Knowledge / PMO Lead** | {{PMO_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Team Member / Contributor** | {{Contributor_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> LESSONS LEARNED REGISTER | <strong>Ref:</strong> PMO-05.07 <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: Lessons Learned Register

Document Reference: PMO-05.07

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

1. What?

A centralized repository capturing successes, mistakes, and improvement insights across all project phases.

2. Why?

Prevents repeating costly errors, institutionalizes best practices, and improves organizational capability.

3. When?

Initiated early and updated continuously at milestones, phase gates, and project retrospectives.

4. Who?

Maintained by the Project Manager with active contributions from all project team members and stakeholders.

Tailoring Tips

Conduct structured retrospective discussions at the end of each iteration or milestone.
Transfer high-impact lessons to the central PMO knowledge repository at project closing.

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 Lessons Learned Register, 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 lesson learned (e.g., LLR-01).
Category: Knowledge area or project phase (e.g., Technical, Procurement, Schedule).
Trigger: The triggering event, root cause, or situation encountered.
Lesson: Detailed description of what worked well or what should be done differently.
Responsible Party: Person or role assigned to document or disseminate the lesson.
Identifier/Submitter: Name or team identifying the lesson.
Next Implementation Opportunity & Date: Future milestone, project, or date where this lesson will be applied.
Organizational Impact (Y/N): Whether this lesson impacts enterprise processes, standards, or assets.
Comments: Additional reflections, training recommendations, or references.

6. Reference Example

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

📖 Completed Example: 05_07_Lessons_Learned_Register_Example.md

LLM Generation Prompt & Agent Instructions

Lessons Learned Register - Generation Prompt

System Instructions: This document contains instructions for generating the «Lessons Learned Register». 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 used to record knowledge gained during a project so that it can be used for the benefit of current and future projects.

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)