Cost and Time Management in Project Management

Learning Objectives

• Explain why cost and time management are inseparable disciplines in project delivery
• Apply the three main cost estimation methods (bottom-up, top-down, parametric) to realistic scenarios
• Calculate and interpret Earned Value Management (EVM) metrics including CPI and SPI
• Compare CPM, PERT, Gantt charts, and the Critical Chain Method as time management tools
• Describe four budgeting strategies: contingency planning, cash flow management, value engineering, and EVM
• Analyze how risk assessment and mitigation directly affect cost and schedule outcomes
• Extract practical lessons from the Sydney Opera House, International Space Station, and London 2012 Olympics case studies

Quick Answer

Cost and time management are the two most visible constraints on any project — they determine whether stakeholders declare success or failure. Cost management involves estimating, budgeting, and controlling all financial aspects of the project; time management involves sequencing activities and ensuring delivery on schedule. The two are tightly linked: schedule compression usually costs more, and budget cuts often extend timelines. Tools like Earned Value Management (EVM), Critical Path Method (CPM), and contingency budgeting give project managers the quantitative discipline to detect problems early and respond before they become crises.

Introduction to Cost and Time Management

Cost and time management are two crucial aspects of project management that work hand-in-hand. Effective cost management ensures that projects are completed within budget constraints, while efficient time management helps deliver results on schedule.

Why is Cost and Time Management Important?

• Ensures project feasibility — a project that cannot be afforded or cannot be delivered on time should not be started
• Maximizes value delivery — resources spent on one project cannot be spent elsewhere; discipline ensures maximum return
• Minimizes risks — most project risks ultimately manifest as cost overruns or schedule delays
• Improves overall project success rate — PMI research shows that organizations with mature cost and schedule management practices waste 13 times less money than those without

Cost Management Principles

Cost management involves planning, controlling, and reporting on all financial aspects of a project.

Estimating Costs

Accurate estimates are the foundation of cost management. Three primary methods:

1. Bottom-up Estimation Work from the lowest level of the WBS upward. Estimate the cost of each work package individually, then aggregate to get the total project cost. This is the most accurate method but also the most time-consuming. Best used when you have detailed scope and experienced estimators.

2. Top-down Estimation Use historical data from similar projects to estimate the total cost, then allocate it down to phases and tasks. Faster but less precise. Best used early in the project lifecycle when detailed scope is not yet available.

3. Parametric Estimation Use statistical relationships between variables — for example, cost per square foot for construction, or cost per function point for software. This method is fast and objective but requires high-quality historical data and assumes the new project is similar enough to past projects to make the relationship valid.

Method	Accuracy	Speed	Best Used When
Bottom-up	High	Slow	Detailed scope is known
Top-down (analogous)	Low to medium	Fast	Early phases, rough order of magnitude
Parametric	Medium to high	Fast	Good historical data exists

Cost Baseline

The cost baseline is the approved, time-phased budget for the project — the benchmark against which actual spending is measured. It is established at the end of the Planning phase and formally approved by the sponsor. Any approved change to the budget requires an update to the cost baseline through the change control process.

Why it matters: Without a baseline, you cannot measure variance. If you budgeted $100,000 and spent $110,000, the baseline tells you whether you are on track or over budget. Without it, you only know what you spent — not whether that is a problem.

Cost Variance

Cost Variance (CV) measures the difference between the value of work accomplished and the actual cost of accomplishing it:

CV = Earned Value (EV) − Actual Cost (AC)

• Positive CV: The project is under budget (good)
• Negative CV: The project is over budget (requires corrective action)
• Zero CV: The project is exactly on budget

The Cost Performance Index (CPI = EV / AC) expresses this as a ratio:

• CPI = 1.00: perfectly on budget
• CPI < 1.00: over budget (less than $1 of value for every $1 spent)
• CPI > 1.00: under budget

Sensitivity Analysis

Sensitivity analysis examines how changes in input variables (labor costs, material prices, duration estimates) affect the overall project cost. It helps identify which cost drivers have the greatest impact on the budget, allowing the PM to focus risk management efforts where they matter most.

Methods include:

• What-if scenario analysis — manually testing alternative cost assumptions
• Tornado diagrams — ranking variables by their impact range
• Monte Carlo simulation — running thousands of probabilistic scenarios to generate a cost probability distribution

Time Management Techniques

Effective time management is critical for delivering projects on schedule.

Critical Path Method (CPM)

CPM is the backbone of project scheduling. It identifies the longest path through the network of project tasks — the critical path. Key concepts:

• Tasks on the critical path have zero float — any delay pushes the project end date back
• Non-critical tasks have positive float — they can slip without affecting the end date
• CPM uses single-point, deterministic duration estimates — best when durations are known from historical data

Example: A software release with tasks A (2 days) → B (5 days) → C (3 days) on the critical path has a minimum duration of 10 days. A parallel task D (4 days) has 6 days of float and is not critical.

Advantages: Simple to understand, widely used, supported by all major PM software Limitations: Does not handle duration uncertainty; ignores resource constraints

Program Evaluation and Review Technique (PERT)

PERT was developed by the US Navy for the Polaris missile program in the 1950s and remains valuable for projects with high duration uncertainty.

Three-point estimates:

• Optimistic (O): best-case duration
• Most Likely (M): most probable duration
• Pessimistic (P): worst-case duration

Expected Duration = (O + 4M + P) / 6

Standard Deviation = (P − O) / 6

PERT also supports probability calculations — for example, what is the probability that the project finishes within 20 days? This is valuable for US government contracts and defense programs that require probabilistic schedule commitments.

Comparison: CPM vs. PERT

Feature	CPM	PERT
Duration estimates	Single-point	Three-point (O, M, P)
Uncertainty handling	No	Yes
Probability output	No	Yes
Best for	Construction, manufacturing	R&D, defense, novel projects

Gantt Charts

Gantt charts remain the most widely used schedule communication tool. They show:

• Tasks on the vertical axis
• Time on the horizontal axis
• Task duration as horizontal bars
• Dependencies as arrows between bars
• Milestones as diamond symbols

Gantt charts are intuitive for sponsors and executives who need schedule visibility without reading a network diagram. They are the standard reporting format for most US project status reports.

Limitation: On complex projects with hundreds of tasks, Gantt charts become unwieldy. CPM networks or EVM dashboards are more appropriate.

Critical Chain Method

The Critical Chain Method (CCM), introduced by Eli Goldratt, extends CPM by explicitly addressing resource constraints and human behavior.

Key differences from CPM:

• Resource constraints are incorporated into the schedule — two critical path tasks cannot run in parallel if both need the same person
• Task buffers are removed from individual tasks and consolidated into project buffers at the end of the critical chain and feeding buffers where non-critical chains merge with the critical chain
• This combats Parkinson's Law (work expands to fill available time) and student syndrome (procrastination until the deadline)

Benefits for complex projects: More realistic schedules, better resource utilization, and built-in protection for the project end date through the buffer management system.

Budgeting Strategies

Contingency Planning

Contingency reserves are amounts added to the budget to cover identified risks that may or may not occur. The size of the contingency depends on the risk profile of the project — a pioneering technology project warrants a larger contingency than a routine office renovation.

How to allocate: Common approaches include a fixed percentage of the total budget (5–15%), expected monetary value of identified risks (probability × impact), or Monte Carlo simulation to determine the budget needed to achieve a given confidence level.

Cash Flow Management

Cash flow management ensures the project has sufficient funds at each point in time to pay for the work being performed. A project can be on budget overall yet still fail because money arrives too late to pay workers and vendors. Key practices:

• Align payment milestones in contracts with the project's spending curve
• Forecast monthly cash outflows and secure funding in advance
• Monitor accounts payable to avoid straining vendor relationships

Value Engineering

Value engineering (VE) is a systematic method for improving the value of a product or process by analyzing its functions. In project management, VE asks: can we achieve the same functional outcome at lower cost? It is not about cutting corners — it is about finding alternative approaches that deliver the required performance more efficiently.

Example: A company building a data center found that using a modular cooling system instead of a traditional centralized system reduced both upfront capital cost and ongoing operating cost while meeting the same performance requirements.

Earned Value Management (EVM)

EVM is the gold standard for integrated performance measurement. It combines scope, schedule, and cost into a single framework.

Core EVM Metrics:

Metric	Formula	Meaning
Planned Value (PV)	Budgeted cost of work scheduled	How much work should have been done?
Earned Value (EV)	Budgeted cost of work performed	How much work was actually accomplished?
Actual Cost (AC)	Actual cost of work performed	How much did the accomplished work cost?
Schedule Variance (SV)	EV − PV	Negative = behind schedule
Cost Variance (CV)	EV − AC	Negative = over budget
SPI	EV / PV	Less than 1 = behind schedule
CPI	EV / AC	Less than 1 = over budget
EAC	BAC / CPI	Estimated cost at completion (if current trend continues)

Interpretation rule: CPI and SPI above 1.0 are favorable; below 1.0 require investigation.

EVM in the US: The US federal government requires EVM for major defense and construction contracts under the guidelines of the National Defense Industrial Association (NDIA) and OMB Circular A-11. PMP-certified professionals are expected to be proficient in EVM.

Risk Assessment and Mitigation

Identifying and mitigating risks is crucial for protecting cost and schedule baselines.

Risk Identification

Techniques include brainstorming, expert interviews, historical data review, checklists, SWOT analysis, and the Delphi method (structured expert consensus). All identified risks are recorded in the Risk Register with a description, owner, probability, and impact.

Risk Assessment

Qualitative methods: Rate probability (High/Medium/Low) and impact on a scale, then plot on a probability-impact matrix to prioritize risks. Quick and useful for early-phase assessment.

Quantitative methods: Assign numeric probability and cost/schedule impact values. Calculate Expected Monetary Value (EMV = Probability × Impact). Use Monte Carlo simulation to model the combined effect of all risks on total cost or schedule.

Risk Prioritization

Prioritize risks by their EMV or by their position in the probability-impact matrix. Focus mitigation effort on high-probability, high-impact risks. Accept or monitor low-probability, low-impact risks.

Risk Response Strategies

Strategy	Description	Example
Avoidance	Eliminate the risk by changing the plan	Use a proven technology instead of an experimental one
Mitigation	Reduce probability or impact	Build a prototype to validate design before full production
Transfer	Shift risk to a third party	Purchase insurance; use fixed-price contracts
Acceptance	Acknowledge the risk and prepare a contingency response	Set aside a contingency reserve for material price fluctuations

Project Scheduling Methods

Critical Path Method (CPM)

See the detailed explanation in the Time Management Techniques section above. CPM is the foundation for all advanced scheduling methods.

Program Evaluation and Review Technique (PERT)

PERT extends CPM with probabilistic duration estimates. See the Time Management section above. Use PERT when durations are uncertain and the consequences of missing deadlines are severe (contracts, public events, regulatory deadlines).

Resource-Constrained Scheduling

Standard CPM assumes unlimited resources. In reality, the same person cannot work on two tasks simultaneously. Resource-constrained scheduling adds resource availability as a constraint, which often extends the critical path and the project duration.

Challenges: Resource conflicts can be hidden until execution begins. Addressing them in planning prevents mid-project crises. Solutions: Resource leveling (extending duration to eliminate over-allocation) and resource smoothing (redistributing work within float without extending duration).

Leveling Techniques

Resource Leveling: Adjusts start and finish dates based on resource availability. May extend the project duration. Used when resource over-allocation cannot be resolved any other way.

Resource Smoothing: Adjusts activities within their available float to reduce peak resource demand. Does not extend the project duration. Used when schedule is fixed and workload must be managed within that constraint.

Resource Allocation and Optimization

Resource Breakdown Structure (RBS)

The RBS organizes project resources hierarchically — by type (human, equipment, material), department, or location. It helps identify all resources needed before the schedule is built, preventing the common mistake of planning a schedule that requires resources that are not available.

Resource Allocation Strategies

• Critical Path Method: Assign the best resources to critical path tasks first, since delays on those tasks delay the whole project
• Least Cost Method: Where multiple resources can perform a task, assign the least expensive one that meets quality requirements
• Critical Chain Method: Assign resources to the critical chain (resource-constrained critical path) and protect it with buffers

Resource Leveling and Smoothing

See the Scheduling Methods section above. In practice, project managers use PM software (MS Project, Primavera P6) to run automatic leveling calculations, then review and manually adjust the results to reflect organizational priorities and individual preferences.

Resource Smoothing

Resource smoothing is preferred over leveling because it does not extend the project duration. It redistributes work on non-critical tasks within their available float so that the resource load is more even across the project timeline — reducing burnout risk and improving productivity.

Performance Monitoring and Control

Performance Metrics

Cost Performance Index (CPI = EV/AC): Indicates how efficiently the project is spending money. A CPI of 0.85 means the project is getting only 85 cents of value for every dollar spent.

Schedule Performance Index (SPI = EV/PV): Indicates how efficiently the project is using time. An SPI of 0.90 means the project is accomplishing only 90% of the planned work per unit time.

Earned Value Management (EVM): Combines both metrics into a unified performance picture. Used by the US federal government for all major contracts and expected on the PMP exam.

Status Reporting

Types of reports:

• Weekly status report: brief update on accomplishments, upcoming work, issues, and EVM metrics
• Monthly performance report: detailed variance analysis, forecast at completion, risk status update
• Exception report: triggered when variance exceeds thresholds (for example, CPI falls below 0.90)

Frequency: Weekly for most active projects; monthly for phases with lower activity. Reporting frequency should be defined in the Communications Management Plan.

Corrective Actions

When performance metrics signal a problem:

1. Investigate root cause — is the variance due to estimation error, scope change, or execution inefficiency?
2. Identify options — schedule compression (crashing or fast-tracking), scope reduction, resource addition
3. Evaluate impact on other constraints — compressing schedule usually increases cost
4. Get approval through change control if the corrective action alters the baseline
5. Update the project plan and communicate changes to stakeholders

Lessons Learned

Documenting lessons learned throughout the project (not just at closure) captures fresh insights before they are forgotten. Effective lessons learned include:

• What went wrong and why
• What warning signs were visible in advance
• What worked well and should be repeated
• Specific recommendations for future projects

US organizations with PMOs (Project Management Offices) maintain lessons learned databases accessible to all project managers — a significant competitive advantage in repeat project environments.

Case Studies and Examples

The Sydney Opera House

The Sydney Opera House (completed 1973) is the canonical example of cost and time management failure — and ultimately, hard-won success. Originally estimated at AUD $7 million with a four-year timeline, it was completed 10 years late and at a cost of AUD $102 million.

Cost management challenges: The decision to begin construction before the design was complete meant that the structural engineering had to be revised mid-build, adding enormous cost. This violates the fundamental PM principle of completing planning before execution.

Time management strategies: The project used phased delivery — the concert hall opened while other sections were still under construction — which allowed some value delivery even as the overall schedule slipped.

Lessons learned: Scope and design must be sufficiently defined before major construction begins. Incremental design changes during construction are exponentially more expensive than changes during planning. The "cone of uncertainty" — costs of change escalate dramatically as the project progresses — is well illustrated here.

The International Space Station

The International Space Station (ISS) represents one of the most complex scheduling achievements in history — a multinational, multi-decade project requiring the coordination of over 15 nations.

Complex scheduling requirements: Assembly required precise sequencing of more than 40 major components launched by different nations' rockets, each with its own schedule constraints. A delay in one country's component could ripple across the entire program.

Risk mitigation strategies: Modular design allowed sections to be built and tested independently. Redundant systems reduced the cost of a single component failure. Multi-year contingency reserves were built into each national budget.

Budget optimization techniques: The multinational structure allowed parallel development of components, compressing the overall schedule. Sharing technical expertise reduced individual national costs.

Lessons learned: For megaprojects, interface management (coordinating the work of many organizations) is as important as managing individual components. Clear contractual responsibilities and communication protocols prevent costly coordination failures.

The London Olympics 2012

The London 2012 Olympics was widely praised as a project management success — delivered on time and within the revised budget of £9.3 billion.

Multi-project coordination: Over 70 individual construction and service projects were managed under a single program structure. The Olympic Delivery Authority (ODA) functioned as a PMO, enforcing consistent standards, coordinating shared resources, and managing cross-project dependencies.

Resource allocation challenges: Peak construction simultaneously required thousands of workers across dozens of sites in London. The ODA used workforce planning software to forecast labor demand 18 months ahead, coordinating with labor unions and training programs to ensure supply.

Performance monitoring strategies: The ODA used EVM-based performance reporting across all sub-projects, with monthly executive dashboards showing CPI and SPI for each venue. Projects falling below CPI 0.90 triggered mandatory recovery plans reviewed by senior leadership.

Lessons learned: Clear governance (a single PMO with real authority), standardized reporting, and proactive resource planning — not just reactive firefighting — are the keys to delivering complex multi-project programs. The ODA's approach is now a reference model for major event delivery organizations globally.

---

By mastering these aspects of cost and time management, Business Administration students gain valuable insights into effective project management practices. Practical application is key — seek opportunities to apply these principles in real-world projects to reinforce your understanding. In the US, PMP certification validates mastery of these concepts and significantly enhances career prospects across industries.

Key Terms

Term	Definition	Related Concept
Cost Baseline	Approved time-phased budget used as a reference for measuring cost performance	EVM, Change Control
Earned Value (EV)	Budgeted cost of work actually performed at a point in time	EVM, CPI, CV
Planned Value (PV)	Budgeted cost of work scheduled to be done at a point in time	EVM, SPI, SV
Cost Performance Index (CPI)	EV divided by AC; measures cost efficiency (CPI < 1 means over budget)	EVM, Cost Variance
Schedule Performance Index (SPI)	EV divided by PV; measures schedule efficiency (SPI < 1 means behind schedule)	EVM, Schedule Variance
Critical Path	Longest sequence of dependent tasks; determines the minimum project duration	CPM, Float
Float (Slack)	Time a non-critical task can be delayed without pushing the project end date	CPM, Scheduling
Contingency Reserve	Budget set aside to cover identified risks that may or may not occur	Risk Management
Resource Leveling	Adjusting the schedule to resolve resource over-allocation, potentially extending duration	Resource Management
Value Engineering	Systematic method for achieving required project functions at lower cost	Cost Optimization
Monte Carlo Simulation	Probabilistic technique running thousands of scenarios to model cost or schedule risk	Risk Quantification
Critical Chain Method	Scheduling approach that accounts for resource constraints and protects the schedule with buffers	CPM, Theory of Constraints

Common Mistakes

Misconception: The project budget is fixed at initiation and should never change. Why it's wrong: Budgets are based on estimates, and estimates improve as the project progresses. Refusing to update the budget when scope changes are approved, when risk events occur, or when new information changes the estimate-to-complete results in the team managing against an inaccurate number — which defeats the purpose of budgeting entirely. Correct understanding: The cost baseline is the approved budget. Changes go through the change control process. When approved, the baseline is updated to reflect the new reality. The goal is an accurate, current baseline that reflects what the project actually costs to deliver — not an original estimate that no longer reflects scope or conditions.

---

Misconception: A CPI above 1.0 always means the project is in great shape and no action is needed. Why it's wrong: A high CPI can mask serious problems. The project might be under budget because planned work is not actually happening — the team skipped complex tasks and is completing only easy ones. The deferred work will surface later at full cost. CPI must be read alongside SPI and scope completion to get an accurate picture. Correct understanding: A healthy project has both CPI and SPI at or above 1.0 and is delivering the planned scope. If CPI is high but SPI is low, the project is under-spending because it is behind on work — a warning sign, not a success signal. Always interpret EVM metrics together, not in isolation.

---

Misconception: Risk management is a one-time activity done during Planning. Why it's wrong: New risks emerge throughout the project — a key vendor goes out of business, a regulatory change adds new requirements, a technical approach proves infeasible. A risk register that is not updated after Planning is useless because it does not reflect the project's current threat environment. Correct understanding: Risk management is continuous. The risk register should be reviewed at every status meeting. As identified risks expire (their time window passes without occurring), new risks are added. Risk response budgets should be adjusted as the risk profile changes. A PM who only identifies risks in month one and ignores them in month six is not managing risk — they are documenting it.

Comparison and Connections

Feature	CPM	PERT	Critical Chain Method	EVM
Primary purpose	Find the critical path	Schedule under uncertainty	Schedule with resource constraints and buffers	Measure cost and schedule performance
Duration estimates	Single-point	Three-point (O, M, P)	Single-point with buffers	Uses planned vs. actual cost
Handles resources	No	No	Yes (explicitly)	No
Handles uncertainty	No	Yes (probabilistic)	Yes (via buffers)	Indirectly (via variance)
Output	Critical path, float	Critical path, probabilities	Critical chain, buffer status	CPI, SPI, EAC, variance
Best for	Well-defined sequential projects	R&D, novel technology, defense	Complex multi-resource projects	Ongoing performance monitoring
US context	Construction, government contracts	Defense, NASA programs	Pharmaceutical, aerospace	Federal contracts (required by law)

Practice Questions

Recall

1. What are the three main cost estimation methods, and when is each most appropriate? Guidance: Bottom-up (most accurate, most time-consuming — use when detailed scope is known), top-down/analogous (fastest, least accurate — use early in the lifecycle for rough order of magnitude), and parametric (uses statistical relationships — use when good historical data exists and the new project is similar to past ones).

2. What do CPI and SPI measure in Earned Value Management, and what does a value below 1.0 indicate for each? Guidance: CPI = EV/AC measures cost efficiency. CPI < 1.0 means the project is over budget (less than one dollar of value for every dollar spent). SPI = EV/PV measures schedule efficiency. SPI < 1.0 means the project is behind schedule (less work accomplished than planned). Both are unitless ratios — the closer to 1.0, the better.

Understanding

3. Why does the Critical Chain Method add buffers at specific locations in the schedule rather than padding each individual task? Guidance: When every task has its own buffer, Parkinson's Law kicks in — work expands to fill the available time, so the buffer is consumed even when it is not needed. Student syndrome compounds this: people start work only when the deadline is near, using up the buffer in haste. By pooling all buffers into a project buffer and feeding buffers, CCM provides protection where it actually matters (the critical chain and its merging paths) while removing the temptation to waste individual task buffers.

4. How does sensitivity analysis help a project manager prioritize risk mitigation efforts? Guidance: Sensitivity analysis identifies which cost or schedule drivers have the greatest impact on the overall project. A tornado diagram, for example, ranks variables by their impact range — the widest bars are the most sensitive inputs. By focusing risk mitigation on the top two or three variables in the tornado diagram, the PM gets the highest reduction in overall project risk for the least mitigation effort. Spending equal time on all risks wastes resources on low-impact items.

Application

5. A project has BAC = $200,000, PV = $80,000, EV = $70,000, and AC = $85,000 at the mid-point review. Calculate CPI, SPI, CV, SV, and EAC. What is your assessment? Guidance: CV = EV − AC = 70,000 − 85,000 = −$15,000 (over budget). SV = EV − PV = 70,000 − 80,000 = −$10,000 (behind schedule). CPI = 70,000/85,000 = 0.82 (only 82 cents of value per dollar). SPI = 70,000/80,000 = 0.875 (87.5% of planned work done). EAC = BAC/CPI = 200,000/0.82 = $243,902 (project will overspend by nearly $44,000 if current efficiency continues). The project needs immediate intervention — both cost and schedule corrective action are required.

6. Using the London 2012 Olympics case, identify two specific cost and time management practices that contributed to successful delivery and explain why each was effective. Guidance: EVM-based reporting with CPI/SPI dashboards: this gave senior leadership an objective, quantitative early warning system — projects with CPI below 0.90 were flagged before they became crises. The single PMO structure: by centralizing governance, the ODA enforced consistent standards across 70+ sub-projects, preventing the coordination failures that plagued the Sydney Opera House. Both practices work because they impose discipline without micromanagement — they provide information (EVM) and authority (PMO) needed for timely decisions.

Analysis

7. The Sydney Opera House cost 14 times its original estimate and took more than twice as long. Using the cost and time management principles in this chapter, identify at least three root causes and explain how modern PM practice would prevent them. Guidance: Root cause 1: Construction began before design was complete — modern PM practice requires completing Planning (including detailed design) before major Execution begins. Root cause 2: No cost baseline — without an approved budget, there was no objective measure of variance, making overruns invisible until they were enormous. EVM requires a cost baseline. Root cause 3: No formal change control — each design revision was simply implemented without evaluating schedule and cost impact. Modern change control requires impact analysis and sponsor approval before any scope change is implemented.

8. A pharmaceutical company is developing a new drug with highly uncertain lab task durations. Should they use CPM or PERT for scheduling? Justify your answer and explain what additional technique you would recommend for the overall project budget. Guidance: PERT is appropriate because lab research has high duration uncertainty — optimistic, most likely, and pessimistic estimates can differ by orders of magnitude, which CPM cannot accommodate. PERT also supports probability calculations: "what is the probability of completing Phase I trials within 18 months?" — a question critical for go/no-go decisions. For the budget, Monte Carlo simulation is the recommended complement: it runs thousands of scenarios combining all the uncertain duration and cost inputs to produce a probability distribution of total project cost, allowing the company to set a contingency reserve with a defined confidence level (for example, 80% confidence of staying within $50M).

FAQ

Q1: How do US government contracts use EVM differently from private-sector projects? The US federal government mandates EVM for major acquisition programs through OMB Circular A-11 and the NDIA EVMS guidelines. Government EVM requires formal system surveillance, independent EAC calculations, and monthly Contract Performance Reports (CPRs). Thresholds are strict — CPI below 0.90 triggers a formal Estimate at Completion review. In the private sector, EVM is applied more flexibly. Teams may use simplified metrics (milestone completion, burn rate) rather than full EVM calculations. The PMP exam tests full EVM; real-world application depends on the organization's maturity.

Q2: What is the difference between a contingency reserve and a management reserve? A contingency reserve covers identified risks — specific risk events in the risk register that may or may not occur. It is part of the cost baseline and the PM can use it to respond to those identified risks without a change request. A management reserve covers unknown unknowns — risks not yet identified, truly unforeseen events. It is held above the cost baseline by senior management and requires a change request to access. Together they ensure the project can absorb both predictable and unpredictable surprises.

Q3: How does resource leveling affect the critical path? Resource leveling can create a new critical path. When tasks are delayed to resolve resource conflicts, some previously non-critical tasks may have their float consumed — they become critical. The PM must re-run CPM calculations after leveling to identify the updated critical path. In resource-constrained environments, the "critical path" after leveling may differ significantly from the original CPM critical path — which is precisely what the Critical Chain Method is designed to address.

Q4: If a project's CPI drops below 0.85, what are the realistic options for recovery? A CPI of 0.85 means the project is spending $1 for every 85 cents of value delivered. Recovery options include: (1) Scope reduction — remove lower-priority features to reduce remaining work, potentially bringing CPI above 1.0 on the remaining scope; (2) Resource addition — "crashing" the schedule by adding people or overtime to complete work faster, but this increases cost further in the short term; (3) Process improvement — identify why cost is running over (rework? scope changes? poor estimates?) and fix the underlying cause; (4) Reforecast — if the CPI reflects a fundamental estimation error rather than execution inefficiency, revise the cost baseline with sponsor approval and reset performance measurement. There is no painless option; all recoveries require trade-offs.

Q5: How does value engineering differ from simply cutting the project budget? Budget cuts reduce the money available without changing the required outputs — the team must do the same work with less. Value engineering changes the approach: it asks "is there a different way to achieve the same function at lower cost?" The output requirement stays the same; the method changes. For example, switching from a custom-built software module to an off-the-shelf solution delivers the same functionality at lower cost. Budget cutting impairs quality or reduces scope; value engineering maintains scope and quality while reducing cost. VE is proactive (done during planning) rather than reactive (done in response to overruns).

Quick Revision

• Cost management: estimate → baseline → control → report; deviations trigger corrective action
• Three estimation methods: bottom-up (accurate, slow), top-down (fast, rough), parametric (uses historical ratios)
• Cost Variance (CV) = EV − AC; Schedule Variance (SV) = EV − PV; negative values are bad
• CPI = EV/AC; SPI = EV/PV; values below 1.0 signal problems; EAC = BAC/CPI forecasts final cost
• CPM: single-point estimates, finds critical path and float; best for well-known, deterministic projects
• PERT: three-point estimates (O, M, P), Expected Duration = (O + 4M + P) / 6; best for uncertain durations
• Critical Chain Method: adds project buffers and feeding buffers; combats Parkinson's Law and student syndrome
• Four risk responses: Avoid, Mitigate, Transfer, Accept
• Resource leveling extends duration to resolve conflicts; resource smoothing works within float
• Contingency reserve = identified risks (in baseline); management reserve = unknown risks (above baseline)
• Sydney Opera House: started construction before design was complete — 14× cost overrun, 10-year delay
• London 2012: EVM dashboards and a central PMO drove on-time, on-budget delivery across 70+ sub-projects

Related Topics

Prerequisites

• Introduction to Project Management
• Project Lifecycle and Phases
• Project Planning and Scheduling
• Basic Statistics (for PERT and Monte Carlo)

Related Topics

• Risk Management in Projects
• Procurement Management
• Resource Management
• Quality Management
• Agile and Scrum Methodology

Next Topics

• Risk Management in Projects (quantitative risk analysis, Monte Carlo, and response planning)
• Quality Management in Projects
• Stakeholder and Communications Management
• Agile Project Management and PMI-ACP