VARIANCE ANALYSIS

تحليل التباين

tasleemat asset PMO-06.04 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 06: Monitoring and Controlling

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

Template Markdown (Bilingual)

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

Section-by-Section Instructions:
- Variance Analysis Table: Document the planned results, actual results, calculated variance, root causes, and planned responses for Schedule, Cost, Quality, and Scope.
- Variance Implications and Escalation: Document implications of continued variance (forecasts/trends) and whether the variance needs escalation.
- Comments: Document any comments that add relevance to this report. -->

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

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

---

## 1. Variance Analysis Table

| Category | Planned Result | Actual Result | Variance | Root Cause | Planned Response |
| :--- | :--- | :--- | ---: | :--- | :--- |
| **Schedule** | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| **Cost** | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| **Quality** | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| **Scope** | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |

---

## 2. Variance Implications and Escalation

**Implications of continued variance (Forecast):**
[ Add details... ]

**Escalation Required (Y/N):**
[ Add details... ]

**Escalation Details:**
[ Add details... ]

---

## 3. Comments
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Cost & Schedule Controller** | {{Cost_Controller_Name}} | _______________________ | [ .... - .... - .... ] |
| **Finance Controller** | {{Finance_Controller_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> VARIANCE ANALYSIS | <strong>Ref:</strong> PMO-06.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: Variance Analysis

Document Reference: PMO-06.04

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

1. What?

A structured analysis report identifying variances, diagnosing root causes, and formulating corrective actions.

2. Why?

Enables timely diagnostic understanding of project deviations and provides defensible evidence for corrective actions.

3. When?

Conducted periodically or upon detecting threshold breaches during monitoring and controlling.

4. Who?

Prepared by the Project Manager with Project Controllers and reviewed by PMO and Governance committees.

Tailoring Tips

Set custom variance tolerance thresholds (e.g., +/- 5% cost or schedule) to trigger formal root-cause analysis.
Combine with Earned Value forecasting for capital-intensive infrastructure and engineering projects.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Approved Project Baselines (PMO-04.01.01)
- Work Performance Data & Logs (PMO-05.01 - 05.12)
Optional / Contextual:
- Risk Register (PMO-04.08.02)
- Vendor Agreements (PMO-04.09.04)

2. Downstream Dependents

Mandatory:
- Change Requests (PMO-05.03)
- Project / Phase Closeout (PMO-07.03)
- Lessons Learned Summary (PMO-07.01)
Optional / Contextual:
- Transition to Operations Checklist (PMO-07.04)
- Value Realization Register (PMO-01.03)

5. How?

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

Schedule / Planned Result: The target baseline schedule milestone, duration, or date.
Schedule / Actual Result: The actual completed milestone date, duration, or current progress.
Schedule / Variance: Calculated difference between actual schedule performance and the baseline.
Schedule / Root Cause: Primary cause and contributing factors for schedule variance.
Schedule / Planned Response: Action plan or recovery strategy designed to address schedule variance.
Cost / Planned Result: The approved baseline budget or planned expenditure for the period.
Cost / Actual Result: The actual expenditures or costs incurred during the period.
Cost / Variance: Calculated difference between actual expenditures and the cost baseline.
Cost / Root Cause: Primary drivers and events resulting in cost overruns or savings.
Cost / Planned Response: Corrective measures and cost containment actions to realign with budget.
Quality / Planned Result: The quality metric, acceptance threshold, or standard expected.
Quality / Actual Result: The actual measured quality outcome, defect rate, or test score.
Quality / Variance: Discrepancy between actual quality achievements and defined quality metrics.
Quality / Root Cause: Root cause analysis detailing why quality requirements were not met.
Quality / Planned Response: Remediation plan, rework procedures, or process improvements.
Scope / Planned Result: The authorized deliverables and work packages committed in the scope statement.
Scope / Actual Result: The actual scope deliverables completed and verified during the period.
Scope / Variance: Extent of scope variance, unapproved scope additions, or unfinished deliverables.
Scope / Root Cause: Factors causing scope variance, creep, or delayed deliverable completions.
Scope / Planned Response: Corrective actions, change requests, or realignment to baseline scope.
Implications of continued variance (Forecast): Anticipated long-term impact on overall project objectives if variances persist.
Escalation Required (Y/N): Clear indication (Yes/No) whether senior leadership escalation is necessary.
Escalation Details: Details of the specific escalation path, required decisions, and target stakeholders.
Comments: Additional explanatory notes, cross-functional dependencies, or contextual insights.

6. Reference Example

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

📖 Completed Example: 06_04_Variance_Analysis_Example.md

LLM Generation Prompt & Agent Instructions

Variance Analysis - Generation Prompt

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

Context and Definition: An analytical tool used to measure the differences between planned baselines and actual performance across schedule, cost, quality, and scope.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Approved Project Baselines (PMO-04.01.01), Work Performance Data & Logs (PMO-05.01 - 05.12) * Optional: Risk Register (PMO-04.08.02), Vendor Agreements (PMO-04.09.04) * Downstream Dependents: * Mandatory: Change Requests (PMO-05.03), Project / Phase Closeout (PMO-07.03), Lessons Learned Summary (PMO-07.01) * Optional: Transition to Operations Checklist (PMO-07.04), Value Realization Register (PMO-01.03)