Gap Analysis Report

تقرير تحليل الفجوات

tasleemat asset PMO-01.04 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 01: Business and Value Delivery

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

Template Markdown (Bilingual)

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

Context and Definition: A formal pre-project and value delivery document systematically comparing an organization's Current State (As-Is) with its Desired Target State (To-Be) to define capability discrepancies, risks, and bridge actions.

Section Instructions:
- Analysis Context: Provide comprehensive data for all fields.
- Gap Evaluation Matrix: Provide comprehensive data for all fields.
- Remediation Strategy: Provide comprehensive data for all fields.
-->

<h3 dir="ltr" align="right">{{Company_Name}}</h3>
<h2 dir="ltr" align="right">{{Product_or_Service_Name}} - {{Canvas_ID}}</h2>
<h1 dir="ltr" align="center">GAP ANALYSIS REPORT</h1>

| **Date Prepared:** {{Current_Date}} | **Product Strategist:** {{Product_Strategist_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |

---

## Analysis Context

**Analysis Objective and Scope:**
[ Add details... ]

**Current State Summary:**
[ Add details... ]

**Desired Target State:**
[ Add details... ]

---

## Gap Evaluation Matrix

**Functional and Process Gaps:**
[ Add details... ]

**Technical and Systems Gaps:**
[ Add details... ]

**People and Competency Gaps:**
[ Add details... ]

**Risk and Business Impact:**
[ Add details... ]

---

## Remediation Strategy

**Closure Initiative Description:**
[ Add details... ]

**Priority and Execution Feasibility:**
[ Add details... ]

**Assigned Owner and Target Date:**
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Lead Business Analyst** | {{Lead_BA_Name}} | _______________________ | [ .... - .... - .... ] |
| **Business Domain Owner** | {{Business_Owner_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Sponsor** | {{Project_Sponsor_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div dir="ltr" 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> GAP ANALYSIS REPORT | <strong>Ref:</strong> PMO-01.04 <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: Gap Analysis Report

Document Reference: PMO-01.04

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

1. What?

A formal Tasleemat-aligned project artifact known as the Gap Analysis Report. A formal pre-project and value delivery document systematically comparing an organization's Current State (As-Is) with its Desired Target State (To-Be) to define capability discrepancies, risks, and bridge actions.

2. Why?

Because without a structured gap analysis report, decisions risk ambiguity and lack objective backing.

3. When?

This artifact is prepared during project lifecycle activities and refreshed as required.

4. Who?

Responsibilities: Prepared by the designated project lead and approved by key governance authorities.

Tailoring Tips

Scale the depth of analysis to match project complexity and risk.
Ensure all key stakeholders are aligned before final sign-off.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Enterprise Strategic Plan
Optional / Contextual:
- Project Charter (PMO-03.01)

2. Downstream Dependents

Mandatory:
- Project Governance and Reporting Records

5. How?

Fill out each section carefully following the specific field guidance provided below:

Analysis Context

Analysis Objective and Scope: The strategic purpose and organizational business domain boundaries evaluated by this gap analysis.
Current State Summary: Executive summary of the baseline operating model, legacy systems, and existing operational capabilities.
Desired Target State: The envisioned future operating state, target business architecture, and required capability levels.

Gap Evaluation Matrix

Functional and Process Gaps: Specific discrepancies identified between current operational workflows and target process efficiency standards.
Technical and Systems Gaps: Deficiencies in current software infrastructure, data architecture, security tooling, and integration capabilities.
People and Competency Gaps: Human capital deficiencies, staffing shortages, and technical skill gaps required to sustain the target state.
Risk and Business Impact: The quantified operational risk, revenue exposure, and strategic impact of leaving identified gaps unaddressed.

Remediation Strategy

Closure Initiative Description: The specific project, enhancement sprint, or restructuring action designed to bridge the capability gap.
Priority and Execution Feasibility: The implementation urgency (Urgent/High/Medium/Low) and technical/financial execution feasibility rating.
Assigned Owner and Target Date: The accountable business lead and committed milestone target date for closing the capability gap.

6. Reference Example

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

📖 Completed Example: 01_04_Gap_Analysis_Report_Example.md

LLM Generation Prompt & Agent Instructions

GAP ANALYSIS REPORT - LLM GENERATION GUIDE

System Prompt / Instructions: This document serves as the detailed instruction set for generating the GAP ANALYSIS REPORT. When asked to populate this form, use the guidance provided for each section below to accurately generate the required content. Reference parameters.md for global project variables.

Context & Definition: A formal pre-project and value delivery document systematically comparing an organization's Current State (As-Is) with its Desired Target State (To-Be) to define capability discrepancies, risks, and bridge actions.

Alignment: This gap analysis report must be aligned with standard PMI PMBOK principles.

Analysis Context

Analysis Objective and Scope

Instruction: The strategic purpose and organizational business domain boundaries evaluated by this gap analysis.