Budgeting and Scheduling in Projects (Boston Course) Notes — MNG 0001 & Project Management Short Course (Boston City Campus)

Budgeting and scheduling are the two “spines” of project management: budgeting answers how much resources cost, while scheduling answers when work must happen. In practice, the two are inseparable—cash flow depends on schedule decisions, and schedule feasibility depends on budget constraints. These notes consolidate the core ideas typically examined in project planning modules (including MNG 0001 style introductory management content) and align them with the Boston City Campus Project Management Short Course & Certification Notes approach, using South Africa–relevant terminology and exam-ready structure.

A strong exam performance usually requires not only defining terms (e.g., baseline, critical path, cost variance) but also demonstrating correct logic, calculations, and interpretation using realistic project scenarios.

1) Project Budgeting Foundations (Boston Style) — Linking Costs to Work, Resources, and Time

Budgeting goals: the “why” behind the numbers

Project budgeting is the process of estimating, aggregating, and controlling the project’s costs so that the project can deliver the required scope within approved financial limits. In most university and short-course examinations, budgeting is assessed on three linked outcomes:

1. Estimating accuracy: Can you justify estimates (top-down and bottom-up), identify assumptions, and manage uncertainty?
2. Traceability: Can you show that costs align with specific work packages and resources?
3. Control readiness: Can you monitor performance against baselines (e.g., through variance analysis) and support decisions like re-planning or corrective action?

Budgeting is not just arithmetic. It is a governance mechanism. When budgets are created without schedule logic, projects often fail when reality “arrives”—deliverables slip, labour costs escalate, or procurement arrives late.

The budgeting hierarchy: from scope to cost breakdown

A well-structured project budget typically follows a hierarchy similar to the Work Breakdown Structure (WBS):

• WBS Level 1–2: Major deliverables / phases (e.g., Design, Procurement, Construction/Implementation, Testing)
• WBS Level 3–4 (work packages): Concrete units of work that can be estimated and scheduled
• Activity-level estimates: Labour, materials, equipment, subcontractors per activity
• Cost accounts: Aggregations used to build baselines (often aligned to control accounts)

In exam settings, you may be asked to explain why work packages matter. The reason is that they define where costs “attach” to scope. This supports accountability and avoids vague budgeting like “$50,000 for site work” without specifying what tasks consume that money.

Cost categories: what must appear in a budget

Budgeting becomes clearer when you define cost categories. Common categories include:

• Direct costs
  • Labour (project staff, contractors, skilled trades)
  • Materials (consumables, equipment purchases)
  • Subcontractor costs
  • Equipment rental or depreciation (depending on modelling approach)
• Indirect costs
  • Project management overhead
  • Admin support
  • Facilities and shared services
• Contingency and management reserves
  • Contingency: funds reserved for identified risks and known unknowns (often tied to a risk register)
  • Management reserve: for unforeseen but plausible events, typically authorized at management level

Exams often reward the distinction between contingency and reserves. A common misunderstanding is treating contingency as “extra budget” without linking it to risks.

Example: contingency tied to risk

Consider a building refurbishment project in which there is a risk that the supplier may deliver tiles 2 weeks late. A contingency amount is then estimated to cover:

• expedited delivery charges if late,
• additional labour for re-sequencing work,
• or holding costs.

Without linking contingency to risk triggers, contingency becomes arbitrary and harder to defend in governance.

Estimating techniques: top-down vs bottom-up vs parametric

Most “Boston course” notes typically emphasise method selection. In exams, answers that show you understand when each method is appropriate tend to score higher.

Bottom-up estimating (preferred for control)

Bottom-up involves estimating each activity/work package and summing. Advantages:

• better accuracy
• clear assumptions per cost component
• easier to integrate with scheduling

Disadvantages:

• time-consuming
• depends on good WBS and activity definitions

Top-down estimating (useful early)

Top-down uses analogies or budget proportions derived from historical projects. Advantages:

• faster
• useful when scope is immature

Disadvantages:

• less reliable
• often weak traceability to work packages

Parametric estimating (model-based)

Parametric uses statistical relationships (e.g., cost per square meter, cost per unit, cost per person-hour). Advantages:

• repeatable
• good when historical data exists

Disadvantages:

• requires valid historical benchmarks
• can mislead if project context differs

Creating a budget baseline: the cost baseline and control accounts

A cost baseline is an approved time-phased budget used for comparing actual results. “Time-phased” is crucial: budgets must be distributed across time periods (weeks or months), not just given as a single total.

A simple budgeting baseline includes:

• Planned value (PV) per period
• Earned value (EV) later (used in integrated cost-schedule control)
• Cost performance measurement structure

In many curricula (including management and project management foundational modules), students learn budgeting first and then apply it in Earned Value Management (EVM). Even if your course doesn’t require EVM calculations, the conceptual linkage—planned vs actual vs earned—often appears in exam questions.

Case scenario: budgeting with scheduling awareness

A project to develop a small inventory system has these phases:

• Phase 1: Requirements and design
• Phase 2: Development
• Phase 3: Testing and deployment

Assume the project uses three roles:

• Business Analyst
• Software Developer
• QA Tester

If the scheduling plan puts requirements work in weeks 1–2, development in weeks 3–8, testing in weeks 9–10, and deployment in week 11, then time-phased budgets can align with labour availability.

If budgeting ignores schedule sequencing, you could budget the same total labour cost but allocate it all upfront—leading to cash flow stress and misleading variance reporting. Even when total cost is correct, the timing mismatch will distort performance control.

Budgeting outputs you should know (and be able to describe)

Typical exam outputs include:

• Budget estimate (total project cost)
• Cost breakdown structure (CBS) or cost accounts
• Cost baseline (time-phased)
• Budget assumptions and constraints
• Risk-related funding (contingency/reserve)
• Resource plan (labour/materials/equipment per activity)
• Procurement plan (purchase dates and cost instalments)

In short: budgeting creates an auditable model of how the project’s cost is expected to behave over time.

2) Scheduling Basics and Tools — From Activity Lists to Critical Path Logic

What scheduling really answers

Project scheduling translates scope into a timeline. The schedule defines:

• activities needed (what work is performed),
• sequence (what comes after what),
• duration (how long each activity takes),
• resources (who/what performs it),
• and constraints (deadlines, milestones, procurement lead times).

The schedule is therefore both a planning tool and a coordination tool. In the exam context, the schedule is often assessed via:

• correct activity dependencies,
• correct identification of critical activities,
• correct milestone logic,
• and correct interpretation of schedule variance.

Activity definition and sequencing

Scheduling begins with defining activities. The “activity” in scheduling is a work element that produces an output meaningful for planning and tracking. A poor activity definition leads to either:

• activities that are too large (not trackable), or
• activities that are too small (too much detail to control).

Then you define dependencies, usually in the form:

• Finish-to-Start (FS): activity B starts when A finishes.
• Start-to-Start (SS): activity B starts when A starts.
• Finish-to-Finish (FF): activity B finishes when A finishes.
• Start-to-Finish (SF) (rare): activity B finishes when A starts.

Most beginner exam questions use FS relationships.

Example dependency

For a system implementation project:

• “Write test cases” FS “Code development complete”
• “Deploy to production” FS “User acceptance testing complete”

Duration estimating: optimistic, most likely, and pessimistic

Even if your course is not deeply probabilistic, scheduling often references risk-informed duration estimates. A classic technique is three-point estimating:

• optimistic (a)
• most likely (m)
• pessimistic (b)

The expected duration can be computed using a weighted formula:

• te = (a + 4m + b) / 6

This helps incorporate uncertainty and reduces overconfidence in single-number durations.

Developing the network diagram: AON and AOA concepts (at exam level)

Network diagrams visually represent the project sequence. Students are often exposed to two formats:

• AON (Activity-on-Node): nodes are activities, arrows show precedence relationships.
• AOA (Activity-on-Arrow): arrows are activities, nodes represent events.

Exams in many South African universities typically focus on conceptually correct sequencing rather than notation mastery. If your question asks for the critical path, it is still essential to compute based on predecessor relationships and durations.

Critical Path Method (CPM): the heart of scheduling exams

The critical path is the longest path through the network in terms of duration. Activities on the critical path have:

• zero slack (no allowable delay without impacting project completion).

To compute critical path, you typically perform forward and backward passes:

1. Forward pass: compute earliest start (ES) and earliest finish (EF).
   • ES of start activity = 0 (or project start date)
   • EF = ES + duration
2. Backward pass: compute latest finish (LF) and latest start (LS).
   • LF of end activity = project completion time
   • LS = LF − duration
3. Slack/Float:
   • Slack = LS − ES = LF − EF

Even if you don’t show full arithmetic, exam questions often reward correct identification: “These activities have zero slack, therefore they form the critical path.”

Worked mini-example (compact but exam-valid)

Suppose a project has these activities:

Activity	Predecessor(s)	Duration (days)
A	—	3
B	A	2
C	A	4
D	B, C	2

Compute earliest times:

• A: ES=0, EF=3
• B: ES=3, EF=5
• C: ES=3, EF=7
• D: ES=max(B EF=5, C EF=7)=7, EF=9

Project duration = 9 days. Backward pass:

• D: LF=9, LS=7
• B: LF=LS of D=7, LS=5
• C: LF=7, LS=3
• A: LF=min(LS of B=5, LS of C=3)=3, LS=0

Slack:

• A: LS0 − ES0 =0 (critical)
• B: LS5 − ES3 =2 (not critical)
• C: LS3 − ES3 =0 (critical)
• D: 7−7=0 (critical)

Critical path = A → C → D, length 9 days.

Milestones and schedule baselines

Milestones mark significant events (e.g., “Requirements approved”, “UAT complete”, “Go-live”). A milestone schedule often aligns with decision points that require sign-off.

A schedule baseline is an approved time-phased plan used to evaluate performance. If schedule baseline is set, then later actual activity progress can be compared. This comparison is what enables schedule variance calculations or integrated cost/schedule control.

Constraints and calendars (where scheduling meets reality)

In real projects, durations are not simply calendar days. You must consider:

• working days vs non-working days (weekends, public holidays),
• shift patterns (e.g., night shifts),
• resource availability calendars,
• procurement lead times and delivery windows,
• internal approvals and review cycles.

Exams sometimes include a question where a planned duration “looks right” in network logic but fails due to calendar constraints. A high-scoring response explains that scheduling tools incorporate working time and constraints, not just duration arithmetic.

3) Integrating Budget and Schedule — Cost, Time, Variance, and Control (Including an Exam-Ready Earned Value View)

Why budgeting and scheduling must integrate

If budgeting and scheduling are treated separately, three failures commonly occur:

1. Cash flow mismatch: costs are incurred when the schedule is not aligned with procurement and labour release.
2. Misleading performance evaluation: you may declare “on budget” because total spending matches the budget, while scope completion lags behind schedule.
3. Incorrect decision-making: schedule delays trigger indirect costs and rework, but a separate budget may not reflect that dynamic.

Integrated project control addresses these failures by comparing:

• what was planned (PV),
• what was earned (EV, value of completed work),
• what was actually spent (AC, actual cost).

Even if you are not asked to run full EVM formulas, exams frequently test understanding of these concepts and the logic behind them.

Time-phasing and cost loading

A key integration practice is cost loading: distributing budgeted costs over the periods in which work is planned to occur.

Consider two projects with the same total budget:

• Project 1 front-loads procurement and early labour.
• Project 2 front-loads design and later labour.

Their totals match, but their time-phased spending differs. If you monitor “actual cost vs planned cost” without time-phasing, you might incorrectly flag a variance early and later “recover,” causing you to miss the real performance pattern.

Variance logic: schedule variance and cost variance

In EVM terms:

• Cost Variance (CV) = EV − AC
  • CV < 0 means you are over budget for the work earned.
• Schedule Variance (SV) = EV − PV
  • SV < 0 means you are behind schedule for the work earned.

Performance indices:

• Cost Performance Index (CPI) = EV / AC
  • CPI < 1 means poor cost efficiency.
• Schedule Performance Index (SPI) = EV / PV
  • SPI < 1 means behind schedule.

These relationships are common in exams because they provide quick diagnostic insight.

A full exam-style EVM scenario (with consistent numbers)

Assume a project for developing and deploying a municipal document tracking system. At the end of Week 6, the performance measurement shows:

• Budget at completion (BAC): ZAR 600,000
• Time-phased budget (PV) at Week 6: ZAR 300,000
• Earned value (EV) at Week 6: ZAR 240,000
• Actual cost (AC) at Week 6: ZAR 270,000

Compute:

1. CV = EV − AC = 240,000 − 270,000 = −ZAR 30,000
2. SV = EV − PV = 240,000 − 300,000 = −ZAR 60,000
3. CPI = EV / AC = 240,000 / 270,000 = 0.8889
4. SPI = EV / PV = 240,000 / 300,000 = 0.8000

Interpretation:

• Cost overrun for earned work (CPI < 1; CV negative).
• Behind schedule for earned work (SPI < 1; SV negative).

These interpretations are high-probability exam responses because they combine calculation and meaning.

Forecasting (what happens next)

A typical exam extension uses indices to forecast Estimate at Completion (EAC) and Estimate to Complete (ETC). One common approach is:

• EAC = BAC / CPI

Using CPI = 0.8889:

• EAC = 600,000 / 0.8889 ≈ ZAR 675,000

Meaning: you expect to spend about ZAR 675,000 instead of ZAR 600,000 due to current cost inefficiency (assuming performance continues similarly).

Another approach:

• ETC = EAC − AC = 675,000 − 270,000 = ZAR 405,000

These computations should be consistent with earlier values.

Schedule-corrective actions: what to do when SV is negative

When SV is negative, you are behind schedule. Corrective actions can include:

1. Re-sequencing work
   • compress critical path activities by adjusting dependencies.
2. Fast tracking
   • perform phases in parallel when possible (e.g., begin certain test planning before development fully complete).
3. Crashing
   • add resources to critical path activities (but increases cost).
4. Scope adjustment
   • renegotiate scope or remove non-critical deliverables if time is the dominant constraint.

The exam frequently asks for trade-offs. If you crash, cost variance may worsen initially, but schedule completion might improve.

Cost-corrective actions: what to do when CV is negative

When CV is negative, you are over budget relative to earned work. Corrective actions may include:

1. Resource leveling
   • reduce labour idle time and overtime.
2. Supplier renegotiation
   • correct procurement issues driving cost premiums.
3. Quality improvement
   • invest in preventing defects; reduces rework cost.
4. Scope control
   • change control to prevent uncontrolled scope creep.

Quality interventions deserve special attention because rework is often an invisible schedule-killer that also drives cost variance. Many exam graders value the recognition of this “two birds” effect: improved quality can help both schedule and cost.

Planning stability: baseline discipline and change control

Integrated control only works if baselines are stable. Therefore, students should understand:

• Scope baseline defines what work is included.
• Cost baseline defines budget distribution.
• Schedule baseline defines planned timeline.

If scope changes, you must perform formal changes to baselines (under change control), otherwise variance analysis becomes meaningless.

4) Resource Planning, Resource Levelling, and Scheduling Under Constraints (Labour, Equipment, and Procurement)

Why resource planning is the missing link in many “easy” schedules

A schedule that ignores resource capacity can look perfect on paper but fail operationally. For example:

• labour crew might only be available for 40 hours/week,
• equipment (e.g., scaffolding, testing equipment) might have limited availability windows,
• subcontractors might have lead times and constraints.

Resource planning ensures the schedule uses feasible resource allocation. Two common approaches are:

• Resource assignment: decide which resources perform each activity.
• Resource levelling: smooth resource usage to resolve overloads.

Identifying resource conflicts

Resource conflicts happen when multiple activities require the same resource simultaneously. Common signs:

• negative float (in some tools),
• unrealistic labour intensity,
• overtime beyond contractual limits,
• or equipment overbooking.

In exam scenarios, conflicts often appear in narrative form: “Two critical activities require the same technician and the technician can only work 5 days per week.”

A correct response explains:

• how conflicts are detected (capacity constraints),
• what scheduling rule is used (e.g., priority to critical path tasks),
• and how conflicts are resolved.

Resource levelling vs critical path: the trade-off

A crucial concept: levelling can change the schedule. When you level resources, you may delay some tasks to reduce peaks in demand. But if you delay critical path tasks, the project completion date can move.

Therefore:

• Levelling aims for feasibility.
• Critical path determines minimum duration under ideal constraints.

In practice, levelling may:

• shift the critical path,
• increase overall duration, or
• preserve completion date by rescheduling non-critical tasks only.

Exam questions often test that you understand this trade-off without oversimplifying.

Procurement and lead times: schedules that respect supply realities

Projects frequently rely on procurement. Procurement lead times create planning constraints such as:

• ordering windows,
• supplier delivery dates,
• installation readiness.

In scheduling, procurement activities are typically on the critical path when:

• delivery is time-limited,
• installation cannot start without receiving components,
• inspection and acceptance depend on delivered materials.

A strong exam answer includes:

• that procurement is a scheduled activity,
• that it should have duration and dependencies,
• and that it drives time-phased budget and cash requirements.

Detailed mini-case: scheduling and levelling with labour capacity

Assume a project involves two parallel tasks in Weeks 3–5:

• Activity E: “Electrical installation” requires 2 electricians for 3 weeks
• Activity F: “Security system configuration” requires 2 electricians for 2 weeks

If the electricians are available only for 2 electricians total concurrently, then E and F cannot both run full-time without conflict.

A resource-constrained schedule might do:

• run E in Weeks 3–4 (2 electricians),
• then run F in Week 5 (after E partially complete),
• or allow overlap with reduced electricians (if partial assignment is allowed).

In exam response terms, this means you would:

1. identify the overlap,
2. compare planned usage with capacity,
3. adjust sequencing or split activities (if technically feasible),
4. update schedule impacts on critical path.

Cost impacts of resource levelling

Resource levelling can affect costs in at least three ways:

1. Overtime reduction
   If you avoid overtime, you reduce labour premiums.
2. Opportunity cost and delay
   Delays may increase indirect costs (site overhead, project management overhead).
3. Productivity changes
   Starting and stopping work can reduce productivity. For example, electricians may require ramp-up time for each work package.

So resource levelling can reduce direct labour cost but still increase total cost due to schedule delays and overhead. Examiners appreciate answers that mention both effects.

Equipment constraints and the importance of calendar logic

Equipment constraints arise in many projects:

• cranes,
• lab testing equipment,
• vehicles,
• IT infrastructure environments.

If equipment is scarce:

• scheduling needs explicit equipment availability windows,
• the “duration” of tasks might include setup and teardown time,
• and buffers may be needed for equipment repair or maintenance.

In many university exam question stems, “equipment availability” appears as a narrative condition. A strong answer translates it into scheduling constraints that affect dependencies and durations.

Balancing scope, time, and cost (the triple constraint)

The triple constraint (scope-time-cost) is relevant because resource levelling is often a decision mechanism:

• If time is non-negotiable (e.g., a fixed launch date), you may allow overtime or subcontracting (higher direct costs).
• If cost is fixed, you might accept longer duration and delay completion.
• If scope is fixed, you manage time and cost via crashing/fast tracking or re-scoping.

Exams frequently use short narratives like “the client insists on completion by 30 June” and ask how you would respond. A high-scoring response ties the response to resource planning and change control.

5) Baselines, Monitoring, Updating Schedules, and Practical Control for Budget vs Time (Boston Course Exam Skills)

The control cycle: plan → execute → compare → correct

A robust project control system is cyclical:

1. Plan
   • create schedule baseline and cost baseline,
   • define measurement rules (how EV is earned),
   • establish reporting cadence.
2. Execute
   • perform work according to the plan,
   • capture actual progress and actual costs.
3. Compare
   • evaluate variances (schedule and cost),
   • interpret why variances occurred (root cause).
4. Correct
   • apply corrective actions (replan, crash, fast-track, resource changes),
   • update baselines only through change control.

This logic appears across project management short courses and introductory management modules because it is fundamental to governance.

Measuring progress correctly: EV measurement and “rules”

A common exam trap is misunderstanding progress measurement. For EV, you need a clear method. Common EV measurement approaches include:

• 0/100 method: no credit until completion of activity, then full EV.
• 50/50 method: credit 50% when work starts and 50% at completion.
• Percentage complete based on deliverables and evidence.
• Milestone-based: EV earned when milestones are achieved.

The best practice (and often the exam-preferred logic) is to use evidence-based measurement. Percentage complete should be supported by inspection results, test results, or sign-offs—not just “effort estimates.”

Schedule updating: what changes and what does not

Schedule updating is the process of reflecting actual progress and new estimates. But baselines should not be overwritten silently. Instead:

• the schedule baseline stays as the “approved plan” for variance comparisons,
• the current schedule is updated for realism,
• forecasts are produced for future outcomes.

In exams, if asked “what should be updated vs what should remain stable,” a clear baseline discipline answer scores well.

Forecasting and trend analysis: beyond one measurement date

Single-date variances are helpful but limited. Trend analysis improves decisions:

• If CPI is consistently below 1.0, cost risk increases.
• If SPI worsens over time, schedule risk increases.
• If variances improve, you may be recovering.

A well-structured exam answer includes that:

• performance trends should influence corrective actions,
• and that you should watch whether recovery is sustainable or temporary.

Root cause analysis: why variances happen matters

Variance numbers alone are not enough. You must interpret causes. Typical causes include:

• Planning errors: unrealistic durations, wrong resource assumptions
• Execution issues: poor productivity, poor coordination
• Change requests and scope creep: unplanned work introduced
• Procurement problems: late deliveries, wrong specifications
• Quality failures: rework increases both cost and time
• External events: strikes, weather, regulatory delays

In exam narrative answers, the best responses select likely root causes and connect them to schedule and budget mechanisms. For example:

• procurement problems usually drive schedule delays first and then cost overruns due to expediting or idle labour.

Change control: the governance layer connecting budget and schedule

Because baselines are approved plans, changes to scope, cost, or time must go through a change control process. A typical process includes:

1. Request (change request submitted)
2. Impact analysis
   • effects on schedule (which activities and whether critical path changes),
   • effects on cost (direct and indirect costs).
3. Decision
   • approve/reject/hold.
4. Implementation
   • update plans accordingly, then update baselines if approved.

In exams, change control questions often ask:

• who is responsible (project manager, steering committee),
• what information must be included (impact on cost and time),
• and what happens if changes are implemented without approval (baselines become invalid).

Reconciling cash flow with schedule: practical budgeting insights

Budget variance analysis is sometimes misunderstood as “cash spent” only. In reality:

• costs can accrue when work is performed,
• invoices might be issued later,
• procurement instalments might be tied to delivery,
• labour costs might depend on attendance and payroll cycles.

Therefore, schedule affects payment timings, and budgeting should consider cash flow planning separately when required. In many exam questions, however, the simpler “time-phased budget” view is used as a proxy for cash flow.

Still, the exam-grade conceptual response:

• planned spending follows planned work,
• delays shift planned spending to later periods,
• and early procurement can increase early cash requirement even if final total cost stays similar.

Worked integrated example: schedule delay leading to cost overrun

Using earlier EVM Week 6 snapshot values:

• PV = ZAR 300,000
• EV = ZAR 240,000
• AC = ZAR 270,000
• CPI = 0.8889, SPI = 0.8

Suppose the root cause is a delivery delay of a key component taking 1.5 weeks. That delay pushes subsequent activities on the critical path. As a result:

• EV is behind because work expected by Week 6 is not completed.
• AC is higher because the team paid expedited shipping and retained labour despite idle time.

This matches the signs:

• SV = −ZAR 60,000 (behind schedule)
• CV = −ZAR 30,000 (over budget for earned work)

Now corrective actions might include:

• negotiating revised delivery windows,
• re-sequencing non-critical tasks to consume time without increasing critical path delay,
• adjusting resource assignments to reduce overtime,
• applying fast tracking if technical dependencies permit.

In an exam, the examiner expects you to connect the narrative cause to the quantitative outcomes—not treat them as separate topics.

Common exam questions and high-scoring answer patterns

Because these notes align with typical exam-style questions (including introductory management and project scheduling/budgeting modules), the following answer patterns are effective:

1. If asked to define budgeting and scheduling
   • Define budgeting: estimate + time-phased baseline + control.
   • Define scheduling: activity sequencing + durations + dependencies + baseline.
2. If asked to compute critical path
   • Show forward pass earliest times.
   • Show backward pass latest times.
   • Compute slack and identify zero-slack activities.
3. If asked to interpret EVM variances
   • Calculate CV and SV with correct sign.
   • Interpret CPI and SPI.
   • Mention plausible root causes and corrective actions.
4. If asked about resource constraints
   • Explain conflict detection.
   • Explain resource levelling and its impact on critical path.
   • Mention cost-time trade-offs.

Quality assurance and review points: keeping schedule realistic

Realistic scheduling includes review and quality gates. Examples:

• design approval gate before procurement,
• inspection and acceptance before installation,
• user acceptance testing sign-off before deployment.

These gates often act like “dependencies,” even if not drawn as strict technical dependencies. In exams, you can add value by describing them as:

• scheduled approval milestones,
• risk-reducing mechanisms,
• and contributors to schedule buffers.

Buffer management: preventing schedule collapse

Buffers are often used informally, but good practice treats buffers as part of planning. Two concepts:

• Time buffers: additional time to absorb uncertainty (e.g., float, reserves).
• Risk-based buffers: contingency for identified risks.

If the schedule has insufficient buffers, minor delays can cascade into major schedule slippage. Budget control then suffers because rework and corrective action costs increase.

In exam responses:

• avoid describing “buffers” as an excuse for poor planning,
• describe buffers as mitigation tied to risks or uncertainty.

Final integrated checklist: what you must be able to do in the exam

A strong Boston course–style exam answer on budgeting and scheduling should include competency in:

• Budgeting

  • create a WBS-aligned cost breakdown,
  • identify direct vs indirect costs,
  • include contingency vs management reserve logic,
  • build a time-phased cost baseline.

• Scheduling

  • define activities,
  • specify dependencies and durations,
  • compute critical path and slack,
  • interpret milestones and baselines.

• Integration

  • explain PV, EV, AC concepts,
  • compute CV/SV and interpret CPI/SPI,
  • forecast EAC using CPI when asked,
  • propose corrective actions (crashing/fast tracking/re-sequencing) with trade-offs.

• Control

  • update schedules without overwriting baselines,
  • measure progress using evidence-based EV rules,
  • apply change control with impact analysis.

Quick Reference Table: Key Terms You Should Recognize Instantly

Term	Meaning	Typical Exam Focus
WBS	Work Breakdown Structure	Linking scope to activities/costs
Work package	Smallest planned unit of work	Estimation and traceability
Cost baseline	Time-phased approved budget	Variance comparisons (planned vs actual)
Schedule baseline	Approved timeline	Updating current schedule correctly
Dependencies	Precedence relationships	Correct network logic and critical path
Critical path	Longest duration path	Identify zero slack activities
Slack/Float	Allowable delay without affecting completion	Critical vs non-critical determination
PV	Planned Value	Schedule/cost integration
EV	Earned Value	Value of completed work
AC	Actual Cost	Cost performance measurement
CV, SV	EV−AC, EV−PV	Sign interpretation and meaning
CPI, SPI	EV/AC, EV/PV	Efficiency and trend indicators
Contingency vs reserve	Risk-based vs management-unforeseen	Distinction and governance logic

These notes provide the budgeting and scheduling logic expected in project management short-course assessments and introductory university modules (including MNG 0001–type management foundations). The emphasis is on exam-ready reasoning: define key concepts, compute where required, interpret results, and propose realistic corrective actions under constraints—exactly how budgeting and scheduling operate together in real projects at Boston City Campus.