Task 19: Plan and Manage Budget and Resources
Budget and resources are the twin engines of project execution. Without money, nothing gets built. Without people and materials, the money is useless. ECO Task 19 in the Process domain addresses the full discipline of financial and resource stewardship: from estimating what you need, through anticipating what might go wrong, to actively monitoring variations and working with governance structures to keep the project on track.
The PMP exam tests budget and resource management heavily — not just through formula-based earned value questions, but through situational scenarios that require you to recognize when a budget is drifting, what corrective action to take, and how to work within organizational governance frameworks. This guide covers all of it.
ECO Enablers for Task 19
The PMP Exam Content Outline defines four enablers that structure this task. Each represents a distinct competency the PMP exam will test:
- Estimate budgetary needs based on the scope of the project and lessons learned from past projects. Estimation isn't guesswork — it should be grounded in the project's scope baseline and informed by historical data from similar projects. PMI expects you to use multiple estimation techniques and document your assumptions.
- Anticipate future budget challenges. A good PM doesn't just react to overruns — they identify risks that could affect the budget before they materialize. This enabler ties directly to risk management and contingency planning.
- Monitor budget variations and work with the governance process to adjust as necessary. Once the budget baseline is set, you must track actual spending against it, analyze variances, and — when changes are needed — follow the organization's formal change control and governance processes.
- Plan and manage resources. Beyond money, this covers people, equipment, facilities, and materials. Resource planning includes capacity planning, resource leveling and smoothing, and managing resource constraints throughout the project lifecycle.
These enablers span both the predictive planning mindset (detailed upfront estimates, formal baselines) and the agile mindset (rolling-wave estimation, capacity-based sprint planning). The exam will test your ability to apply the right approach based on the methodology described in the scenario.
Estimating Budgetary Needs
Budget estimation follows a progression from rough to refined. PMI defines several estimation techniques, each appropriate at different stages of project definition. Understanding when to use each is critical for the exam:
| Technique | Accuracy | When Used | Key Characteristics |
|---|---|---|---|
| Analogous Estimation | Rough (-25% to +75%) | Early initiation, limited information available | Uses actual costs from similar past projects, scaled for size/complexity. Fast but imprecise — relies on expert judgment to identify truly comparable projects. |
| Parametric Estimation | Moderate (-10% to +25%) | When you have unit cost data and measurable parameters | Uses statistical relationships between historical data and variables (e.g., cost per square foot, cost per line of code). Requires reliable historical models. |
| Bottom-Up Estimation | Fine (-5% to +10%) | Detailed planning, when WBS is well-defined | Estimates each work package or activity individually, then rolls up. Most accurate but most time-consuming. The gold standard for cost baselines. |
| Three-Point Estimation | Moderate to Fine | When uncertainty is significant and you want risk-adjusted estimates | Uses optimistic (O), pessimistic (P), and most likely (M) estimates. Triangular: (O+M+P)/3. Beta/PERT: (O+4M+P)/6. Incorporates risk directly into the estimate. |
Whenever a PMP exam question asks about improving future estimates or dealing with uncertain costs, the answer almost always references lessons learned from past projects or historical data. PMI places enormous value on organizational process assets (OPAs). A PM who estimates based on gut feeling instead of historical data is answering incorrectly on the exam. Look for answer choices that reference the lessons learned register, organizational process assets, or historical information from previous similar projects.
The Cost Baseline and Reserves
Understanding the structure of a project budget is essential. The PMP exam will test your ability to distinguish between different components of the budget and — critically — who controls each one:
- Cost Baseline: The approved, time-phased budget against which project performance is measured. It includes the work package cost estimates plus contingency reserves. This is what the project manager uses for earned value calculations and is the primary tool for monitoring budget variations.
- Contingency Reserve: Funds set aside for "known unknowns" — risks that have been identified in the risk register. The project manager controls the contingency reserve and can authorize its use without sponsor approval. This is included in the cost baseline.
- Management Reserve: Funds for "unknown unknowns" — unforeseen work that is within the project scope but wasn't anticipated. The sponsor or senior management controls the management reserve. Using it requires a formal change request. Management reserve is NOT included in the cost baseline.
- Project Budget: The sum of the cost baseline plus the management reserve. This is the total authorized funding for the project.
A common exam trap: if a scenario describes an identified risk materializing, the correct source of funding is the contingency reserve, not the management reserve. If the scenario describes something completely unforeseen, management reserve — via a change request — is the answer.
Monitoring Budget Variations with Earned Value Management
Earned Value Management (EVM) is the most heavily tested quantitative topic on the PMP exam. It provides objective, data-driven answers to three fundamental questions: Are we on budget? Are we on schedule? Where are we headed? The core EVM metrics you must memorize:
| Metric | Formula | What It Tells You | Interpretation |
|---|---|---|---|
| CV (Cost Variance) | EV − AC | Are we over or under budget? | Positive = under budget. Negative = over budget. Zero = on budget. |
| SV (Schedule Variance) | EV − PV | Are we ahead or behind schedule? | Positive = ahead. Negative = behind. Zero = on schedule. |
| CPI (Cost Performance Index) | EV / AC | Cost efficiency — how many dollars of value per dollar spent? | CPI > 1.0 = under budget (efficient). CPI < 1.0 = over budget. CPI = 1.0 = on budget. |
| SPI (Schedule Performance Index) | EV / PV | Schedule efficiency — how fast are we progressing? | SPI > 1.0 = ahead. SPI < 1.0 = behind. SPI = 1.0 = on schedule. |
| EAC (Estimate at Completion) | BAC / CPI (typical) | What will the project actually cost at completion? | There are multiple EAC formulas. BAC/CPI assumes future performance mirrors past performance — the most common exam scenario. |
| ETC (Estimate to Complete) | EAC − AC | How much more will it cost to finish? | What remains to be spent. Used for replanning and forecasting. |
| TCPI (To-Complete Performance Index) | (BAC − EV) / (BAC − AC) | What efficiency is needed to hit the original budget? | TCPI > 1.0 = must perform better than planned. TCPI < 1.0 = can ease up. Used for recovery planning. |
| VAC (Variance at Completion) | BAC − EAC | At completion, how far off budget will we be? | Positive = under budget. Negative = over budget. |
Many PMP candidates mix up CPI and SPI. Remember: CPI = EV/AC (cost), SPI = EV/PV (schedule). The numerators are the same — EV. The denominator tells you what you're comparing against: AC for cost, PV for schedule. A trick: the word "Cost" and "Actual" both start with vowels, so CV uses AC. "Schedule" and "Planned" both start with consonants, so SV uses PV.
Anticipating Future Budget Challenges
Budget challenges rarely arrive unannounced — there are almost always early warning signs if you're paying attention. PMI expects project managers to proactively identify and address budget risks through several mechanisms:
Reserve Analysis: Regularly compare remaining contingency reserves against remaining risks. If your risk profile has changed — some risks retired, new ones identified — your reserve levels may need adjustment. The exam will test whether you update reserves proactively or wait until you run out.
Trend Analysis: Track CPI and SPI trends over time, not just point-in-time values. A CPI that started at 1.2 and has steadily dropped to 1.02 is a warning sign even though you're still under budget. The direction matters as much as the current value.
Cost of Quality: Understand the trade-offs between prevention costs (training, quality planning), appraisal costs (testing, inspection), and failure costs (rework, warranty claims, lost business). The exam favors investing in prevention — it's always cheaper than fixing problems later.
Working with Governance
When a budget variation is significant enough to require action, the project manager must work within the organization's governance framework. This means understanding the change control process: document the variance, analyze the impact (on scope, schedule, quality, and risk — not just cost), propose corrective or preventive actions, and submit the change request through the formal change control board (CCB).
PMI is clear: the project manager does NOT unilaterally approve budget changes that affect the baseline. Only the CCB or sponsor has that authority. The PM's role is to identify the need, analyze the options, make a recommendation, and — once approved — implement the change and update the project management plan and project documents accordingly.
Planning and Managing Resources
Resource management goes hand-in-hand with budget management — people and equipment cost money, and inefficient resource use drives budget overruns. Key resource planning concepts tested on the exam include resource leveling (adjusting the schedule so resource demand stays within available supply, which may extend the critical path), resource smoothing (adjusting activities within their float so resource demand is evened out without changing the critical path), and the RACI chart (Responsible, Accountable, Consulted, Informed) for clarifying who does what.
In agile environments, resource management shifts to capacity-based planning. Teams commit to a sustainable pace, velocity is tracked sprint over sprint, and the Product Owner prioritizes the backlog to maximize value within the team's capacity. The concept of "story points" replaces hours-based estimation, and team velocity provides the empirical data for forecasting.
Study Checklist for Task 19
- ✅ Can you name and describe all four estimation techniques and when each is appropriate?
- ✅ Do you understand the difference between contingency reserve (PM controls) and management reserve (sponsor controls)?
- ✅ Can you calculate CV, SV, CPI, SPI, EAC, ETC, TCPI, and VAC from given values and interpret the results?
- ✅ Do you know the formal process for requesting and approving budget changes through governance?
- ✅ Can you distinguish between resource leveling (may change critical path) and resource smoothing (uses float only)?
- ✅ Are you able to recognize early warning signs of budget drift and select the correct proactive response on situational exam questions?
Budget and resource management is the most quantitatively rigorous task in the Process domain. The earned value formulas alone account for a significant number of exam questions, and the situational scenarios around reserves, governance, and resource constraints appear throughout the test. Continue to Task 20: Plan and Manage Schedule to complete the Process domain with schedule mastery.
← Back to ECO Study Guide Index | Practice Process Domain Questions →