Project Cost Management
Open in the Padhaiko app8.1 Cost and project cost management
In ICT projects, financial success is just as critical as technical delivery. Project Cost Management comprises the processes required to ensure that a project is completed within its approved budget. According to the PMBOK framework, it encompasses four primary processes: Plan Cost Management, Estimate Costs, Determine Budget, and Control Costs.
Cost and Project Cost Management
- Cost: A resource sacrificed or foregone to achieve a specific objective, or something given up in exchange. Costs are typically measured in monetary units (e.g., NPR or USD) expended for hardware, software licenses, cloud infrastructure, salaries, training, and vendor services.
- Project Cost Management: The systematic process of planning, estimating, budgeting, financing, funding, managing, and controlling costs so that the project delivers the agreed scope within the approved budget.
ICT project managers must distinguish among several fundamental cost categories:
| Cost Pair | Meaning and ICT Examples |
|---|---|
| Direct vs. Indirect Costs | Direct costs are directly attributable to the project (e.g., developer salaries, dedicated cloud servers, software licenses). Indirect costs (overhead) are shared across multiple projects (e.g., office electricity, HR, central IT security). |
| Fixed vs. Variable Costs | Fixed costs remain constant regardless of project output or duration (e.g., an annual enterprise IDE license). Variable costs scale with volume or usage (e.g., pay-as-you-go cloud compute hours, contractor hours). |
| Tangible vs. Intangible Costs | Tangible costs can be measured easily in monetary terms (hardware purchase). Intangible costs are real but hard to quantify directly (e.g., loss of customer goodwill from system downtime). |
| Sunk Cost | Money already spent in the past that cannot be recovered. Sunk costs should never influence future project continuation decisions; only future costs and benefits matter. |
| Life-Cycle Costing | Considers the total cost of ownership (TCO) across development, deployment, operation, maintenance, and retirement—not merely initial build cost. |
8.2 Cost estimates, types, process and accuracy; Enterprise environmental factors, organizational process assets, cost estimating tools
Cost estimation is the process of developing an approximation of the monetary resources needed to complete project activities. In ICT projects, labour (software engineers, testers, DevOps engineers) usually dominates total project cost, alongside infrastructure and licensing.
8.2.1 Types of Cost Estimates and Accuracy
As a project progresses through its life cycle, more scope details become clear and estimate uncertainty narrows. The three standard estimate types are:
| Estimate Type | When Performed | Accuracy Range | Primary Purpose |
|---|---|---|---|
| Rough Order of Magnitude (ROM) | Initiation / early concept phase | to (historically to ) | High-level screening and project selection decisions |
| Budgetary Estimate | Early planning phase | to | Allocating funds into organizational budgets |
| Definitive Estimate | Detailed planning / before execution | to | Establishing the cost baseline and procurement bids |
8.2.2 Cost Estimation Process, EEFs, and OPAs
The cost estimation process follows a structured sequence:
- Review the Cost Management Plan and Scope Baseline (WBS and WBS dictionary).
- Decompose work packages into measurable activities and identify required resources (people, hardware, cloud, tools).
- Apply appropriate estimating tools and techniques using historical benchmarks and market rates.
- Determine basis of estimates (assumptions, constraints, confidence level, and range of possible outcomes).
- Aggregate estimates and account for risk reserves.
Two organizational inputs heavily shape estimates:
- Enterprise Environmental Factors (EEFs): Factors outside the project team's immediate control that constrain or inform costs—market conditions, currency exchange rates, vendor pricing, cloud region tariffs, and published commercial cost databases.
- Organizational Process Assets (OPAs): Internal assets the organization owns—cost estimating policies, standardized templates, historical project cost records, and lessons learned from past ICT deployments.
8.2.3 Cost Estimating Tools and Techniques
Core Cost Estimating Techniques
- Analogous (Top-Down) Estimating: Uses the actual cost of a similar, previously completed project as the basis for estimating the current project, adjusted for scale and complexity. Fast and inexpensive, but less accurate.
- Parametric Estimating: Uses a statistical relationship between historical data and project variables (parameters) to compute cost—for example, cost per function point, cost per line of code, or cost per server node:
- Bottom-Up Estimating: Estimates the cost of individual work packages or activities at the lowest WBS level and rolls them up to obtain the total project cost. Most accurate, though time-consuming.
- Three-Point (PERT) Estimating: Captures uncertainty using three estimates—Optimistic (), Most Likely (), and Pessimistic (). Under the beta (PERT) distribution:
Under the triangular distribution, .
- Reserve Analysis & Cost of Quality (CoQ): Adds contingency reserves for identified risks and factors in prevention, appraisal, and failure costs (testing, code reviews, rework).
- Vendor Bid Analysis: Evaluates quotations or proposals submitted by external vendors for software modules, hardware, or SaaS subscriptions.
| Aspect | Top-Down (Analogous) | Bottom-Up Estimating |
|---|---|---|
| Basis | Historical cost of a similar past project | Detailed cost of every WBS work package or activity |
| Speed & Effort | Fast, low effort | Slow, high effort |
| Accuracy | Lower (suitable for ROM / early screening) | Highest (suitable for Definitive baseline) |
| Team Involvement | Senior managers / estimators | Functional leads and technical team members |
1
An ICT team is estimating the cost of developing a web portal with three components:
- Authentication Module: Three-point (PERT) estimate with Optimistic , Most Likely , and Pessimistic .
- API Integration: Parametric estimate of at .
- Cloud Infrastructure Setup: Vendor bid fixed at .
If the project requires a contingency reserve on the direct estimated cost, find: (a) the expected cost and standard deviation of the Authentication Module, (b) the total direct cost, and (c) the cost baseline including contingency reserve.
Expected Cost and Standard Deviation of Authentication Module: Using the PERT (beta) three-point formula with , , and :
Parametric Cost and Total Direct Cost:
Summing all three components:
Cost Baseline with Contingency Reserve:
- (a) Authentication Module: Expected cost , standard deviation .
- (b) Total Direct Cost: .
- (c) Cost Baseline: .
8.3 Cost budgeting, cost aggregation, deriving budget from activity cost
Project Cost Budgeting (Determine Budget) is the process of aggregating the estimated costs of individual activities or work packages to establish an authorized, time-phased cost baseline.
8.3.1 Cost Aggregation and Deriving Budget from Activity Cost
Cost aggregation rolls estimates up the Work Breakdown Structure (WBS) hierarchy:
Once activity costs are mapped onto the project schedule (start and finish dates), spending is distributed over time periods (weeks, months, or quarters) to produce the time-phased cost baseline, typically visualized as a cumulative S-curve (slow spending during initiation, steep spending during execution, tapering off during closure).
Cost Baseline vs. Project Budget
- Work Package Estimates: Sum of activity cost estimates plus activity-level contingency reserves.
- Control Accounts: Sum of work package estimates within each management control point.
- Cost Baseline (): Sum of all control accounts (and any project-level contingency reserves), distributed across time. Performance is measured against this baseline.
- Total Project Budget: Cost Baseline plus Management Reserves:
8.3.2 Funding Limit Reconciliation
Even when the total budget is approved, organizations enforce periodic spending caps (e.g., quarterly cash-flow limits). Funding limit reconciliation compares planned periodic expenditures against funding constraints and, if necessary, adjusts the project schedule (rescheduling non-critical activities) so expenditures stay within each period's funding ceiling.
2
A software upgrade project has four WBS work packages scheduled across three months. Activity costs (in USD) per month are shown below. A contingency reserve of of total work package costs and a management reserve of are authorized.
| Work Package | Month 1 | Month 2 | Month 3 |
|---|---|---|---|
| WP 1.1 Requirements & Design | |||
| WP 1.2 Core Coding | |||
| WP 1.3 Database Migration | |||
| WP 1.4 Testing & Cutover |
Derive: (a) the monthly planned expenditures and cumulative spending before reserves, (b) the Cost Baseline (), and (c) the Total Project Budget.
Monthly Planned Expenditures (Cost Aggregation):
- Month 1: (Cumulative: )
- Month 2: (Cumulative: )
- Month 3: (Cumulative: )
Deriving the Cost Baseline (): The contingency reserve is of the aggregated work package cost:
Deriving the Total Project Budget: Adding the management reserve () to the cost baseline:
- (a) Monthly Planned Costs: Month 1 , Month 2 , Month 3 (Total ).
- (b) Cost Baseline (): .
- (c) Total Project Budget: .
8.4 Cost control process, cost control methods
Control Costs is the process of monitoring the status of the project to update project costs and managing changes to the cost baseline. In ICT projects, scope creep, underestimated integration complexity, and cloud usage spikes make disciplined cost control essential.
8.4.1 Cost Control Process
Key activities in the cost control process include:
- Influencing change factors to ensure that only beneficial or approved changes affect the cost baseline.
- Monitoring cost performance continuously to detect variances from the authorized cost baseline.
- Recording actual expenditures accurately and comparing them against physical work accomplished (not merely money spent).
- Preventing unapproved changes from entering cost reports or resource charges.
- Communicating variances and corrective actions to stakeholders in a timely manner, and updating forecasts (, ).
8.4.2 Cost Control Methods
- Earned Value Management (EVM): Integrates scope, schedule, and cost baselines to evaluate project performance objectively and forecast final cost.
- Variance Analysis: Compares planned performance against actual results (, ) to identify root causes (e.g., vendor rate hikes, rework due to defects, or schedule slippage) and decide corrective measures.
- Forecasting: Uses current performance indices (, ) to project Estimate at Completion () and Estimate to Complete ().
- To-Complete Performance Index (TCPI): Measures the cost efficiency required on remaining work to stay within or .
- Performance Reviews & Trend Analysis: Tracks cost performance over consecutive reporting periods to detect whether performance is improving or deteriorating.
- Reserve Analysis: Monitors remaining contingency reserves against remaining project risks to verify whether reserves are adequate.
- Project Management Information Systems (PMIS): Software tools (e.g., MS Project, Jira with cost plugins, Primavera) that automate cost tracking, S-curves, and EVM dashboards.
8.5 Earned value management, EVM benefits, variance analysis
Earned Value Management (EVM) is a quantitative project management technique that integrates scope, schedule, and cost baselines into a single unified performance measurement framework. Rather than simply comparing budgeted spending vs. actual spending (which ignores how much work was actually finished), EVM evaluates the value of work genuinely completed.
8.5.1 Core EVM Metrics and Formulas
Core EVM Parameters, Variances, and Forecasts
Four Fundamental Values (at data date ):
- Planned Value ( / BCWS): The authorized budget assigned to scheduled work up to time .
- Earned Value ( / BCWP): The authorized budget value of work actually completed up to time ().
- Actual Cost ( / ACWP): The realized cost actually incurred in accomplishing the work up to time .
- Budget at Completion (): The total authorized cost baseline for the entire project.
Variances and Performance Indices:
- Cost Variance: ( under budget; over budget).
- Schedule Variance: ( ahead of schedule; behind schedule).
- Cost Performance Index: ( favourable; cost overrun).
- Schedule Performance Index: ( ahead/on schedule; behind schedule).
Forecasting Formulas:
- Estimate at Completion () — Typical variance (current continues):
- Estimate at Completion () — Atypical variance (remaining work at budgeted rate):
- Estimate at Completion () — Both and affect remaining work:
- Estimate to Complete ():
- Variance at Completion (): ( projected overrun)
- To-Complete Performance Index ():
| Metric | Favourable Condition | Unfavourable Condition | Meaning when Unfavourable |
|---|---|---|---|
| Spending more than the value of work done (cost overrun) | |||
| Completing less work than scheduled (behind schedule) | |||
| Getting less than of value per spent | |||
| Progressing at less than of planned pace | |||
| Remaining work must be done more efficiently than planned to meet |
8.5.2 Benefits of EVM and Variance Analysis
Key Benefits of EVM:
- Single Integrated View: Combines scope, time, and cost in one common monetary unit, preventing misleading "under-spend" reports that actually reflect delayed work.
- Objective Progress Tracking: Eliminates subjective "% complete" guesswork by tying earned value to verified deliverables.
- Early Warning Signal: Because and stabilize relatively early (often by completion), EVM alerts managers before minor variances become unrecoverable overruns.
- Reliable Cost Forecasting: Enables data-driven and projections for senior management funding decisions.
Variance Analysis in EVM: Variance analysis examines the magnitude, cause, and trend of and (or percentage variances and ). Project teams check variances against pre-defined control thresholds (e.g., ). When a threshold is breached, the manager performs root-cause analysis (e.g., scope ambiguity, staff turnover, faulty cost estimates) and initiates corrective or preventive actions such as crashing, fast-tracking, or resource reallocation.
3
An enterprise ERP implementation has a Budget at Completion scheduled over . At the end of Month 6, planned work is (), actual work completed is (), and actual cost incurred is . Calculate , , , , and assuming current cost performance is typical for the rest of the project, find , , , and . Interpret the project's status.
Cost and Schedule Variances ( and ):
Since both and , the project is over budget and behind schedule.
Performance Indices ( and ):
The project earns only of value per spent and progresses at of the planned rate.
Forecasting (, , , and ):
To still finish within the original budget, the team would need to achieve a of on all remaining work (up from ), which is unlikely without major corrective intervention.
, , , . Under typical cost performance, , , (projected overrun), and . The project is currently over budget and behind schedule.
Exercises
Practice Exercises — Project Cost Management
Differentiate between Rough Order of Magnitude (ROM), Budgetary, and Definitive cost estimates in terms of timing and accuracy range. Also explain how Enterprise Environmental Factors (EEFs) and Organizational Process Assets (OPAs) influence cost estimation.
Three Types of Cost Estimates:
- Rough Order of Magnitude (ROM): Prepared early during project initiation for screening decisions; accuracy range is to .
- Budgetary Estimate: Prepared during early planning to allocate organizational funds; accuracy range is to .
- Definitive Estimate: Prepared during detailed planning before execution to form the cost baseline; accuracy range is to .
Influence of EEFs and OPAs:
- EEFs (external/contextual): Market salary rates, vendor quotations, cloud pricing tariffs, currency exchange rates, and published commercial cost databases determine prevailing unit prices.
- OPAs (internal organizational): Historical project cost records, cost estimation templates, estimating policies, and lessons learned provide empirical benchmarks and standardized procedures.
ROM ( to ), Budgetary ( to ), and Definitive ( to ) estimates progress from early screening to baseline commitment as scope clarity improves. EEFs supply external market rates and commercial benchmarks, while OPAs supply internal templates, policies, and historical cost records.
Distinguish between Contingency Reserve and Management Reserve. Explain how a Cost Baseline and Total Project Budget are derived from activity cost estimates.
Contingency Reserve vs. Management Reserve:
- Contingency Reserve: Covers known-unknowns (identified risks), sits inside the cost baseline, and is controlled by the project manager.
- Management Reserve: Covers unknown-unknowns (unforeseen risks), sits outside the cost baseline, and requires sponsor or senior management approval.
Cost Aggregation Hierarchy: Activity cost estimates are summed into work package estimates, which are rolled up into control accounts. Adding contingency reserves forms the time-phased Cost Baseline (). Adding management reserves to the cost baseline yields the Total Project Budget.
Contingency reserves handle known-unknowns inside the cost baseline (PM authority), whereas management reserves handle unknown-unknowns outside the baseline (management authority). Activity estimates roll up through work packages and control accounts plus contingency reserves to yield the Cost Baseline, and adding management reserves produces the Total Project Budget.
A cybersecurity audit task has a three-point cost estimate of , , and . Using the PERT beta distribution, compute the expected cost and standard deviation .
Expected Cost ():
Standard Deviation ():
Expected cost and standard deviation .
At Month 4 of a cloud migration project with , you record , , and .
- Compute , , , and , and state whether the project is ahead/behind schedule and under/over budget.
- Calculate assuming (a) the current cost variance was a one-time atypical event, and (b) future performance depends on both and .
Variances and Indices:
Since () and (), the project is over budget but ahead of schedule.
Forecasting under Atypical vs. Combined () Assumptions:
- (a) Atypical variance (remaining work at planned rate):
- (b) Combined and effect:
- , , , (over budget, ahead of schedule).
- (a) Atypical ; (b) Combined .
A data-center upgrade has . Halfway through the schedule (), of the total project work has been completed and has been spent. Find , , (assuming typical cost performance), and . Explain why comparing only and would mislead management here.
Calculating and :
Calculating and :
Why Comparing Only and Is Misleading: Comparing to makes the project appear "exactly on budget." However, only of value () was actually earned, revealing both a cost overrun () and a schedule delay ().
, , , . Comparing only and falsely suggests the project is on track because it ignores that only (rather than ) of work was completed.