Chapter 2 (Budgeting uncertainty and risk

management)
Top-Down Budgeting (Explained)
How it works

 Senior and middle managers use their experience and knowledge of similar past projects to estimate
the overall cost of a new project.
 They then break the budget into major parts and give these parts to lower-level managers.
 Those managers further divide the budget into smaller tasks.

Advantages

 Fairly accurate total budget because senior managers have broad experience.
 Small errors don’t matter much — if a small task is underestimated or missed, the overall budget
usually covers it.
 Fast — managers can estimate quickly without waiting for detailed task analysis.

Limitations

 Low-level tasks may be inaccurate because they are estimated without detailed input from the people
who actually do the work.
 Depends heavily on the judgment of upper managers — if their assumptions are wrong, the whole
budget can be off

Bottom-Up Budgeting (Explained)

How it works

 The Work Breakdown Structure (WBS) lists all tasks.

 Each person responsible for a task estimates the resources and time needed.
 These estimates (labour, materials, etc.) are converted to costs.
 Costs are then added up from bottom to top to form the total budget.
 Then the PM adds indirect costs (administration, contingency, profit).

Advantages

 Very accurate for small tasks since the people doing the work estimate them.
 Increases employee morale, acceptance, and commitment because workers participate.
 Helps train team members for future management roles.

Limitations

 Risk of missing small tasks, which can add unexpected costs.

 Time-consuming.
  Senior managers often resist because:
o Workers may inflate costs.
o They may need to cut the budget later, causing complaints.
o Managers want to maintain control over budget limits.

Using Both Methods

 Many organizations combine both:
o Top-down for overall structure.
o Bottom-up for detail.
 They compare and negotiate the differences.
 It takes extra time but gives a more balanced and realistic budget.

Point Top-Down Budgeting Bottom-Up Budgeting

People who actually perform the

Who estimates? Senior & middle managers
tasks
Estimate total project cost first, then Estimate each small task first, then
How it starts?
divide downward add upward
Accurate overall, less accurate at
Accuracy Very accurate at detailed task level
detailed levels
Risk of overlooking small but costly
Risk Risk of error in small tasks
tasks
Speed Faster Slower (more detailed work)
Employee involvement Low involvement High involvement; participative
Less control by top; workers input
Management control High control by top management
more
Acceptance & High commitment; team owns the
Lower team commitment
Commitment budget
Assumptions of upper managers may Workers may overestimate (inflate)
Possible problems
be wrong costs
Need detailed accuracy; strong
Best used when Time is limited; past data is available
teamwork culture
Common usage Most organizations prefer this method Less commonly used fully
Quick, overall accurate, covers Detailed accuracy, good for morale,
Strengths
overlooked small tasks good training
Time-consuming, may miss some
Weaknesses Weak detail accuracy
tasks
Use both methods together for best Works better when combined with
Ideal Approach
results top-down
1. Explain why top-down and bottom-up budgeting estimates often differ.

Answer:
Top-down and bottom-up estimates differ due to the following reasons:

1. Different perspectives: Bosses often view tasks as easier, faster, and cheaper than the
workers who perform them.
2. Optimism bias: Bosses are typically optimistic and assume no major problems or
overlooked details.
3. Pessimism and safety padding: Subordinates tend to add extra cost and time to protect
against uncertainties and potential issues.

2. Describe how negotiation helps reduce differences between top-down and

bottom-up estimates.

Answer:
Negotiation between the boss and subordinate reduces differences through:

1. Clarifying real work requirements, causing the boss to increase the estimate.
2. Boss requesting reduction of unnecessary safety padding, causing the subordinate to
lower the estimate.
3. Joint search for efficiencies, where both parties identify better methods or technologies to
lower costs and durations.
4. Honest and cooperative communication, enabling a win-win outcome rather than conflict.

3. What should management do if the subordinate’s cost estimate remains

higher even after negotiation?

Answer:
Management should decide based on the shape of the project life cycle:

 For S-shaped life cycle projects, accepting top-down budgets is usually safe because
small resource cuts lead to only minor performance reductions.
 For J-shaped life cycle projects, top-down reductions are dangerous because small cuts
can cause major performance losses.
→ Therefore, management should accept the subordinate’s higher bottom-up estimate.

4. Differentiate between S-shaped and J-shaped project life cycles in terms of

budget cuts.

Answer:
  S-shaped life cycle:
o Impact of reduced resources is small and nearly proportional. Less sever effect
o The project can still meet objectives with minor adjustments.
o Top-down budgeting is generally acceptable.
 J-shaped life cycle:
o Resource cuts lead to large, disproportionate declines in performance.
o Severe underfunding can cause major delays or failures.
o Bottom-up budgeting is essential.

1. What is activity budgeting?

Answer:
Activity budgeting is a traditional organizational budgeting method where:

1. Expenses are grouped according to activity categories (e.g., phone, materials, salaries).
2. Costs are accumulated using historical, activity-based accounting systems.
3. Budgets are reported by organizational units such as departments or divisions.
4. Project-related expenses may be spread across several units, causing loss of control over
individual project costs.
5. It may be difficult to track resources accurately when multiple projects share resources.

2. What is program budgeting?

Answer:
Program budgeting organizes expenses according to the project’s tasks and time periods.
Key features include:

1. Budgets are divided by project task and expected time of expenditure.

2. Allows aggregation of costs across multiple projects.
3. Provides clearer visibility of each project’s total spending.
4. Reports include both regular operations and individual project budgets.
5. Helps maintain better control over project resource usage.

Activity Budgeting Program Budgeting

Based on traditional activity lines (phone, materials,
Based on project tasks and time periods.
salaries).
 Activity Budgeting Program Budgeting
Reported department-wise. Reported project-wise.
Focuses on current project planning and
Uses historical, activity-based accounting.
control.
Hard to track true project costs when multiple units Provides clear, project-specific cost
contribute. visibility.
Suitable for routine operations. Better for project-based organizations.

2. What are some ways to improve the cost estimating process?

Answer:
Improvements include:

1. Using standardized forms to collect consistent estimating data.

2. Applying learning curves to adjust estimates for repeated tasks.
3. Using tracking signals to detect systematic forecasting bias.
4. Formalizing the estimating process with clear procedures.
5. Addressing behavioral factors such as optimism, pessimism, and “padding.”

3. Explain how forms help improve cost estimates.

Answer:
Forms improve estimating by:

1. Providing a structured method to capture cost, time, resource needs, and availability.
2. Ensuring all relevant details (who, when, how much, availability) are included.
3. Allowing the PM to aggregate data from all tasks into a project-wide resource plan.
4. Reducing mistakes caused by missing or inconsistent information.

4. What is a learning curve and why is it important in cost estimating?

Answer:T
A learning curve shows that:

 Each time production quantity doubles, the labor hours per unit decrease by a fixed
percentage (learning rate).
 Humans become more efficient with repetition.
 Downward sloping
 More repetition = less cost

Importance:
 1. Prevents underestimation for early units (which take longer).
2. Prevents overestimation if only prototype time is used.
3. Produces more realistic labor cost calculations, especially for manufacturing and repeated
tasks.
4. Helps generate accurate budgets using data such as the first-unit time and learning rate.

Time(cost)

repitition

The time required to produce the xth unit is:

Tx=T1 Xb
Where:
 Tx = time for the xth unit of output
 T1= time for the first unit of output
 R = learning rate
log r
 Learning curve slope, b= log 2

Example:
 First unit of a complex device takes T1=10 hours.
 Learning rate, r = 80%. B= (log 0.8) / (log 2) = -0.32
 Labor time reduces as output doubles:
 2nd unit, T2 → 8 hours
 4th unit → 6.4 hours
Time needed for nth unit, Tn = T1nb
Time needed for mth unit, Tm = T1mb
n
So, Tn = Tm ( m )b
Example: time for 10th unit is 30 hour. If b is -0.2, what is the time for 50th
unit?
50
T50= 30( 10 )0.2 = 22 hour
7. What is a tracking signal?

There are 2 types of errors,

Random errors:
o Occur unpredictably.
o Over- and underestimates cancel out over time.
o Average error tends toward zero.
Biased errors:
o Systematic tendency to overestimate or underestimate.
o Do NOT cancel out.
o Create consistent cost/time inaccuracies.

A tracking signal is a numerical measure used to detect bias in cost or

duration estimates. Calculation of a number called the tracking signal can
reveal if there is systematic bias in cost and other estimates and whether
the bias is positive or negative.
Knowing this can then be quite helpful to a PM in making future
estimates or on the critically important task of judging the quality of
estimates made by others
Key points:
 1. It compares the cumulative forecast error to the mean absolute
ratio (MAR).
2. If estimates are unbiased → tracking signal ≈ 0.
3. Large positive signal → systematic underestimation.
4. Large negative signal → systematic overestimation.

Budget Uncertainty
1. Concept of Budget Uncertainty

Budget uncertainty refers to the possibility that actual project costs may differ from estimated costs. At the
start of the project, the project manager (PM) views the estimate as a range of possible outcomes. More factors
tend to increase cost rather than decrease it, which makes budget overruns more likely.

As the project progresses, uncertainty gradually decreases because actual costs to date become known.
Revised estimates are prepared at various points (t₁, t₂), each starting from the actual cost incurred so far.

2. Reasons for Budget Uncertainty

Cost uncertainty arises for several reasons:

1. Price escalation
– Increases in the cost of materials, labor, or equipment.
2. Resource variability
– Different types or quantities of resources may become necessary.
3. Time variations
– Longer project duration increases overhead and indirect costs.
4. General unpredictability
– Unexpected changes occur as the project progresses.
3. Three Causes of Change
(1) Technological Uncertainty

These changes occur due to misunderstanding or incorrect assumptions about how tasks will be executed.
Examples:

 A building foundation must be reinforced due to unidentified soil weakness.

 A new innovation allows tasks to be completed more easily than expected.

(2) Increased Knowledge/Sophistication

Changes occur because the client or project team learns more about the project’s scope or application during
implementation.
Examples:

 A medical team decides the device must be usable both in the hospital and in the field.
 Chemists discover a new application requiring additional materials.

(3) Mandates

Changes imposed by external authorities:

 New laws
 New industry standards
 New regulatory policies

These changes are the most difficult because they can affect any part of the project and usually come without
warning.

5. Risk Management
Project risk management includes three major areas:

1. Risk Identification
2. Risk Analysis
3. Risk Response

PMBOK breaks these into six subprocesses:

(1) Risk Management Planning

  Developing a structured plan for conducting risk processes.
 Ensures adequate resources and continuous monitoring.
 Many firms create a risk management group.

(2) Risk Identification

Risk identifi cation consists of a thorough study of all sources of risk in the project. Common sources of risk
include the organization of the project itself; senior manage ment of the project organization; the client; the
skills and character of the project team members, including the PM; acts of nature; and all of the three types of
changes described earlier under budget uncertainty.

(3) Qualitative Risk Analysis

 Assessing the likelihood, timing, and severity of each risk.

 Often performed immediately after identifying risks.

Tools used:

a. Scenario Analysis

 Scenario analysis is a well - known method for identifying serious risks.

 It involves envisioning likely scenarios (e.g., hurricanes, strikes, system failures) that may have major
repercussions on the organization
 then identifying the possible resulting outcomes of events

b. Failure Mode and Effect Analysis (FMEA)

FMEA is a structured approach similar to the scoring methods to help identify, prioritize, and better manage
risk. It was originally developed by NASA in the 1960s and is widely used in project management to prevent
failures before they occur.

1. Identify Potential Failure Modes

List all the possible ways the project, process, activity, or component could fail.
Examples include technical breakdowns, schedule delays, supply issues, or human-error-driven failures.

2. Determine the Effects of Each Failure and Rate Severity (S)

For each identified failure, describe what will happen if the failure occurs.
Then assign a Severity (S) rating using a 10-point scale:

 1 = No effect on the project

 10 = Extremely severe / hazardous effect with no warning
3. Identify Causes and Rate Likelihood (L)

List the causes or reasons for each failure.

Assign a Likelihood (L) score on a 10-point scale:

 1 = Very unlikely to occur

 10 = Almost certain to occur

4. Evaluate Detectability (D)

Estimate how easily the failure can be detected before it causes harm.
Assign a Detectability (D) score using a 10-point scale:

 1 = Almost certain to detect

 10 = Almost impossible to detect

Higher D means poorer detectability.

5. Calculate the Risk Priority Number (RPN)

Use the formula:

RPN = S × L × D\textbf{RPN = S × L × D}RPN = S × L × D

Higher RPN values indicate higher-priority risks that require urgent attention.

6. Prioritize and Develop Risk-Reduction Actions

 Sort all failure modes from the highest to lowest RPN.

 Focus managerial effort on failures with high RPN values.
 Identify corrective or preventive actions such as:
o design changes,
o improved controls,
o additional monitoring,
o or contingency planning.

(4) Quantitative Risk Analysis

Uses numerical techniques when probability estimates are available.

Key Methods:
a. Expected Value (EV)

When probabilities can be estimated, risk analysis often uses expected value, which combines outcome values
with their probabilities. Expected value is a neutral long-run prediction of average outcome.

EV = Σ [Probability × Outcome]
Used for decision tables (payoff matrices).

Decision tables and expected values are especially useful when:

 There are multiple technological options

 Each option has different costs, risks, and outcomes

By comparing expected values, managers can choose:

 The technology with the optimal long-term average cost

 The alternative with the best balance of risk and reward

1. Estimates in Risk Analysis

During the qualitative risk analysis stage, project managers must estimate the range and timing of possible
outcomes for risky events. While estimating cost ranges (optimistic, most likely, pessimistic) is usually
straightforward, estimating probabilities is more difficult because actual historical data may be unavailable.

In such cases, probability estimates are based on:

 Expert judgment
 Experience of individuals familiar with the activity
These subjective estimates are acceptable when no reliable data exists.

Three-Point Estimates

As discussed earlier in the PM life cycle, experts provide:

 Optimistic estimate (O)

 Most likely estimate (M)
 Pessimistic estimate (P)

These are later used to compute expected values or durations (covered in Chapter 5).

If no reasonable approximation can be made, other approaches such as equal probability assignment may be
used, though this is also arbitrary.

2. Game Theory Approach (Minimax Method)

When probability information is completely unavailable or unreliable, managers sometimes assume a

pessimistic viewpoint. This is the Game Theory approach.
Assume competitors or the environment act against you.
Select the option that results in the best of the worst outcomes.

This is called the minimax strategy.

Example: Choosing Between Two Mutual Funds

Interest Rate Condition Return on A Return on B

Rates rise 5% 3%

Rates fall 7% 12%

Worst outcomes:

 Fund A: 5%
 Fund B: 3%

The minimax approach selects A, because 5% is better than 3%.

This avoids maximum harm but sacrifices the chance of a higher (12%) return.

Game theory is useful when:

 No probability data exists

 Decisions must be risk-averse
 The environment is unpredictable

5. Risk Response Planning

 Risk response typically involves decisions about which risks to prepare for and which to ignore and
simply accept as potential threats.
 The main preparation for a risk is the development of a risk response plan.
 Such a plan includes contingency plans and logic charts detailing exactly what to do depending on
particular events.

(a) Contingency Plans (Plan B, C, D)

A contingency plan is a prepared backup plan designed to be implemented during an emergency or unexpected
event. It outlines alternative actions (“Plan B,” “Plan C,” or more) to ensure operations can continue or be
restored. It specifies who is in charge, what resources are available, where backup facilities are located, and
how support will be provided during the crisis.

 Who is in charge
 Resources available
 Backup facilities
 Communication lines
(b) Logic Charts

A logic chart is a diagram that outlines the flow of activities once a backup plan is activated. It shows
decisions, tasks, notifications, support needs, and information flows. Logic charts force managers to think
through the critical steps required in a crisis and highlight dependencies and interdependencies. They provide a
clear overview of how response and recovery operations should proceed using “If X happens, do this;
otherwise, do that” structures.

Show step-by-step response actions.

 Include decisions, tasks, notifications, dependencies.

(c) Tabletop Exercises & Dress Rehearsals

 Practice responses in simulated scenarios.

 Should be:
o Facilitated by experts
o Documented
o Debriefed
o Updated regularly

6. Risk Monitoring and Control

 Conducted by both the project team and the organization’s risk management group.
 Involves:
o Tracking identified risks
o Updating risk registers
o Documenting outcomes
o Learning lessons for future projects

A strong monitoring system ensures continuous improvement.