Project Budgeting and Cost Control for IT Projects: Baselines, Reserves and Forecasts

Money is the constraint everyone understands. A project that delivers the right scope on time but overspends has still disappointed its sponsor. Cost management covers planning how costs will be estimated and controlled, estimating them, setting a budget and keeping spending in line as the project proceeds. This lesson focuses on building the budget and controlling it; the next one, Earned Value Management, adds a powerful measurement technique.

The Four Cost Processes

  1. Plan cost management: decide units of measure, precision, thresholds and reporting formats.
  2. Estimate costs: approximate the cost of each resource and work package.
  3. Determine the budget: aggregate estimates, add reserves and establish a cost baseline.
  4. Control costs: monitor spending, manage changes and forecast.

Typical IT Project Cost Categories

CategoryExamples
PeopleInternal staff time, contractors, consultants, vendor professional services
SoftwareLicences, subscriptions, development tools, third-party components
InfrastructureServers, cloud usage, networking, test environments
Training and changeCourse delivery, materials, communications
DataMigration, cleansing, conversion
Governance and overheadProject management, quality assurance, audits, travel
Contingency and reservesAmounts held for identified and unidentified risks

Direct, Indirect, Fixed and Variable Costs

Direct costs are attributable to the project, such as a developer’s salary during the project. Indirect costs are shared overheads such as office space. Fixed costs do not change with volume (a licence purchased once) while variable costs do (cloud usage that rises with traffic). Knowing which is which helps you forecast when scope or usage changes.

Total Cost of Ownership

The project budget normally covers only the cost to deliver. However, the organisation will also pay to run, support, maintain and eventually retire the system. Total cost of ownership (TCO) includes all of these. A cheap build with heavy support costs may be worse than a pricier but efficient solution. Make sure the business case and sponsor understand operating costs, not only project costs.

Building the Budget

  1. Estimate at work-package level using the techniques in Estimating IT Projects.
  2. Roll up the costs through the WBS to get control account totals.
  3. Add contingency reserves for identified risks.
  4. Arrive at the cost baseline, the approved time-phased budget.
  5. Add management reserve for unknown unknowns, to reach the project budget.
  6. Phase the spending over time to produce a cash-flow forecast.

Contingency Reserve vs Management Reserve

AspectContingency reserveManagement reserve
CoversIdentified risks (“known unknowns”)Unforeseen work (“unknown unknowns”)
Included in cost baseline?YesNo
Controlled byProject manager (within agreed rules)Sponsor or senior management
UseRelease when a risk occursRequires approved change to baseline

Contingency should be tied to the risk register, not guessed as a flat percentage; see Project Risk Management.

Worked Budget Example

ItemAmount (₹ lakh)
Analysis and design12
Development30
Testing and quality assurance10
Infrastructure and licences8
Data migration5
Training and rollout4
Project management6
Subtotal (work package estimates)75
Contingency reserve (from risk register)7
Cost baseline82
Management reserve4
Project budget86

The sponsor approves ₹86 lakh. The project manager manages to ₹82 lakh. If something unforeseen arises that exceeds the contingency, the project manager must request a baseline change to draw on the management reserve.

Controlling Costs

  • Track actual costs against the budget regularly, including committed costs (purchase orders raised but not yet invoiced).
  • Forecast to completion, as past spending alone does not show where you will end up.
  • Investigate variances above agreed thresholds, for example 5 per cent, and find the cause.
  • Manage change through change control so scope additions carry funding.
  • Review burn rate: the speed at which funds are consumed, compared with progress.
  • Watch vendors and contractors, including time-and-materials overruns.

Capital vs Operating Expenditure

Many organisations treat project spending as capital expenditure (CapEx), which is capitalised and depreciated, and ongoing running costs as operating expenditure (OpEx). Cloud subscriptions have shifted many IT costs from CapEx to OpEx. The classification affects budgeting, approvals and tax, so check with finance early. This is accounting guidance, not tax advice; your finance team applies the rules for your organisation.

Common Mistakes

  • Forgetting operating costs after go-live.
  • Adding a flat 10 per cent contingency without linking it to risks.
  • Tracking only invoices and missing commitments.
  • Cutting the testing or training budget first when money tightens.
  • Failing to update the forecast after approved changes.
Key takeaways
  • Build the budget bottom-up, then add contingency reserve to form the baseline and management reserve for the total budget.
  • Contingency covers identified risks; management reserve covers the unforeseen and needs approval.
  • Consider total cost of ownership, not just delivery cost.
  • Control by tracking actuals and commitments, and by forecasting regularly.

Related Lessons