HKSM

Ongoing oversight of people, equipment, materials, facilities, and services to ensure they are available when needed, used effectively, and adjusted as conditions change, keeping the project within approved scope, schedule, and cost.

Purpose & When to Use

• Ensure the project has the right resources at the right time and cost, and that utilization supports value delivery and flow.
• Track actual capacity and consumption against the resource plan and baselines, and correct variances quickly.
• Apply across all delivery approaches: predictive, agile, and hybrid, from initiation through closing.
• Use more frequently during delivery, at iteration planning, before major milestones, when supplier risks emerge, or after scope or schedule changes.

Mini Flow (How It’s Done)

• Review current plans and constraints. Gather the resource plan, calendars, skills matrix, procurement schedules, WIP limits, budget run-rate, and team capacity or velocity.
• Collect performance data. Monitor availability, utilization, overtime, absenteeism, supplier deliveries, inventory, tool or license access, and burn-up or burn-down trends.
• Compare against plan. Perform variance and trend analysis on capacity versus demand, and identify bottlenecks, over-allocation, or underutilization.
• Analyze causes and options. Use root cause analysis, what-if scenarios, and cost or schedule impact assessments to evaluate reallocation, cross-training, resequencing, resource leveling or smoothing, backlog prioritization, or alternate sourcing.
• Decide and implement. Coordinate with functional managers and vendors to acquire, reassign, or release resources, expedite deliveries, adjust WIP limits, update access and logistics, and communicate changes to the team.
• Control changes. If baselines are affected, raise a change request, obtain approval through integrated change control, and update the schedule, cost, and resource plan.
• Verify and learn. Confirm the action resolved the variance, close related issues or risks, update lessons learned, and refine forecasting for future periods.

Quality & Acceptance Checklist

• Resource data and calendars are current, including holidays, part-time allocations, and vendor lead times.
• All critical roles and materials have named sources, backups, and coverage for key dates.
• Utilization is within agreed thresholds, with no sustained over-allocation or systemic idle time.
• Capacity forecasts reflect skill mix, onboarding time, attrition, and learning curves.
• Non-people resources such as tools, environments, test rigs, and licenses are sized, funded, and available with access granted.
• Supplier commitments, SLAs, and delivery windows are tracked, with realistic buffers for variability.
• Budget consumption for resources aligns with earned value and run-rate targets, and overtime costs are visible.
• Health, safety, security, and regulatory constraints related to resources are met.
• Release and handback plans exist for resources no longer needed, including asset return and knowledge transfer.
• Required changes to baselines follow formal change control, and all stakeholders are informed of approved adjustments.

Common Mistakes & Exam Traps

• Treating resourcing as a one-time staffing event instead of continuous monitoring and adjustment.
• Looking only at people while ignoring materials, equipment, facilities, and services.
• Jumping to schedule fixes without addressing the true resource constraint or bottleneck.
• Implementing informal reallocations that change cost or schedule without change control.
• Confusing resource leveling with smoothing; leveling changes dates to remove over-allocation, while smoothing keeps dates but may not fully resolve overloads.
• Defaulting to overtime or adding people when a non-people resource is the constraint.
• Failing to update resource calendars, access, and logistics, causing avoidable delays at task start.
• Assuming suppliers can always expedite without cost or quality impacts.
• Holding resources after their need ends, increasing cost and reducing organizational availability.
• In agile settings, micromanaging individual allocations instead of enabling the team to self-organize within capacity and WIP limits.

PMP Example Question

A specialized test rig from a vendor will arrive two weeks late, threatening a critical milestone. The project manager plans to fast-track tasks and ask the team for overtime. What should the project manager do first?

1. Submit a change request to extend the schedule.
2. Analyze options to address the constraint, such as resequencing work, renting a temporary rig, or adjusting WIP, and assess impacts.
3. Add more testers to the team to recover the schedule.
4. Update the risk register and proceed with overtime.

Correct Answer: B — Analyze options to address the constraint, such as resequencing work, renting a temporary rig, or adjusting WIP, and assess impacts.

Explanation: In monitoring and controlling resourcing, identify the root constraint and evaluate alternatives before implementing changes or requesting baseline updates. Overtime or adding people does not fix a missing non-people resource.