Skip to content
Tutorials Center
My learning

Topics

Lesson 15 of 41 ยท Scope, Time and Cost

Cost Estimation and Budgeting

Learn project cost estimation methods: analogous, parametric, bottom-up and three-point, direct and indirect costs, contingency and management reserve, and how to build a cost baseline.

Cost estimation predicts how much money a project needs to complete its work. Budgeting then aggregates those estimates into an approved cost baseline that actual spending is measured against. Estimates are never perfect, so good practice is to state the uncertainty and to improve the estimate as the project learns more.

Types of cost

  • Direct costs: attributable to the project: salaries of the team, equipment, licences, contractors.
  • Indirect costs: shared overhead: office space, management, utilities, allocated by a rule.
  • Fixed costs: do not change with output (a licence).
  • Variable costs: scale with usage (hourly contractors, cloud usage).
  • Recurring versus one-time and capital versus operating: important for the business case.
  • Total cost of ownership: includes running and support after delivery, not just building.

Estimate accuracy

Estimates are rough early and refined later. Common labels, with typical ranges:

Stage Name Typical accuracy
Idea Rough order of magnitude -25% to +75%
Planning Budget estimate -10% to +25%
Detailed plan Definitive estimate -5% to +10%

The cone of uncertainty says the same: the range narrows as the project advances. Giving a single number at the very start gives false precision.

Estimation techniques

Analogous (top-down)

Use the actual cost of a similar past project, adjusted for differences. Fast and cheap, less accurate; best early on.

Parametric

Use a statistical relationship between a measurable variable and cost: cost per square metre, cost per screen, cost per function point. Accuracy depends on the quality of the history behind the rate.

Bottom-up

Estimate each work package or activity (see WBS), then add them. The most accurate method but needs the detailed scope and takes time.

Three-point (PERT)

For each item estimate optimistic (O), most likely (M) and pessimistic (P) values and combine: expected = (O + 4M + P) / 6. It captures uncertainty. See PERT estimates for the same idea applied to duration.

Expert judgement and reserve analysis

Experienced people review the numbers; reserves are added for known and unknown risk.

Python Bottom-up estimate with rates

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Three-point cost estimate

Python Three-point (PERT) costs

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Reserves

  • Contingency reserve: money for identified (known) risks. Part of the cost baseline, controlled by the project manager.
  • Management reserve: money for unidentified risks, held outside the baseline and released only by management.

Budget = work-package costs + contingency + (outside the baseline) management reserve.

From estimate to budget

  1. Estimate costs per work package.
  2. Aggregate up the WBS.
  3. Add contingency reserve to get the cost baseline.
  4. Distribute over time (an S-curve), the time-phased budget, so you can compare actual spending month by month.
  5. Add management reserve for the project budget.
  6. Get approval; changes go through change control.
Python Time-phased budget (S-curve)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Tips for better estimates

  • Estimate in ranges and write down assumptions.
  • Have the people who do the work estimate it, and use history from your own projects.
  • Do not forget non-development costs: management, testing, training, migration, documentation, licences, travel.
  • Re-estimate at gates and when scope changes.
  • Beware of anchoring: the first number mentioned sticks, even if it was a guess. Beware also of padding each item secretly, which hides uncertainty and gets cut; use visible reserves instead.
  • Track actuals so your next estimate has real data.

For software-specific sizing and effort models, see Software Size and Cost Models.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which estimating technique adds up estimates of each work package?

    Bottom-up sums detailed estimates and is usually the most accurate.
  2. 2. The three-point expected value with O=6, M=9, P=18 is...

    (6 + 4 x 9 + 18) / 6 = 60 / 6 = 10.
  3. 3. Which reserve covers unknown risks and sits outside the cost baseline?

    Management reserve is for unidentified risks and is controlled by management.
  4. 4. Why is an early single-number estimate risky?

    Early estimates have wide ranges (cone of uncertainty).

Summary

  • Know direct, indirect, fixed, variable costs and total cost of ownership.
  • Use analogous, parametric, bottom-up and three-point methods; refine as detail grows.
  • Contingency covers known risks; management reserve covers unknowns.
  • Aggregate and time-phase estimates into the cost baseline that earned value later uses.

Next: Software Size and Cost Models