Estimate Costs
Introduction: Why This Matters
Projects live or die by their budgets. If costs are underestimated, overruns, delays, and stakeholder dissatisfaction are almost guaranteed. If costs are significantly overestimated, the project may never get approved. The Estimate Costs process ensures that all project activities and resources are realistically costed so that you can build a sound and defensible budget.
On the PMP exam, cost estimation is often tested through situational questions about estimation techniques or calculation based questions involving parametric or three point estimates. In real projects, accurate cost estimation improves financial predictability, supports decision making, and builds credibility with sponsors (Project Management Institute, 2021).
Purpose and Objectives
Primary Purpose: To develop an approximation of the monetary resources required to complete project activities.
Key Objectives:
- Estimate costs of resources such as labor, materials, equipment, and facilities.
- Include indirect costs such as overhead, insurance, and administrative expenses.
- Account for risks through appropriate reserves.
- Provide a documented basis of estimates to justify the numbers.
- Supply cost estimates as input to Determine Budget.
Overview
Estimate Costs converts the defined scope, schedule, and resource requirements into monetary values, producing cost estimates and a clear basis of how those estimates were developed.
- Inputs: Cost management plan, quality management plan, scope baseline, project schedule, risk register, resource requirements, enterprise environmental factors, and organizational process assets.
- Tools and Techniques: Expert judgment, analogous, parametric, bottom up and three point estimating, reserve analysis, cost of quality, project management software, and vendor bid analysis.
- Outputs: Activity and work package cost estimates, the basis of estimates, and updates to project documents such as the risk register and activity cost details.
Characteristics
- Multi technique: Uses several estimating approaches so you can balance speed, accuracy, and data availability.
- Scope anchored: Relies heavily on the scope baseline and schedule so that costs align with defined work and timing.
- Risk aware: Integrates reserve analysis and risk register insights to reflect uncertainty.
- Evidence based: Emphasizes a strong basis of estimates so that numbers are defensible and auditable.
Estimation Techniques Explained
Analogous estimating
- Uses historical cost data from similar projects.
- Faster and less detailed, typically around plus or minus 25 percent accuracy.
- Example: A similar data center upgrade cost $1 million. You estimate $1 million for this upgrade, adjusted for scale and complexity.
Parametric estimating
- Uses statistical relationships between historical data and variables such as units built.
- More accurate when the underlying data and model are reliable.
- Example: $500 per server multiplied by 200 servers equals $100,000.
Bottom up estimating
- Estimates individual components or subtasks at the work package level.
- Rolls up detailed estimates into totals for activities and control accounts.
- Most accurate technique, but also the most time intensive.
- Example: Cost each material item, labor hour, and subtask, then aggregate the values to get the total estimate.
Three point estimating
- Uses three values: Optimistic (O), Most Likely (M), and Pessimistic (P).
- Expected cost using PERT type formula: (O + 4M + P) divided by 6.
- Example: O = $8,000, M = $10,000, P = $14,000. Expected cost = (8 + 40 + 14) ÷ 6 = $10.33 thousand.
Reserve analysis
- Adds contingency reserves to address identified risks.
- May also include management reserves for unknown unknowns that sit outside the cost baseline.
Practical Example
Context: A company is relocating to a new headquarters.
Estimations:
- Analogous: A past relocation for 200 staff cost $400,000. For 250 staff, the project manager approximates $500,000.
- Parametric: $2,000 per employee multiplied by 250 employees equals $500,000.
Bottom up example:
- Moving services: $100,000
- IT setup: $150,000
- Furniture and fixtures: $200,000
- Contingency: $50,000
Total estimated cost: $500,000
- Three point: IT setup has estimates of $120,000 (optimistic), $150,000 (most likely), and $200,000 (pessimistic). Expected cost = (120 + 600 + 200) ÷ 6 = $153,333 approximately.
Outcome: The project manager integrates the results from different techniques and documents all assumptions, data sources, and constraints in the basis of estimates.
Common Pitfalls
Skipping basis of estimates
- Pitfall: Cost figures exist without any explanation of how they were derived.
- Prevention: Document assumptions, estimation methods, data sources, ranges, and the level of confidence for each estimate.
Forgetting indirect costs
- Pitfall: Only direct activity costs are considered.
- Prevention: Include overhead, compliance, utilities, administrative support, training, and other indirect costs.
Overconfidence in optimistic estimates
- Pitfall: Estimates assume everything will go according to plan.
- Prevention: Use three point estimates and contingency reserves to account for realistic levels of uncertainty.
Ignoring risk impacts
- Pitfall: No buffer is built in for known risks.
- Prevention: Integrate outputs from the risk register into reserve analysis and cost estimates.
Sensei Tip : On exam questions, never throw out a cost number without asking, in your mind, “What is the basis of this estimate?” The PMP tends to reward answers that include documented assumptions, data sources, and techniques.
Exam Alert : If a question ignores indirect costs or reserves and asks why estimates are repeatedly exceeded, the best answer usually points to incomplete estimating. Look for options that mention indirect costs, risk based reserves, or improving the basis of estimates.
Exam Lens
Patterns on the PMP Exam:
- Distinguish between analogous (fast, less accurate) and bottom up (detailed, most accurate) methods.
- Expect math questions involving three point estimates and parametric calculations.
- Know the difference between contingency reserves inside the baseline for identified risks and management reserves that sit outside the cost baseline for unknown unknowns.
Sample Question
Question: A project manager estimates software development costs using a rate of $50 per function point. For 2,000 function points, what is the estimated cost?
- $50,000
- $100,000
- $150,000
- $200,000
Correct Answer: B. Calculation: 50 × 2,000 = $100,000.
Quick Recap Table
| Technique | Description | Exam Watch Point |
|---|---|---|
| Analogous | Uses historical comparison at a high level. | Fast, less accurate, useful early in planning. |
| Parametric | Uses statistical relationships such as cost per unit or cost per function point. | Requires reliable data and a valid model to be accurate. |
| Bottom up | Builds estimates from detailed components and rolls them up. | Most accurate, but also the most time intensive to perform. |
| Three point (PERT) | Uses optimistic, most likely, and pessimistic values in a weighted average. | Expect calculation questions using (O + 4M + P) ÷ 6. |
| Reserve analysis | Adds buffers to account for risk and uncertainty in cost estimates. | Distinguish contingency reserves (baseline) from management reserves (outside baseline). |
Key Takeaways
- Estimate Costs produces cost estimates at both the activity and work package level.
- The main outputs are cost estimates and a clear basis of estimates.
- Core techniques include analogous, parametric, bottom up, and three point estimating, supported by reserve analysis.
- Reserves account for uncertainty and help protect the project from cost overruns.
- On the PMP exam, expect both calculation questions and scenarios that test which estimation method is most appropriate.
Next Step
With costs estimated, the next process is Determine Budget, where you aggregate cost estimates to establish the cost baseline and funding requirements for the project.
Bibliography
Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.
