Project Cost Management (PMBOK Knowledge Area 4) is the collection of processes that ensure a project is completed within the approved budget. It covers three core processes: Plan Cost Management (defining how costs will be estimated, budgeted and controlled), Estimate Costs (developing approximations of monetary resources needed), and Determine Budget (aggregating estimated costs into a cost baseline). A fourth process — Control Costs — monitors spending against the baseline using Earned Value Management (EVM) and takes corrective action when variances occur. Cost management is deeply interrelated with scope, schedule, risk, resource and procurement management — a change in any of these areas will almost always affect the project budget.
Of all the constraints a project manager navigates — scope, time, quality, risk — cost is the one that most visibly defines success or failure in the eyes of sponsors and business stakeholders. Projects that deliver their objectives within budget signal professional competence. Projects that overrun significantly — even when they deliver every requirement — are widely perceived as failures.
But project cost management is frequently misunderstood as a financial tracking exercise: track what was spent, compare to budget, report the variance. That is cost accounting, not cost management. True project cost management starts at planning, runs through every stage, and requires the PM to understand not just what has been spent but what value has been earned for that spend — a distinction that Earned Value Management makes analytically precise.
This guide covers all four PMBOK processes in depth, the complete EVM formula set with a worked example, how cost management changes in Agile and hybrid environments, and how cost management connects to every other PMBOK knowledge area.
The Four Processes
Project Cost Management — The 4 PMBOK Processes
PMBOK 6th and 7th editions define four processes within Project Cost Management. They are not sequential steps that each happen once — they are iterative activities that interact continuously throughout the project lifecycle. Click each process to expand the full detail.
7.1
Plan Cost Management
Planning Process Group · Defines how costs will be managed throughout the project
+
Plan Cost Management is the process of establishing the policies, procedures and documentation for planning, managing, expending and controlling project costs. Its primary output is the Cost Management Plan — a component of the overall Project Management Plan that guides all subsequent cost-related activities.
The Cost Management Plan defines: the units of measure for cost estimation (hours, days, pounds, dollars), the level of precision required in estimates (round to nearest £100, £1,000 etc.), the level of accuracy acceptable, the organisational procedures links (which account codes and WBS elements align to costs), the control thresholds that trigger corrective action (e.g. CPI below 0.9), the EVM rules to be used, the reporting formats and frequencies, and any additional funding requirements.
The inputs to this process are the Project Charter (which defines the pre-approved budget and financial constraints), the Project Management Plan (particularly the schedule and risk management plans), and Enterprise Environmental Factors (EEFs) such as market conditions, exchange rates, and the organisation's cost management infrastructure.
Inputs
Project Charter
Project Management Plan
Enterprise Environmental Factors
Organisational Process Assets
Tools & Techniques
Expert judgement
Data analysis (alternatives analysis)
Meetings
Outputs
Cost Management Plan
7.2
Estimate Costs
Planning Process Group · Develops an approximation of costs for project activities
+
Estimate Costs is the process of developing an approximation of the monetary resources needed to complete project work. Cost estimates are predictions based on the information available at the time — they are not guarantees. The accuracy of estimates improves as more project information becomes available, which is captured in the Cone of Uncertainty: early estimates (at project initiation) carry ±50% accuracy, while later estimates (as work begins) may reach ±10%.
Key estimation techniques include:
Analogous estimating: Uses historical data from similar past projects. Quick and low-cost but less accurate. Best used in early phases when detailed information is not available.
Parametric estimating: Uses statistical relationships between historical data and other variables (cost per square metre, cost per function point, cost per line of code). More accurate than analogous if the parameters are reliable and the relationship is scalable.
Bottom-up estimating: Estimates individual work packages at the most granular level and aggregates upward. Most accurate but most time-consuming. Best used when the WBS is well-defined.
Three-point estimating (PERT): Calculates a weighted average from Optimistic (O), Most Likely (M) and Pessimistic (P) estimates. Triangular: (O + M + P) / 3. Beta/PERT: (O + 4M + P) / 6. Produces a more realistic estimate by accounting for uncertainty.
Reserve analysis: Identifies contingency reserves (for known unknowns) and management reserves (for unknown unknowns). Contingency reserves are included in the cost baseline; management reserves are held above it and require specific authorisation to use.
Cost of quality: Estimates the cost of conformance (prevention and appraisal) vs non-conformance (internal and external failure). Investing in quality activities now typically costs less than fixing defects later.
Planning Process Group · Aggregates estimated costs to establish the cost baseline
+
Determine Budget is the process of aggregating the estimated costs of individual activities or work packages to establish an authorised cost baseline. The cost baseline is the time-phased project budget — it shows not just the total approved budget but how much is expected to be spent at each point in time. This time-phasing is essential for Earned Value Management: without knowing what should have been spent by a given date (the Planned Value), it is impossible to assess whether the project is ahead or behind on cost performance.
The key outputs are the Cost Baseline (the authorised, time-phased budget excluding management reserves — this is the "S-curve") and the Project Funding Requirements (total funding needed, which includes the cost baseline plus management reserves). The cost baseline is the primary reference against which cost performance is measured throughout the project.
The structure of total project budget: Work Package Estimates → Contingency Reserves (added by PM, for known risks) = Cost Baseline. Cost Baseline → Management Reserves (added by sponsor/steering group, for unknown risks) = Project Budget. This structure is a common PMP exam distinction.
Inputs
Cost Management Plan
Scope Baseline
Cost Estimates
Basis of Estimates
Project Schedule
Risk Register
Resource Calendars
Agreements (contracts)
OPAs
Tools & Techniques
Expert judgement
Cost aggregation
Data analysis (reserve analysis)
Historical information review
Funding limit reconciliation
Financing
Outputs
Cost Baseline (S-curve)
Project Funding Requirements
Project Documents Updates
7.4
Control Costs
Monitoring & Controlling Process Group · Monitors project status to update costs and manage changes
+
Control Costs is the process of monitoring the status of the project to update project costs and managing changes to the cost baseline. It is the only cost management process that occurs during the Monitoring and Controlling process group — it runs continuously from project initiation through project close. Its primary tool is Earned Value Management (EVM), which provides an objective, data-driven assessment of project cost and schedule performance at any point in time.
Control Costs has two distinct responsibilities that are often conflated: monitoring actual costs against the baseline (cost accounting) and managing changes to the baseline (cost control). A PM who only does the first is reporting — not controlling. True cost control means taking corrective action when variances exceed thresholds, implementing preventive measures before variances occur, and managing the change control process when the baseline itself needs to change.
To-Complete Performance Index (TCPI) is one of the most powerful Control Costs tools: it calculates the efficiency rate that must be achieved for the remaining work to meet the project's financial objective. TCPI > 1.0 means the remaining work must be done more efficiently than has been achieved so far — a TCPI above 1.1 is generally considered unrealistic to achieve without significant intervention.
Inputs
Project Management Plan (Cost Baseline, Cost Management Plan)
Project Funding Requirements
Work Performance Data
OPAs
Tools & Techniques
Earned Value Management
Data analysis (variance analysis, trend analysis, reserve analysis)
To-Complete Performance Index (TCPI)
PM software
Outputs
Work Performance Information
Cost Forecasts (EAC)
Change Requests
Project Management Plan Updates
Project Documents Updates
Earned Value Management
The Complete EVM Formula Set
Earned Value Management is the analytical engine of project cost control. It integrates scope, schedule and cost to provide objective performance measurement. Every EVM calculation starts from three foundational values — PV, EV and AC — from which all other metrics are derived.
Complete EVM Reference — All Formulas for PMP and APM PMQ
PV
Planned Value (Budgeted Cost of Work Scheduled)
PV = % planned complete × BAC
The authorised budget assigned to scheduled work. What you planned to have done by this date.
EV
Earned Value (Budgeted Cost of Work Performed)
EV = % actual complete × BAC
The budget value of work actually completed. What you have earned for what you have done — regardless of what was spent.
AC
Actual Cost (Actual Cost of Work Performed)
AC = Total actual spend to date
The total cost incurred for work performed. What was actually spent. Comes from financial records, not estimation.
BAC
Budget at Completion
BAC = Total approved project budget
The total planned budget for the entire project (the cost baseline). The denominator in many EVM calculations.
CV
Cost Variance
CV = EV − AC
Positive CV = under budget. Negative CV = over budget. Measures cost efficiency of completed work.
SV
Schedule Variance
SV = EV − PV
Positive SV = ahead of schedule. Negative SV = behind schedule. Expressed in cost terms, not time units.
CPI
Cost Performance Index
CPI = EV ÷ AC
CPI > 1.0 = under budget (getting more value per £ spent). CPI < 1.0 = over budget. Most critical EVM metric for forecasting.
SPI
Schedule Performance Index
SPI = EV ÷ PV
SPI > 1.0 = ahead of schedule. SPI < 1.0 = behind schedule. Useful for trend analysis but loses predictive power near project end.
EAC
Estimate at Completion (most common)
EAC = BAC ÷ CPI
Forecasts total project cost assuming current CPI continues to project end. The most frequently used EAC formula on the PMP exam.
EAC
EAC (remaining work at planned rate)
EAC = AC + (BAC − EV)
Assumes all remaining work will be performed at the original planned rate (the past CPI is an anomaly). Used when early variances are not expected to continue.
EAC
EAC (new estimate for remaining work)
EAC = AC + ETC
Uses a fresh bottom-up estimate for remaining work (ETC). Most accurate but most resource-intensive. Used when original estimate is fundamentally flawed.
ETC
Estimate to Complete
ETC = EAC − AC
Expected cost to finish remaining project work from this point forward. "How much more do we need to spend?"
VAC
Variance at Completion
VAC = BAC − EAC
Expected budget surplus (positive) or overrun (negative) at project end. "By how much will we be over or under budget at the end?"
TCPI
To-Complete Performance Index
TCPI = (BAC − EV) ÷ (BAC − AC)
Cost efficiency needed for remaining work to meet BAC. TCPI > 1.0 means remaining work needs to be more efficient than past performance. Above 1.1 is generally unrealistic.
CPI > 1.0 AND SPI > 1.0
Under budget and ahead of schedule. Ideal state — investigate whether estimates were too conservative.
CPI < 1.0 AND SPI < 1.0
Over budget and behind schedule. Most critical state — requires immediate corrective action and likely sponsor escalation.
CPI < 1.0 but SPI > 1.0
Ahead of schedule but overspending. May indicate team is crashing tasks — investigate resource costs vs productivity.
Worked Example
EVM in Practice — A Worked Example
Scenario: IT Infrastructure Upgrade Project — Month 4 Status Review
CPIEV ÷ AC = £35K ÷ £42K0.83Getting £0.83 of value for every £1 spent
SPIEV ÷ PV = £35K ÷ £40K0.875Only completing 87.5% of planned work
EACBAC ÷ CPI = £100K ÷ 0.83£120,482Project will cost ~£120K if trend continues
VACBAC − EAC = £100K − £120,482−£20,482Expected overrun of ~£20K at completion
TCPI(BAC−EV) ÷ (BAC−AC) = £65K ÷ £58K1.12Remaining work needs 12% more efficiency than achieved — very challenging
What this tells the PM: The project is behind schedule and overspending. At the current performance rate, it will overrun by approximately £20,000. The TCPI of 1.12 indicates that completing within the original budget is unrealistic without significant process improvements or scope reduction. The PM should present these findings to the project board, request a formal change to the cost baseline, and implement corrective actions to improve the CPI — likely involving root cause analysis of where costs are being lost.
Interrelation to Other Knowledge Areas
How Cost Management Connects to Every Other Knowledge Area
Project cost management does not exist in isolation. Every other knowledge area either provides inputs to cost management, receives outputs from it, or is directly affected by cost changes. Understanding these connections is critical for integrated project management — and for the PMP exam, which frequently tests how changes in one knowledge area ripple through others.
🔗KA01 — Integration Management
Integration Management is the overarching framework within which cost management operates. The Project Management Plan includes the Cost Management Plan and Cost Baseline as subsidiary components. All changes to the cost baseline must go through the integrated change control process — a change request cannot increase the budget without integration management's approval mechanism. Direct the and Manage Project Work generates the actual cost data (Work Performance Data) that Control Costs analyses. When EVM identifies a significant variance, the corrective action often requires an update to the entire Project Management Plan, not just the cost components.
📐KA02 — Scope Management
The Scope Baseline (the WBS, WBS Dictionary and Project Scope Statement) is a primary input to both Estimate Costs and Determine Budget. Every work package in the WBS must have a cost estimate — without a defined scope, you cannot estimate costs reliably. Scope creep — adding work without adjusting the cost baseline — is the most common cause of cost overruns. Control Scope and Control Costs must operate in tandem: every scope change request must include a cost impact assessment before approval. If scope grows without a corresponding budget increase, cost performance will inevitably deteriorate.
📅KA03 — Schedule Management
Schedule and cost are so closely intertwined that EVM explicitly combines them in a single measurement framework. The Project Schedule is a direct input to Determine Budget — without knowing when work will be performed, you cannot time-phase the budget into the S-curve cost baseline. Schedule delays increase costs through extended resource burn rates, supplier delay penalties and extended project overhead. EVM's SPI provides a cost-denominated schedule performance measure that connects the two knowledge areas numerically. Crashing a schedule (adding resources to recover time) is a cost management decision as much as a schedule one.
⭐KA05 — Quality Management
The Cost of Quality concept connects these two knowledge areas directly. Prevention costs (training, process design, quality planning) and appraisal costs (testing, inspection) are cost components that must be estimated and budgeted in Estimate Costs. Non-conformance costs (rework, defect correction, warranty claims) represent unplanned cost impacts that damage CPI. A project that under-invests in quality often sees its cost performance deteriorate in later stages as rework cost exceeds the prevention investment that was skipped. The Quality Management Plan directly informs cost estimates.
👥KA06 — Resource Management
Labour is typically the largest single cost category in most projects. Resource costs — hourly rates, day rates, overhead charges, travel and accommodation — flow from Resource Management into Estimate Costs as a primary input. Resource levelling decisions in Schedule Management affect cost because moving work to different time periods changes when high-cost resources are deployed. When a project faces a cost overrun, the first lever is almost always resource adjustment — reducing hours, substituting lower-cost resources, or adjusting resource mix. The Resource Management Plan and cost estimates are developed interdependently.
⚠️KA08 — Risk Management
Risk management and cost management share the concept of reserves. Contingency reserves (identified from the risk register's known risks) are included within the cost baseline — the PM can access them without seeking additional approval when the associated risk materialises. Management reserves (for unknown unknowns) sit above the baseline and require formal authorisation. Risk responses — avoid, transfer, mitigate, accept — all have cost implications that must be estimated and budgeted. Quantitative risk analysis (Monte Carlo simulation) can model the likely range of project costs, producing a probability distribution rather than a single-point estimate.
🛒KA09 — Procurement Management
Procurement decisions directly shape cost structure. A fixed-price contract transfers cost risk to the supplier but typically at a higher base price. A time-and-materials contract transfers cost risk to the project — actual supplier hours and rates flow directly into AC. Contract type selection in Procurement Management is therefore a cost risk decision. Vendor bid analysis (a tool in Estimate Costs) uses procurement market data to validate estimates. Significant cost variance investigations frequently trace back to supplier performance — delays, rework or contract change orders from procurement.
📣KA07 — Communications Management
Cost performance information — CPI, EAC, VAC, variance reports — must be communicated accurately and appropriately to different stakeholder audiences. The Communications Management Plan defines who receives cost reports, at what frequency and in what format. Communicating a CPI of 0.83 to a technical team requires different framing than communicating a projected £20K overrun to a finance-focused project board. Poor cost communication — either under-reporting variances (creating surprise) or over-reporting them (creating panic) — damages stakeholder trust and undermines the governance function that depends on accurate cost information.
Agile and Hybrid Approaches
Project Cost Management in Agile, Waterfall and Hybrid Environments
The four PMBOK cost management processes were designed primarily for predictive (waterfall) delivery environments. In Agile and hybrid contexts, the same underlying objectives apply — spending within authorised limits, forecasting accurately, managing reserves appropriately — but the mechanisms look quite different.
🏛️ Cost Management in Waterfall (Predictive)
In a traditional waterfall environment, cost management follows the full PMBOK process model:
Costs are estimated in detail during the planning phase from a fully-defined WBS
A formal cost baseline (S-curve) is established before work begins
EVM is used throughout execution to track cost and schedule performance against the baseline
Variances exceeding thresholds trigger formal change requests to adjust the baseline
Management reserves require sponsor authorisation to access
Cost forecasting (EAC) uses EVM projections to anticipate final cost
Cost reporting frequency is typically monthly with formal variance analysis
Scope changes must include cost impact assessment before approval
Key challenge: The fixed cost baseline assumes the scope was correctly defined upfront. When scope understanding evolves (as it inevitably does), every change must go through formal change control — creating administrative overhead and potential delays.
🔄 Cost Management in Agile
In pure Agile environments, the relationship between cost and scope is inverted from waterfall:
Time and cost are typically fixed (the team, the sprint duration, the cadence) — scope is the variable
Budgeting is often at the team level (cost per sprint × number of sprints) rather than at the feature level
Burn-down and burn-up charts replace EVM as the primary cost/progress monitoring tools
Cost per story point or cost per velocity unit provides a rough parametric estimating mechanism
Continuous re-prioritisation of the backlog serves as the scope control mechanism — lower-priority items are removed rather than formally changed
Financial forecasting uses velocity trend analysis rather than CPI projection
The concept of a fixed cost baseline is replaced by a rolling budget allocation per sprint cycle
Key challenge: Agile cost management provides less financial predictability than waterfall — sponsors who need to know total project cost with certainty before approving it are less comfortable with Agile's variable-scope model.
Cost Management in Hybrid Environments
Most real-world projects in 2026 are neither pure waterfall nor pure Agile — they operate in hybrid environments where PRINCE2 or PMBOK governance structures are maintained at the project level while delivery teams work iteratively. Cost management in hybrid environments combines elements of both approaches.
The typical hybrid cost model: a formal cost baseline is established for the overall project (as in waterfall), divided into stage-level budget allocations. Within each stage, Agile delivery teams operate with a fixed sprint budget (time-boxed team cost). The stage budget serves as the tolerance within which the PM manages — if a stage is likely to exceed its allocation, a formal exception report is raised. The Agile team delivers value within the sprint without needing to produce detailed line-item cost estimates for every feature.
Key hybrid techniques include: rolling wave planning (detailed cost estimates for near-term stages, rough-order-of-magnitude for future stages), story point cost mapping (cost per story point derived from team velocity × team cost rate), and Agile EVM adaptations (where story points completed serve as a proxy for Earned Value, allowing some EVM-style analysis even in iterative delivery).
Common Mistakes
The 6 Most Common Project Cost Management Mistakes
Using actual cost as a proxy for progress
Spending 50% of the budget does not mean 50% of the work is done. AC tells you what was spent; EV tells you what was earned. A project where AC = 50% of BAC and EV = 35% of BAC is significantly over budget — not on track. Always track EV alongside AC.
Baseline the budget without time-phasing it
A cost baseline that shows only the total approved budget — without distributing it across time — cannot support EVM analysis. Without a time-phased PV (the S-curve), you cannot calculate CV, SV, CPI or SPI. Every cost baseline must be time-phased to period-level granularity.
Confusing contingency reserves and management reserves
Contingency reserves are within the cost baseline and accessible by the PM for identified risks. Management reserves are above the baseline and require sponsor authorisation. Many PMs conflate them. On the PMP exam, this distinction is tested frequently — know exactly which reserve is in which budget tier.
Waiting until the end of a stage to identify cost overruns
By the time a stage ends with a significant cost overrun, the PM has lost the ability to take corrective action within that stage. EVM's value is in providing early warning — a CPI of 0.88 in week 4 projects a significant overrun by week 12 if the trend continues. Analyse EVM data at each reporting period, not just at stage gates.
Applying the wrong EAC formula
There are three main EAC formulas, each based on a different assumption about remaining work. EAC = BAC/CPI assumes the current CPI trend continues. EAC = AC + (BAC − EV) assumes remaining work will be done at the planned rate. EAC = AC + ETC uses a fresh estimate. Using the wrong one produces a misleading forecast. The PMP exam tests which formula is appropriate for which scenario.
Neglecting the cost impact of scope and risk changes
Cost management does not operate in isolation. A scope change approved without a cost impact assessment, or a risk that materialises without a pre-planned cost response, will damage cost performance. Every change request and every materialised risk must be evaluated for cost impact before the baseline is updated.
PMP and APM PMQ Exam Tips
Cost Management — 7 Exam Tips for PMP and APM PMQ
1
Know the budget structure hierarchy: Work package estimates → Contingency reserves = Cost Baseline. Cost Baseline + Management reserves = Project Budget. This distinction is frequently tested on both PMP and APM PMQ.
2
EV is the cornerstone of all EVM calculations. If you forget a formula, ask "what would I need EV for here?" Almost every EVM metric derives from EV. Get EV clear (% actual complete × BAC) and the rest follows logically.
3
CPI is more important than SPI for cost forecasting. SPI loses accuracy as a project approaches completion (EV approaches BAC, so SPI approaches 1.0 regardless of actual schedule performance). CPI remains a reliable predictor of final cost throughout the project. For EAC questions, CPI is the primary input.
4
Understand which EAC formula to use in which scenario. The exam will describe a situation and ask which EAC formula is appropriate. EAC = BAC/CPI when current efficiency continues. EAC = AC + (BAC−EV) when the past variance is a one-time anomaly. EAC = AC + ETC when a fresh estimate is more reliable than CPI projection.
5
TCPI above 1.1 is a red flag, not just a number. The exam often asks what action a PM should take when TCPI is above 1.0 or 1.1. The correct answer involves escalation, reporting, and likely a change request to revise the baseline — not simply working harder.
6
Three-point estimating: know both formulas. Triangular distribution: (O + M + P) / 3. Beta/PERT: (O + 4M + P) / 6. The beta distribution weights the most likely estimate more heavily and is generally considered more realistic. The exam may specify which to use — pay attention to the scenario language.
7
Cost control ≠ cost reporting. A PM who reports variances but takes no action is not controlling costs. The correct response to a negative CPI is a corrective action plan, investigation of root cause, and likely a change request. The exam rewards PMs who act, not just those who track.
Use This Knowledge Area on Your PMP or APM PMQ
Cost management processes and EVM formulas are examined in both the PMP and APM PMQ. The PMP exam includes ~15% cost management questions; APM PMQ tests it across budgeting, control and benefits management learning outcomes.
The four processes in PMBOK Project Cost Management (Knowledge Area 7) are: (1) Plan Cost Management — establishing the policies and procedures for managing project costs, producing the Cost Management Plan; (2) Estimate Costs — developing approximations of the monetary resources needed for each activity, producing Cost Estimates and Basis of Estimates; (3) Determine Budget — aggregating individual cost estimates to establish the authorised Cost Baseline (time-phased S-curve); and (4) Control Costs — monitoring actual costs against the baseline, using Earned Value Management to detect variances and forecast final cost, and managing changes to the baseline. The first three processes belong to the Planning Process Group; Control Costs belongs to Monitoring and Controlling and runs throughout the project lifecycle.
The cost baseline is the approved, time-phased budget for the project that includes work package estimates plus contingency reserves — but excludes management reserves. It is the reference against which project cost performance is measured using EVM. The project budget is the total authorised funding for the project, which equals the cost baseline plus management reserves. Management reserves are held above the cost baseline for unknown unknowns (unforeseen events) and require specific authorisation from the project sponsor or steering group to access — they cannot be used by the project manager without that approval. The project manager can authorise use of contingency reserves (which are within the baseline) when the associated identified risk materialises, without seeking additional approval.
A Cost Performance Index (CPI) below 1.0 means the project is over budget — the project is getting less than £1 of value for every £1 spent. For example, a CPI of 0.83 means the project is earning only 83 pence of budgeted work for every pound of actual expenditure. CPI is calculated as EV ÷ AC (Earned Value divided by Actual Cost). CPI below 1.0 is also used to forecast the final project cost: EAC = BAC ÷ CPI. A CPI of 0.83 applied to a £100K project forecasts a final cost of approximately £120K. The lower the CPI, the more significant the projected overrun. Research suggests that CPI established by the 20–25% completion point rarely improves significantly by project end, making early CPI tracking critical for accurate forecasting.
In waterfall, scope is fixed and costs are estimated in detail upfront against a fully defined WBS — the cost baseline represents a commitment to deliver specific deliverables for an agreed budget. Cost management focuses on tracking actual spending against the baseline using EVM and managing changes through formal change control. In Agile, cost and time are typically fixed (the team cost per sprint is known) and scope is the variable — lower-priority features are removed from the backlog rather than raising change requests. Cost management in Agile focuses on burn rate (team cost per sprint × sprints consumed) and burn-down charts rather than EVM. Feature-level cost estimation is replaced by velocity-based forecasting (number of remaining story points ÷ velocity × sprint cost). In hybrid environments, a formal cost baseline is maintained at stage level while Agile delivery operates within sprint-level budget allocations.
Earned Value Management (EVM) is a method for objectively measuring project performance by comparing what was planned, what was accomplished, and what was spent. It combines three data points: Planned Value (PV — what you planned to have done by now in budget terms), Earned Value (EV — the budget value of what you have actually completed), and Actual Cost (AC — what you have actually spent). By comparing these three values, EVM can tell you whether the project is over or under budget (Cost Variance = EV − AC), ahead or behind schedule in cost terms (Schedule Variance = EV − PV), the efficiency of cost spending (CPI = EV/AC), and the projected total final cost (EAC = BAC/CPI). Its power is that it answers a question that pure cost tracking cannot: not just "how much have we spent?" but "how much value have we earned for what we spent?"
Bottom-up estimating is the most accurate cost estimating technique — it estimates costs at the individual work package or activity level and aggregates them upward through the WBS. Because every element of work is individually assessed, it captures detail that higher-level techniques miss. However, it is also the most time-consuming, requiring a fully defined WBS and detailed resource information. Parametric estimating can be highly accurate for well-understood, repeatable work types where a reliable statistical relationship between cost and a measurable parameter (cost per m², cost per function point) exists. Three-point (PERT) estimating improves accuracy by explicitly accounting for uncertainty using optimistic, most likely and pessimistic scenarios. Analogous estimating is the least accurate but fastest. In practice, most projects use a combination: analogous or parametric for early estimates, bottom-up for detailed planning once scope is defined.