HKSM

Resource management is the analysis and coordination of people, equipment, and materials to meet project objectives within schedule and budget. It balances demand and capacity, resolves conflicts, and optimizes allocation using techniques like resource leveling and smoothing.

Key Points

• Aligns resource demand with available capacity across people and physical assets.
• Uses calendars, skills data, and availability to detect overallocations and bottlenecks.
• Applies techniques such as resource leveling, resource smoothing, and what-if scenario analysis.
• Generates artifacts like a resource breakdown structure (RBS), RACI, resource histograms, and updated schedules.
• Iterative throughout the project; updates plans, budgets, risks, and procurement needs.
• Requires negotiation with functional managers and transparent stakeholder communication.

Purpose of Analysis

Ensure the right resources, with the right skills and capacity, are available at the right time to deliver scope within agreed constraints. Reduce delivery risk by identifying conflicts early, evaluating options, and selecting an allocation strategy that best supports value, schedule, and cost goals.

Method Steps

• Capture demand: derive resource needs from WBS, activity list, and estimates.
• Profile capacity: compile calendars, skills, FTE availability, equipment uptime, and vendor lead times.
• Map demand to capacity: create RAM/RACI, resource histograms, and loading by time period.
• Identify gaps and conflicts: find overallocations, single points of failure, and physical resource constraints.
• Model options: run what-if scenarios, apply resource leveling or smoothing, re-sequence work, or consider make-or-buy.
• Select and plan: choose a strategy, update the schedule, costs, and procurement approach; document decisions and assumptions.
• Agree and monitor: confirm with stakeholders and functional managers; track utilization and adjust as conditions change.

Inputs Needed

• Scope baseline, WBS, activity list, and effort/duration estimates.
• Project schedule (draft), milestones, and dependencies.
• Resource calendars, skills inventory, org charts, and FTE limits.
• Physical resource lists, capacities, maintenance windows, and lead times.
• Budget constraints, cost rates, make-or-buy guidance, and procurement policies.
• Risk register, assumptions and constraints log, and stakeholder commitments.

Outputs Produced

• Resource management approach (roles, acquisition, development, and control strategy).
• Resource requirements by activity and time period (staffing profile and equipment needs).
• Responsibility assignment matrix (e.g., RACI) and resource breakdown structure (RBS).
• Resource histograms, allocation reports, and leveling/smoothing decisions.
• Updated schedule with resource-constrained dates and critical path impacts.
• Cost updates (labor/materials), procurement requests, and change requests if baselines shift.

Interpretation Tips

• Watch for sustained overallocations in histograms; short spikes may be solvable with smoothing.
• Check how leveling affects the critical path and float; confirm stakeholders accept any delays.
• Evaluate cost-time trade-offs before crashing or adding resources; consider diminishing returns.
• Validate assumptions about availability (do not assume 100% productive time).
• Address skill gaps early through training, cross-skilling, or external sourcing.
• Revisit analysis at each planning update, major change, or performance variance.

Example

A project requires two senior analysts for Activities A and B scheduled in the same week. The histogram shows both analysts at 150% allocation. The team models options: level resources by delaying Activity B one week, split Activity B across two weeks, or bring in a contractor. Leveling pushes the finish by three days but avoids cost increase; the sponsor accepts the minor schedule impact.

Pitfalls

• Ignoring non-human resources (tools, rooms, test environments) that also constrain work.
• Assuming full-time availability and overlooking meetings, leave, or multitasking losses.
• Relying on a single specialist without a backup plan or cross-training.
• Not updating calendars and skills data, leading to unrealistic allocations.
• Applying leveling without communicating schedule impacts to stakeholders.
• Delaying procurement decisions and missing lead times for critical equipment or services.

PMP Example Question

Midway through planning, you discover two critical activities require the same scarce specialist at the same time, causing an overallocation and potential delay. What should you do first?

1. Crash the schedule by authorizing overtime for the specialist.
2. Fast-track the activities to overlap them further and gain time.
3. Perform resource analysis and leveling to model options and discuss impacts with stakeholders.
4. Update the risk register and proceed without changing the plan.

Correct Answer: C — Perform resource analysis and leveling to model options and discuss impacts with stakeholders.

Explanation: The best first action is to analyze the conflict, run what-if and leveling scenarios, and then communicate outcomes for an informed decision. Crashing or fast-tracking should follow only after analysis confirms they are viable.