WHY THIS MATTERS TO YOU

Every project runs on three things: people, time, and money. You can usually trade one for another up to a point, but all three have limits. When a project is behind schedule, the answer is rarely just ‘work harder.’ It is a resource problem with a resource solution.

This module covers how resources are planned, how budgets are built, and what to do when the plan meets reality.

Resource Planning Basics

Resource planning means identifying what you need (people with specific skills, equipment, facilities, materials) and when you need it. For BA and consultant work, resources are almost always people. The key questions are: who is needed, for how long, at what cost, and are they available?

Resource Type	Examples in Implementation Projects	Common Planning Error
Human – Client	Subject matter experts, UAT testers, data owners	Assuming they will be available full-time; they have day jobs
Human – Consultant	BA, PM, developer, trainer	Booking without confirming actual availability
System	Test environment, sandbox access, data extract tools	Assuming environments will be ready when needed
Vendor	Software vendor support, hardware delivery	Not accounting for vendor lead time in the schedule

Estimating Effort vs. Duration

Effort is the total amount of work time required. Duration is the calendar time the task takes. These are not the same. A task that requires 20 hours of effort might take two weeks in duration if the person doing it is only available 50% of the time.

Most BAs estimate effort. The PM converts effort to duration based on resource availability. Both estimates need to be realistic. Effort estimates should account for meetings, rework, and review cycles, not just the time when someone is actively producing the deliverable.

PMP / PMBOK NOTE

The PMBOK Guide covers several estimating techniques: analogous estimating (based on past projects), parametric estimating (unit-rate based), bottom-up estimating (roll up from work packages), and three-point estimating (optimistic, pessimistic, and most likely). The PMP exam tests when to use each and how three-point estimating calculates expected duration: (O + 4M + P) / 6.

Building a Budget

A project budget is built from the bottom up: estimate the effort for each work package, apply resource rates, add non-labor costs (licenses, travel, equipment), and then add a contingency reserve for identified risks and a management reserve for unknown unknowns.

• Direct labor cost: hours x hourly rate per resource
• Vendor and software costs: license fees, implementation fees
• Travel and expenses: on-site work, training delivery
• Contingency reserve: buffer for known risks (in the budget baseline)
• Management reserve: buffer for unknown risks (above the baseline, controlled by sponsor)

PMP / PMBOK NOTE

The PMP exam distinguishes between the cost baseline (the approved budget) and the project budget (cost baseline plus management reserve). Contingency reserve is part of the baseline. Management reserve is not. Cost performance is measured against the baseline using Earned Value Management (EVM), which is covered more in Module 12.

Resource Leveling and Smoothing

When multiple tasks demand the same resource at the same time, you have a resource conflict. Resource leveling resolves the conflict by adjusting task start and end dates, which may extend the schedule. Resource smoothing adjusts tasks within their available float so the schedule end date does not change.

Resource Leveling	Resource Smoothing
May extend the project end date	Does not extend the project end date
Resolves over-allocation completely	May not fully resolve over-allocation
Used when resource limits are hard constraints	Used when schedule is the priority
Can shift critical path tasks	Only shifts tasks with available float

 

WHAT THEY SAY	WHAT THEY MEAN
Can we just add more people?	Adding resources to a late project often slows it down initially due to onboarding; Brooks’s Law says adding people to a late project makes it later
Our SMEs are only available two days a week	This is a resource constraint that must be reflected in the duration estimates, not assumed away
We did not budget for that	Either it is a scope change (requires change control) or the estimate was wrong (requires re-baselining)
What is the contingency for?	Contingency covers known risks; it is not free money to spend on scope additions

COMMON MISTAKE

MISTAKE: Estimating effort based on ideal conditions and ignoring availability.

What it looks like: The BA estimates 40 hours for a requirements workshop series and assumes the client SMEs will participate for four full days. In reality, the SMEs have 60% availability. The workshops take 6.5 days instead of four, and everything downstream shifts.

Reality: Always estimate based on actual availability. Confirm calendars before finalizing estimates, especially for client-side resources who have operational responsibilities.

QUESTIONS TO ASK YOUR STAKEHOLDER

1. Who are the key resources on this project, and what is their confirmed availability percentage?
2. Has the budget been built from work package estimates, or was it set top-down before estimates existed?
3. What is the contingency reserve, and what risks is it sized to cover?
4. Are client-side SMEs formally committed to the project, or is their participation informal?
5. Are there any shared resources who are also assigned to other projects running in parallel?

Module Quiz

1. A task requires 40 hours of effort. The assigned resource is available 50% of the time. What is the expected duration?

1. 40 hours
2. 20 hours
3. Two weeks (approximately 80 hours of calendar time)
4. Four weeks

Answer: 3

Why it matters: At 50% availability, the person can work 20 hours per week on this task. 40 hours of effort divided by 20 hours/week = two weeks duration.

2. In PMBOK, management reserve differs from contingency reserve in that:

1. Management reserve is for known risks; contingency is for unknown risks
2. Contingency is part of the cost baseline; management reserve is above it and controlled by the sponsor
3. They are the same thing
4. Management reserve is set by the PM; contingency is set by the BA

Answer: 2

Why it matters: Contingency is in the baseline for identified risks. Management reserve sits above the baseline and is controlled at the sponsor level for true unknowns.

3. Brooks’s Law states that:

1. Adding more resources always speeds up a project
2. Adding people to a late project makes it later
3. Project duration is fixed regardless of resources
4. Resources should be added before a project is late

Answer: 2

Why it matters: New team members need onboarding and create coordination overhead. Adding people mid-project typically slows things down before it speeds them up.

4. The three-point estimate formula in PMBOK is:

1. (O + M + P) / 3
2. (O + 4M + P) / 6
3. (O + P) / 2
4. (2O + M + 2P) / 5

Answer: 2

Why it matters: The PERT formula weights the most likely estimate four times more than optimistic or pessimistic to produce a more realistic expected duration.

5. Resource leveling may result in:

1. A shorter project end date
2. Extending the project end date to resolve resource conflicts
3. Lower costs
4. Removing tasks from the schedule

Answer: 2

Why it matters: Resource leveling resolves over-allocation by shifting tasks, which can push the project end date out. It is a deliberate trade-off.