Variance Analysis & Trend Analysis: A Complete Guide for PMP Exam Success
Why Variance Analysis and Trend Analysis Matter
In project management, no plan survives first contact with reality completely intact. Schedules slip, budgets overrun, scope creeps, and quality deviates. The question isn't whether variances will occur — it's how quickly you detect them, how deeply you understand them, and how effectively you respond. This is precisely where Variance Analysis and Trend Analysis become indispensable tools.
Within the PMBOK framework (including the evolving PMBOK 8 and its emphasis on process quality, monitoring, and closure), these two techniques serve as the backbone of project performance monitoring. They empower project managers to move from reactive firefighting to proactive, data-driven decision-making.
What is Variance Analysis?
Variance Analysis is the technique of comparing planned performance (the baseline) against actual performance to determine the magnitude of any deviation. It answers the fundamental question: "Where are we versus where we planned to be?"
Key types of variance analysis include:
• Schedule Variance (SV) = Earned Value (EV) – Planned Value (PV)
- SV > 0: Ahead of schedule
- SV = 0: On schedule
- SV < 0: Behind schedule
• Cost Variance (CV) = Earned Value (EV) – Actual Cost (AC)
- CV > 0: Under budget
- CV = 0: On budget
- CV < 0: Over budget
• Scope Variance: Comparison of deliverables completed versus deliverables planned
• Quality Variance: Deviation of measured quality metrics from quality standards or thresholds
• Resource Variance: Difference between planned resource utilization and actual usage
Variance analysis is a point-in-time assessment. It tells you the current state of deviation but does not, on its own, predict the future.
What is Trend Analysis?
Trend Analysis extends variance analysis by examining performance data over time to identify patterns, directions, and rates of change. It answers the question: "Based on our trajectory, where are we heading?"
While variance analysis gives you a snapshot, trend analysis gives you a movie — it reveals whether things are getting better, getting worse, or stabilizing.
Common trend analysis techniques include:
• Run Charts: Plotting data points over time to visually identify trends
• Control Charts: Monitoring process stability by plotting data against upper and lower control limits
• Earned Value Trend Lines: Tracking SPI (Schedule Performance Index) and CPI (Cost Performance Index) over multiple reporting periods
• Burndown/Burnup Charts: Common in agile environments, showing work remaining or completed over iterations
• Defect Trend Analysis: Tracking defect discovery rates over time to assess quality trends
• Regression Analysis: Using statistical methods to project future performance based on historical patterns
How Do They Work Together?
Variance analysis and trend analysis are complementary. Consider this scenario:
At the end of Month 3, your project shows a Cost Variance (CV) of -$50,000 (over budget). That's variance analysis.
Looking at CPI values over the past three months — 0.98 (Month 1), 0.94 (Month 2), 0.88 (Month 3) — you see a deteriorating trend. That's trend analysis.
Together, they tell you not just that you have a problem, but that the problem is accelerating. This combined insight drives more urgent and targeted corrective action.
The Process: How Variance and Trend Analysis Are Applied
1. Establish Baselines: Before you can measure variance, you need approved baselines — scope baseline, schedule baseline, cost baseline, and quality metrics.
2. Collect Performance Data: Gather actual performance information through work performance data (raw observations and measurements from project execution).
3. Calculate Variances: Compare actuals against baselines using the appropriate formulas or qualitative assessments.
4. Analyze Significance: Not all variances require action. Use thresholds (defined in the management plans) to determine which variances are significant enough to warrant response.
5. Identify Trends: Plot performance data across multiple time periods. Look for patterns — upward, downward, cyclical, or random.
6. Determine Root Causes: Use root cause analysis to understand why variances and negative trends are occurring.
7. Recommend Actions: Based on findings, recommend corrective actions (to bring future performance back in line), preventive actions (to avoid anticipated problems), or change requests.
8. Report and Communicate: Package findings into work performance reports for stakeholders, using visual tools like dashboards, S-curves, and trend charts.
9. Monitor Effectiveness: After implementing corrective actions, continue monitoring to verify the variance is closing and the trend is improving.
Where These Techniques Appear in PMBOK Processes
Variance and trend analysis are used across multiple knowledge areas and process groups, including:
• Control Schedule: Analyzing schedule variances and schedule trends
• Control Costs: Analyzing cost variances, CPI trends, and Estimate at Completion (EAC) projections
• Control Quality: Monitoring quality metrics, defect rates, and process stability
• Control Scope: Assessing scope deviations
• Monitor Risks: Evaluating whether risk responses are effective and whether risk exposure trends are improving
• Monitor and Control Project Work: Overall integrated performance assessment
In the PMBOK 8 context, with its emphasis on principles-based and adaptive approaches, these techniques remain essential regardless of whether you're in a predictive, agile, or hybrid environment. In agile, trend analysis often manifests through velocity trends, burndown charts, and cumulative flow diagrams.
Key Formulas and Indices to Know
• SV = EV – PV
• CV = EV – AC
• SPI = EV / PV (schedule efficiency; 1.0 = on track)
• CPI = EV / AC (cost efficiency; 1.0 = on track)
• VAC (Variance at Completion) = BAC – EAC
• EAC (Estimate at Completion) — multiple formulas depending on assumptions:
- EAC = BAC / CPI (if current CPI trend continues)
- EAC = AC + (BAC – EV) (if original estimates are still valid)
- EAC = AC + Bottom-up ETC (for re-estimation)
- EAC = AC + (BAC – EV) / (CPI × SPI) (considering both cost and schedule trends)
• TCPI (To-Complete Performance Index) = (BAC – EV) / (BAC – AC) or (BAC – EV) / (EAC – AC)
Practical Example
A project has a Budget at Completion (BAC) of $500,000. At the end of Month 6:
• PV = $250,000
• EV = $200,000
• AC = $240,000
Variance Analysis:
• SV = $200,000 – $250,000 = -$50,000 (behind schedule)
• CV = $200,000 – $240,000 = -$40,000 (over budget)
• SPI = $200,000 / $250,000 = 0.80 (only 80% schedule efficiency)
• CPI = $200,000 / $240,000 = 0.83 (only 83 cents of value for every dollar spent)
Trend Analysis:
If CPI over the last six months has been: 0.95, 0.92, 0.90, 0.88, 0.85, 0.83 — the trend is consistently declining. This suggests systemic issues, not a one-time anomaly.
EAC (assuming trend continues) = $500,000 / 0.83 = $602,410
VAC = $500,000 – $602,410 = -$102,410 (expected to be over budget by ~$102K)
This combined analysis provides the project manager and sponsor with clear, actionable intelligence.
Common Causes of Variance
• Inaccurate initial estimates
• Scope creep or gold plating
• Resource unavailability or skill gaps
• Technical complexity underestimated
• Vendor/supplier delays
• Requirement changes
• Environmental or organizational factors
• Risk events materializing
=========================================
Exam Tips: Answering Questions on Variance Analysis and Trend Analysis
=========================================
1. Know the Difference Between the Two
If a question asks about comparing planned versus actual at a specific point, it's variance analysis. If it asks about patterns over time or forecasting, it's trend analysis. Many exam questions test whether you can distinguish between these two concepts.
2. Memorize the Core EVM Formulas
SV, CV, SPI, CPI, EAC, VAC, and TCPI formulas are exam staples. Know them cold. Practice calculating them quickly. Pay attention to the sign of the result — positive is generally good, negative is generally bad (except for SV and CV near project end, where SV always approaches zero).
3. Understand What the Indices Mean, Not Just How to Calculate Them
The exam often presents scenario-based questions. A CPI of 0.85 means you're getting only 85 cents of value for every dollar spent. An SPI of 1.10 means you're progressing 10% faster than planned. Be ready to interpret, not just compute.
4. Know When to Use Which EAC Formula
The exam may describe a scenario and ask you to select the right EAC formula. Key decision factors:
- Past performance expected to continue? → EAC = BAC / CPI
- Past variances were atypical (one-time events)? → EAC = AC + (BAC – EV)
- Original estimates are fundamentally flawed? → EAC = AC + new bottom-up ETC
- Both schedule and cost performance affect future work? → EAC = AC + (BAC – EV) / (CPI × SPI)
5. Remember: Variance Analysis Leads to Action
On the exam, after identifying a variance, the next step is typically to analyze the cause and then determine corrective or preventive actions. The answer is almost never "do nothing" when a significant variance exists.
6. Trend Analysis Is Predictive
If an exam question asks about forecasting future performance, predicting project outcomes, or determining if a trend is improving or deteriorating, the answer involves trend analysis. Look for keywords like "over the last several periods," "trajectory," "forecasting," or "projecting."
7. Control Charts Are a Trend Analysis Tool
If a question mentions upper control limits, lower control limits, the Rule of Seven, or process stability, it's referencing control charts, which are a form of trend analysis within quality management. Remember: 7 consecutive points on one side of the mean indicate a non-random trend requiring investigation.
8. Don't Confuse Variance Analysis with Root Cause Analysis
Variance analysis identifies that a deviation exists and how much it is. Root cause analysis identifies why the deviation occurred. On the exam, if you've identified a variance, the typical next step is root cause analysis before implementing corrective actions.
9. In Agile Contexts, Think Burndown and Velocity
For questions set in agile or hybrid environments, trend analysis may appear as velocity trends across sprints or burndown chart analysis. A declining velocity trend may indicate team issues, technical debt, or unclear requirements. Apply the same analytical logic.
10. Watch for Threshold-Based Questions
Some questions describe variances within acceptable thresholds. In those cases, the correct answer may be to continue monitoring rather than take immediate corrective action. Always check whether the variance exceeds defined thresholds before selecting an action-oriented answer.
11. TCPI Is a Forward-Looking Indicator
TCPI tells you the cost performance you must achieve on remaining work to meet BAC or EAC. If TCPI is significantly greater than 1.0 (and especially greater than CPI), it may be unrealistic, signaling a need to revise the budget or re-baseline. The exam tests this understanding.
12. Integration Is Key
Remember that variance and trend analysis feed into Integrated Change Control. Significant variances may trigger change requests, which must go through the change control board. The exam loves questions that test whether you follow proper change management processes after identifying variances.
Summary
Variance analysis and trend analysis are foundational monitoring and controlling techniques that every project manager must master. Variance analysis provides a point-in-time comparison of actual versus planned performance. Trend analysis reveals patterns and trajectories over time, enabling forecasting and proactive management. Together, they form a powerful diagnostic and predictive toolkit that drives informed decision-making, corrective actions, and ultimately project success. For the PMP exam, focus on understanding the concepts, memorizing the formulas, interpreting results in context, and knowing the appropriate next steps when variances and trends are identified.
