---

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 Baselines: Scope (PMO-04.02.05), Schedule (PMO-04.03.08), Cost (PMO-04.04.04)
  • Work Performance Data & Logs (PMO-05.01 – PMO-05.15)
• Optional / Contextual:
  • Risk Register (PMO-04.08.02)
  • Statement of Work (PMO-04.09.04)

2. Downstream Dependents

• Mandatory:
  • Change Request (PMO-05.03)
  • Project or 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