Exam objective 2.4 asks you to identify the components of a project budget and explain cost management processes. This concept is the backbone of ensuring a project doesn’t run out of money and gets finished. For the PK0-005 exam, you need to know not just what a budget is, but how costs are estimated, tracked, and controlled throughout a project’s life.
Jump to a section
A simple way to picture Budgeting and Cost Management
Ever wondered why a home renovation almost always costs more than the initial quote? The answer reveals the core challenge of project budgeting and cost management in IT.
Imagine you’re planning to renovate your kitchen. You start with a rough idea of what you want: new cabinets, a granite worktop, and a modern sink. You get a quote from a contractor for £15,000. That’s your initial budget estimate. But as work begins, you discover the plumbing behind the wall is rusted and needs replacing. That’s an unexpected cost — a risk you didn’t plan for. You also decide, mid-project, that you want under-cabinet lighting. That’s a scope change, a new feature added after the project started. The contractor tracks every hour of labour and every screw purchased. This ongoing tracking is cost control. At the end, you compare the actual spend (£18,500) against your original estimate (£15,000). That difference is a cost variance. Just like in IT, you need a baseline (the initial budget), a way to approve changes (change control), and a method to track spending (cost accounting). Without these, your kitchen — or your IT project — runs out of money before it’s finished.
Budgeting and cost management is the process of planning, estimating, funding, and controlling costs so that a project can be completed within the approved budget. It’s not just about adding up numbers; it’s a disciplined framework that keeps a project financially healthy from start to finish.
Let’s break down the key components. First, you have the cost baseline. This is the approved version of the project budget, broken down by time period. It’s your official spending plan. Before you can create a baseline, you must estimate costs. Cost estimation is the process of developing an approximation of the resources needed to complete project activities. For IT, this includes labour (salaries of developers, testers, project managers), hardware (servers, laptops), software (licences, subscriptions), and other direct costs (training, travel).
There are several techniques for estimation. Analogous estimating uses the actual cost of a previous, similar project as the basis for the current one. It’s quick but less accurate. Parametric estimating uses a statistical relationship between historical data and other variables — for example, calculating the cost of building a website based on £5,000 per page. Bottom-up estimating is the most accurate: you estimate individual work packages and then roll them up into a total. This is like pricing every single item in your shopping cart before going to the till.
Once you have estimates, you create the project budget, which is the sum of all estimated costs plus any contingency reserves. A contingency reserve is a specific amount of money set aside to cover identified risks — things that might happen, like a key developer being sick or a third-party API changing its pricing. These are risks you’ve thought about and planned for. On top of that, a management reserve is money set aside for unknown risks — completely unforeseen events, like a global pandemic or a major regulatory change. The management reserve is not part of the cost baseline; it’s held by senior management.
Now for the control part. Cost control involves monitoring the status of the project to update costs and managing changes to the cost baseline. The key tool here is earned value management (EVM) . EVM integrates scope, schedule, and cost. It answers three critical questions: where are we supposed to be (planned value), where are we actually in terms of work done (earned value), and how much have we actually spent (actual cost)? From these numbers, you calculate variances. A cost variance (CV) tells you if you are over or under budget. A schedule variance (SV) tells you if you are ahead or behind schedule.
When costs change, you need a formal change control process. Any proposed change to the budget must go through change control — a documented process to evaluate the impact, get approval, and update the baseline accordingly. This prevents unauthorised spending and keeps the project aligned with its goals.
Why does this exist? Before structured cost management, projects often ran over budget without anyone realising until the money was gone. They replaced guesswork with systematic tracking. Without these processes, stakeholders lose confidence, resources are wasted, and projects fail to deliver value. For PK0-005, you must understand that cost management isn’t an optional extra; it’s a core project management knowledge area that ensures financial accountability.
Plan Cost Management
Establish the policies, procedures, and documentation for planning, managing, and controlling project costs. This outputs the cost management plan, which defines the level of accuracy needed for estimates, units of measure, and rules for cost reporting.
Estimate Costs
Develop an approximation of the monetary resources needed to complete project activities. Techniques include analogous, parametric, or bottom-up estimating. The result is activity cost estimates, along with supporting detail about assumptions and constraints.
Determine Budget
Aggregate the estimated costs of individual activities or work packages to establish an authorised cost baseline. This step adds contingency reserves and, if applicable, management reserves. The budget includes the total funds authorised to perform the project.
Control Costs
Monitor the status of the project to update project costs and manage changes to the cost baseline. This involves measuring actual costs against the baseline, calculating earned value metrics, and forecasting future spending. Any variance triggers analysis and, if necessary, a change request.
Perform Cost Closure
At project completion, finalise all cost-related activities. This includes reconciling actual costs with the budget, documenting lessons learned about cost performance, and archiving cost records for future reference. Final cost reports are shared with stakeholders.
An IT professional working on a project to update a company’s customer relationship management (CRM) system uses budgeting and cost management every day. Here’s how it plays out step by step.
The project manager (PM) starts with cost estimation. They talk to the development team to estimate hours for building custom features. They get quotes from software vendors for licences and from cloud providers for hosting. Using bottom-up estimating, they sum all these numbers and add a 15% contingency reserve for known risks, like a potential delay in delivery from a vendor. This total becomes the cost baseline, which is approved by the project sponsor.
During execution, the PM monitors actual costs against the baseline. They might use a tool like Microsoft Project or a spreadsheet to track labour hours entered by the team. Every week, they run a cost report. For example, the plan said they should have spent £20,000 by week 4. The team has actually logged £22,000 worth of work. But the earned value — the value of work actually completed — is only £19,000. This tells the PM they are both over budget (cost variance of -£3,000) and behind schedule (schedule variance of -£1,000).
The PM investigates. They discover the team spent extra hours because a new compliance requirement was missed during planning. The PM initiates a change request through the formal change control process. The change request documents the impact on the budget and schedule. The change control board (CCB) — a group of stakeholders who review changes — approves an additional £5,000. The PM updates the cost baseline to the new approved budget.
At the end of the project, the PM performs cost closure. They compare the final actual cost against the final baseline. They document lessons learned about why estimates were off and how risks were managed. This information is archived for use in future projects.
Key actions an IT professional performs:
Create and maintain a detailed cost management plan.
Use estimation techniques (analogous, parametric, bottom-up) to forecast costs.
Track labour, software, and hardware costs against the baseline.
Calculate earned value metrics (CV, SV, CPI, SPI) regularly.
Facilitate change control for any budget adjustments.
Report cost performance to stakeholders in simple terms.
The PK0-005 exam tests budgeting and cost management in several specific ways. You won’t be asked to calculate a complete EVM problem, but you must understand the concepts and their definitions. Here’s what to expect.
Key concepts tested: - Cost baseline vs. project budget: The cost baseline is the approved budget excluding management reserves. The project budget includes the baseline plus management reserves. - Types of costs: Direct costs (costs directly attributable to the project, like developer salaries) vs. indirect costs (shared costs, like office rent). Fixed costs (unchanged regardless of output, like a software licence) vs. variable costs (change with output, like cloud usage). - Contingency reserves vs. management reserves: Contingency is for known risks and is part of the cost baseline. Management reserve is for unknown risks and is part of the overall budget but not the baseline. - Estimation techniques: Analogous, parametric, bottom-up. Know which is most accurate (bottom-up) and which is fastest (analogous). - Earned value management terms: Planned value (PV), earned value (EV), actual cost (AC). Understand what a positive cost variance means (under budget) and a negative cost variance means (over budget).
Trap patterns: - The exam might describe a scenario where a project is over budget and ask what the PM should do first. The correct answer is always to perform a root cause analysis or initiate change control — not to immediately cut costs. - They may present a cost that seems like a direct cost but is actually indirect (e.g., electricity). Read carefully. - Questions that ask for the ‘cost baseline’ vs. ‘project budget’ often include a management reserve figure that should be excluded from the baseline.
Exam tips: - Memorise the difference between contingency and management reserves. This is a common multiple-choice trap. - When asked about a cost issue, look for the answer that follows the formal change control process. - The definition of ‘cost variance’ is EV minus AC. A positive result is good (under budget). - Analogy: analogous estimation is like guessing based on past projects. Bottom-up is like calculating every single Lego brick.
The exam will not test complex calculations, but you must be able to interpret a simple EVM statement. For example, if EV is higher than AC, the project is under budget. If PV is higher than EV, the project is behind schedule.
The cost baseline is the approved time-phased budget, excluding management reserves, and is the primary benchmark against which spending is measured.
Contingency reserves cover known risks and are part of the cost baseline; management reserves cover unknown risks and are held outside the baseline.
Bottom-up estimating, which estimates individual work packages and rolls them up, is the most accurate estimation technique.
Earned value management (EVM) compares planned value, earned value, and actual cost to objectively measure project performance.
A positive cost variance (EV > AC) means the project is under budget; a negative variance (EV < AC) means it's over budget.
Any change to the project budget must go through a formal change control process and be approved by the change control board (CCB).
Direct costs are directly attributable to the project (e.g., developer salaries), while indirect costs are shared across the organisation (e.g., utilities).
Analogous estimating uses historical data from a similar project and is quick but less accurate than parametric or bottom-up methods.
These come up on the exam all the time. Here's how to tell them apart.
Cost Baseline
Includes contingency reserves but not management reserves
Is the primary benchmark for performance measurement
Is time-phased (broken down by project period)
Project Budget
Includes cost baseline plus management reserves
Represents total authorised funding for the project
Management reserve is not time-phased; held centrally
Contingency Reserve
Covers known risks (identified in risk management)
Part of the cost baseline
Project manager can authorise its use
Management Reserve
Covers unknown risks (unforeseen events)
Not part of the cost baseline; part of overall budget
Requires senior management approval for use
Analogous Estimating
Uses historical data from similar projects
Less accurate; good for early-stage estimates
Fast and inexpensive to perform
Bottom-Up Estimating
Estimates individual work packages and rolls them up
Most accurate estimation technique
Time-consuming and costly to develop
Direct Costs
Directly attributable to one project (e.g., contractor fees)
Easily tracked per project
Includes costs like hardware, software licences, and travel
Indirect Costs
Shared across multiple projects (e.g., electricity, rent)
Allocated using an overhead rate
Includes costs like utilities, administration, and security
Fixed Costs
Do not change with the amount of work (e.g., annual licence fee)
Same regardless of project duration or output
Incurred once or periodically at a set rate
Variable Costs
Change based on project activity (e.g., cloud compute hours)
Can increase or decrease with scope changes
Billed per usage or per unit of work
Mistake
The project budget and the cost baseline are the same thing.
Correct
The cost baseline is part of the project budget. The project budget includes the cost baseline plus management reserves for unknown risks.
Beginners see both as 'the approved money' and miss the subtle difference tested in the exam.
Mistake
Contingency reserves are used for any unexpected cost, including scope changes.
Correct
Contingency reserves are only for identified risks (e.g., a known potential delay). Scope changes must go through change control and may require additional funding, not contingency.
The word 'contingency' sounds like a catch-all buffer, so beginners think it covers everything.
Mistake
If a project is under budget, the project manager should spend the remaining money on extra features.
Correct
Spending leftover budget without change control is unauthorised and violates the cost baseline. Any changes must be formally approved.
Real-world teams sometimes do this ('use it or lose it'), but the exam tests formal process, not common shortcuts.
Mistake
Earned value management (EVM) is only needed for large construction projects, not for small IT projects.
Correct
EVM can scale to any project. It’s a methodology that provides objective cost and schedule performance data, valuable even for small software updates.
Beginners associate EVM with massive engineering projects and underestimate its usefulness in IT.
Mistake
Indirect costs, like office rent, are not part of the project budget because they aren’t directly caused by the project.
Correct
Indirect costs are typically allocated to the project using an overhead rate and are included in the total project budget.
Newcomers think only direct expenses matter, but organisations recover all costs through project budgets.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
The cost baseline is the approved budget excluding management reserves. The project budget includes the cost baseline plus management reserves. Management reserves are for unknown risks.
EVM stands for Earned Value Management. It’s a methodology that combines scope, schedule, and cost measurements to assess project performance.
Cost variance (CV) is calculated as earned value (EV) minus actual cost (AC). A positive CV means you’re under budget; a negative CV means you’re over budget.
A contingency reserve is money set aside to cover identified risks — specific events you’ve planned for, like a delay from a vendor. It’s part of the cost baseline.
Direct costs are directly attributable to a specific project (e.g., developer salaries, cloud hosting fees). Indirect costs are shared across multiple projects (e.g., office rent, administrative staff salaries).
First, analyse the root cause of the overrun. Then, submit a formal change request through the change control process. Do not simply spend additional money without approval.
You've finished Budgeting and Cost Management. Continue through the PK0-005 study guide to build a complete picture of the exam.
Done with this chapter?