PMP Cost Management: Budgeting, EVM & Exam Questions

Cost is the knowledge area that sponsors care about most and that I, as a project manager, have to defend most often. Every estimate is a forecast under uncertainty, and every budget is a promise that future-me has to keep. When I first prepared for the PMP, pmp cost management felt like a maze of acronyms and formulas. With time I realised it is actually one of the most logical knowledge areas, anchored in just four processes and a handful of techniques.

In this guide I want to walk you through cost management as I now teach it to my own teams. We will cover the four processes, the four primary estimating techniques, funding limit reconciliation, the S-curve, and the highlights of earned value management (EVM). For the EVM deep dive, I will point you to a dedicated resource with worked examples.

By the end you should be able to plan, estimate, budget, and control costs in a way that survives both the PMP exam and a sceptical sponsor. Let us get into it.

Cost Management is the set of processes that ensures the project is completed within the approved budget. It covers planning how cost will be managed, estimating activity costs, determining the budget, and controlling costs throughout the project.

The knowledge area has three planning processes and one monitoring and controlling process. Like schedule management, there are no executing processes - actual spending happens via Direct and Manage Project Work in Integration.

I think of cost management as the financial conscience of the project. It is what turns aspiration into accountability.

Four processes, four obligations: plan how, estimate what, set the baseline, control the variance.

This process defines how costs will be planned, structured, and controlled. The output is the cost management plan, a subsidiary of the project management plan.

The cost management plan addresses:

• Units of measure (rupees, hours, days)
• Level of precision and accuracy
• Organisational procedure links (chart of accounts, WBS link)
• Control thresholds (e.g., 10% CV variance triggers escalation)
• Rules of performance measurement (EVM rules: 50/50, 0/100, weighted milestone)
• Reporting formats and frequency
• Additional details (funding strategy, currency considerations, inflation handling)

A few hours invested here saves dozens of arguments later.

Estimate Costs develops an approximation of the monetary resources needed to complete project activities. The output is cost estimates and the basis of estimates document.

Tools include expert judgement, analogous, parametric, bottom-up, three-point, data analysis (alternatives analysis, reserve analysis, cost of quality), PMIS, decision making (voting), and group decision making.

The basis of estimates is often skipped by candidates. Do not skip it. It documents how each estimate was derived, the confidence interval, and the assumptions. Auditors and PMI both love it.

Cost estimates include direct costs (labour, materials, equipment) and indirect costs (overhead, administration) where applicable.

Determine Budget aggregates the estimated costs of individual activities or work packages to establish an authorised cost baseline. Key outputs:

• Cost baseline - time-phased budget excluding management reserves
• Project funding requirements - total and periodic funding needs (cost baseline plus management reserves)

The cost baseline is the approved version against which performance is measured. Changes only via Integrated Change Control.

The S-curve emerges naturally when you plot cumulative cost over time during Determine Budget. We will look at the S-curve in section 8.

Control Costs monitors project status, manages changes to the cost baseline, and prevents unauthorised changes. Tools include data analysis (earned value analysis, variance analysis, trend analysis, reserve analysis), to-complete performance index (TCPI), and PMIS.

Outputs include work performance information, cost forecasts, change requests, and updates to plans and documents.

Cost variances flow into change requests; change requests flow into Integrated Change Control.

The four primary techniques you must know cold for the PMP exam.

Analogous estimating uses historical data from similar projects. Fast, cheap, less accurate. Best in early phases when little detail is known.

Example: "Our last warehouse fit-out cost 80 lakh INR. This one is similar size; estimate 80 lakh INR."

Parametric estimating uses a statistical relationship between variables. More accurate when historical data is reliable.

Example: "Software development typically costs 30,000 INR per function point. The project has 250 function points. Estimate = 250 x 30,000 = 75 lakh INR."

Bottom-up estimating sums detailed estimates of components. Most accurate, most time-consuming.

Example: Decompose each WBS work package into activities, estimate each, sum to get the total.

Three-point estimating uses optimistic (O), most likely (M), pessimistic (P) values.

• Triangular: (O+M+P)/3
• PERT/Beta: (O+4M+P)/6
• Standard deviation: (P-O)/6

Example: O=10 lakh, M=15 lakh, P=30 lakh.

• Triangular: (10+15+30)/3 = 18.3 lakh
• PERT: (10+60+30)/6 = 16.7 lakh
• SD: (30-10)/6 = 3.3 lakh

When activity costs are aggregated to work packages, work packages to control accounts, and control accounts to the project, you get the cost baseline. Plotted over time, the cumulative cost baseline forms an S-curve: slow ramp-up, steep middle, gradual tail.

The S-curve is useful for:

• Visualising planned spend over time
• Comparing actual cumulative cost (AC) to planned value (PV) and earned value (EV)
• Spotting trends early
• Communicating with sponsors and finance partners

I always produce an S-curve as part of the project management plan. It becomes the canonical visual in steering committee meetings.

Funding is often released in tranches rather than upfront. Funding limit reconciliation compares planned cost flow (from the cost baseline) to funding availability. Mismatches mean activities must be rescheduled or budgets adjusted.

Example. Cost baseline shows 50 lakh INR needed in Q2, but funding releases only 35 lakh in Q2. Options:

• Defer non-critical activities to Q3
• Negotiate accelerated funding release
• Re-baseline with stakeholder approval

The exam may test whether you recognise that funding constraints can drive schedule changes.

EVM integrates scope, schedule, and cost into a single performance system. The core variables:

• PV (Planned Value) - budgeted cost of work scheduled
• EV (Earned Value) - budgeted cost of work performed
• AC (Actual Cost) - actual cost incurred for work performed
• BAC (Budget at Completion) - total budget for the project

Variances:

• CV (Cost Variance) = EV - AC. Positive is good (under budget).
• SV (Schedule Variance) = EV - PV. Positive is good (ahead of schedule).

Performance indices:

• CPI (Cost Performance Index) = EV / AC. >1 is good.
• SPI (Schedule Performance Index) = EV / PV. >1 is good.

Quick worked example. BAC = 1 crore INR. PV at month 6 = 50 lakh. EV at month 6 = 45 lakh. AC at month 6 = 55 lakh.

• CV = 45 - 55 = -10 lakh (over budget)
• SV = 45 - 50 = -5 lakh (behind schedule)
• CPI = 45/55 = 0.82 (each rupee delivers 82 paise of value)
• SPI = 45/50 = 0.90 (90% of planned progress)

For a deeper dive with multiple worked scenarios, see Techademy's dedicated PMP Earned Value Examples article.

Once you have EVM data, you can forecast.

EAC (Estimate at Completion) - the forecast total project cost. Four common formulas:

1. EAC = AC + Bottom-up ETC (when original estimate is no longer valid)
2. EAC = BAC / CPI (when current variance is typical)
3. EAC = AC + (BAC - EV) (when remaining work will be performed at planned rate)
4. EAC = AC + ((BAC - EV) / (CPI x SPI)) (when both schedule and cost variances must continue)

ETC (Estimate to Complete) = EAC - AC.

VAC (Variance at Completion) = BAC - EAC. Positive is good (will finish under budget).

TCPI (To-Complete Performance Index) - the CPI required to complete the project within a target.

• TCPI based on BAC = (BAC - EV) / (BAC - AC)
• TCPI based on EAC = (BAC - EV) / (EAC - AC)

If TCPI > 1.0, the team must perform better than originally planned to meet the target.

Two types of reserves the exam loves to test.

Contingency reserves - allocated for identified risks ("known unknowns"). Part of the cost baseline. PM can authorise use.

Management reserves - allocated for unidentified risks ("unknown unknowns"). NOT part of the cost baseline. Senior management authorises use, typically via change request.

Cost baseline + management reserve = project budget.

The exam often tests whether you remember that management reserves are not in the baseline.

Q1. Which estimating technique is most accurate but most time-consuming?

A. Analogous
B. Parametric
C. Bottom-up
D. Expert judgement

Answer: C.

Q2. PV = 80 lakh, EV = 60 lakh, AC = 70 lakh. What is CPI?

A. 0.75
B. 0.86
C. 1.14
D. 1.33

Answer: B. CPI = EV/AC = 60/70 = 0.857.

Q3. Management reserves are:

A. Part of the cost baseline
B. Not part of the cost baseline, but part of the project budget
C. Approved by the PM
D. Used for known risks

Answer: B.

Q4. EAC if current variance is typical:

A. BAC / CPI
B. AC + (BAC - EV)
C. AC + BAC
D. BAC - AC

Answer: A.

Q5. The S-curve typically shows:

A. Activity dependencies
B. Cumulative cost over time
C. Risk probability over time
D. Resource utilisation

Answer: B.

Q6. SV = -50,000 INR means the project is:

A. Ahead of schedule
B. Under budget
C. Behind schedule
D. Over budget

Answer: C. Negative SV = behind schedule.

Q7. Contingency reserves are used for:

A. Unknown unknowns
B. Known unknowns
C. Sponsor changes
D. Out-of-scope work

Answer: B.

Q8. A project has BAC = 1 crore, EV = 30 lakh, AC = 35 lakh. TCPI based on BAC?

A. 0.86
B. 1.08
C. 1.20
D. 1.33

Answer: B. TCPI = (1 crore - 30 lakh) / (1 crore - 35 lakh) = 70/65 = 1.077.

Q9. Three-point PERT estimate with O=8, M=12, P=22:

A. 14
B. 13
C. 12
D. 11

Answer: B. PERT = (8 + 48 + 22)/6 = 78/6 = 13.

Q10. The cost baseline is updated:

A. By the PM at any time
B. Through Integrated Change Control
C. Monthly during status meetings
D. Only at the end of the project

Answer: B.

The traps I see candidates fall into most often.

• Confusing PV and BAC. PV is the budgeted value of work scheduled to a point in time. BAC is the total project budget.
• Forgetting management reserves are outside the baseline. Memorise this.
• CV and SV sign confusion. Negative = bad. Positive = good. Both for cost and schedule.
• Mixing up EAC formulas. Know when each applies; the question's wording is the clue.
• Reserve analysis interpretation. Reducing contingency as risks are retired is good practice, not "cutting corners".
• Funding limit reconciliation confused with cost aggregation. Aggregation is bottom-up totalling; reconciliation is matching the result to funding availability.
• Earned value rule confusion. 0/100 means 0% credit until complete; 50/50 means 50% credit at start, 50% at completion; weighted milestone splits credit across milestones.

Let me walk through three full mini-scenarios that combine multiple cost concepts. These mirror the multi-step questions you will see on the PMP exam.

Scenario A: The mid-project performance review. A nine-month project with BAC of 2 crore INR is at month four. Status: PV = 90 lakh, EV = 80 lakh, AC = 95 lakh.

Step 1 - calculate variances and indices: CV = 80 - 95 = -15 lakh (over budget). SV = 80 - 90 = -10 lakh (behind schedule). CPI = 80/95 = 0.84. SPI = 80/90 = 0.89.

Step 2 - calculate EAC assuming current CPI continues: EAC = BAC/CPI = 2 crore / 0.84 = 2.38 crore. That is 38 lakh over budget projected at completion.

Step 3 - calculate TCPI to meet original BAC: TCPI = (BAC - EV) / (BAC - AC) = (2 crore - 80 lakh) / (2 crore - 95 lakh) = 1.20 crore / 1.05 crore = 1.14. The team would need to perform at 1.14 CPI for the rest of the project to recover.

Step 4 - decision: at current trajectory the project will overrun by roughly 19%. A reasonable response is to escalate to the sponsor with three options: re-baseline the budget upward, reduce scope, or commit to a recovery plan with weekly TCPI tracking. The PMI-correct first action is to raise a change request and route through Integrated Change Control.

Scenario B: The reserve question. Sponsor asks why the budget includes a 15 lakh "contingency". The PM should explain that contingency reserves are allocated for identified risks documented in the risk register, that they are part of the cost baseline, and that the PM has authority to release them when triggered risks occur. The 15 lakh is not "padding" but a planned response to identified risks like "vendor delay" and "regulatory rework".

Scenario C: The estimate negotiation. A new sponsor asks for a "ballpark" before the team has done detailed estimating. The PM uses analogous estimating to provide a ROM (rough order of magnitude) estimate with -25% to +75% range, clearly labelled as preliminary. The PM commits to a refined estimate after the WBS is complete, expected in three weeks. This is the PMI-correct approach: never refuse to estimate, but always communicate the confidence level.

PMBOK 7 emphasises tailoring cost approaches to project context. A few tailoring questions I ask myself at every project start.

• Lifecycle. Predictive projects benefit from detailed upfront cost baseline. Adaptive projects often use rolling-wave budgeting with iteration-level cost tracking.
• Industry. Construction projects rely heavily on parametric estimating with industry benchmarks. Software projects often use story point velocity combined with cost-per-point metrics.
• Funding model. Capital expenditure projects need careful funding limit reconciliation. Operating expense projects may have more flexibility.
• Currency. Multi-currency projects require exchange rate assumptions, hedging strategies, and clear reporting currency choices.
• Inflation. Long-duration projects in volatile economies need inflation adjustments built into estimates and reserves.
• Earned value rules. Choose 0/100, 50/50, or weighted milestone based on activity nature. Short activities suit 0/100; longer activities suit 50/50 or weighted milestone.

Tailoring is not optional in PMBOK 7. The PMP exam tests whether you recognise when standard practice should be adjusted.