HKSM

Key Points

• Describes what resources are needed, in what quantities, and when they are required across the life of the project.
• Covers labor and non-labor resources such as team roles, equipment, materials, supplies, and facilities.
• Expresses needs in measurable units (for example, person-hours, FTEs, quantity, capacity) and is often time-phased.
• Informs staffing plans, cost estimates, procurement strategy, and resource leveling or smoothing.
• Is developed iteratively and updated as scope, schedule, risks, and constraints evolve.
• Should include the basis of estimate, assumptions, and constraints for traceability and decision-making.

Purpose of Analysis

• Translate the scope and activity work into specific, quantifiable resource needs to enable feasible planning.
• Align demand for people and assets with availability, calendars, and organizational or vendor constraints.
• Provide inputs to cost and schedule models, including resource-driven durations and time-phased budgets.
• Surface risks, dependencies, and procurement lead times early to reduce later delays and rework.

Method Steps

• Review scope, WBS, and activity list to identify the work that drives resource demand.
• Classify required resources by type (people, equipment, materials, facilities) and by role or specification.
• Estimate quantities and effort using expert judgment, analogous, parametric, or bottom-up techniques.
• Apply calendars and availability to convert effort into capacity needs (for example, FTEs per period) and time-phase the demand.
• Validate practicality with resource owners or vendors; consider make-or-buy and skill availability.
• Document the basis of estimates, assumptions, and constraints; capture risks and issues found.
• Consolidate into a resource requirements list and, if useful, a resource breakdown structure and histogram.
• Integrate with schedule and cost planning; iterate as plans are adjusted or risks materialize.

Inputs Needed

• Scope baseline, WBS, and activity list with attributes.
• Resource calendars, organizational policies, skill catalogs, and role descriptions.
• Historical data, lessons learned, and reference class benchmarks.
• Cost rates, vendor catalogs, and procurement strategy or contracts.
• Assumptions log, constraints, risk register, and stakeholder requirements.

Outputs Produced

• Documented resource requirements by activity or work package, time-phased where applicable.
• Role descriptions or skill requirements and quantity takeoffs for materials and equipment.
• Resource breakdown structure and resource histograms or demand profiles.
• Basis of estimate and updates to the assumptions log and risk register.
• Inputs to staffing management, procurement planning, schedule development, and cost estimating.

Interpretation Tips

• Differentiate effort from duration; availability and calendars determine how effort translates into time.
• Use generic roles early (for example, Senior Analyst) and assign named individuals later to maintain flexibility.
• For non-labor items, specify quantity, performance specs, and lead times to support procurement and logistics.
• Check for peaks in demand; plan resource leveling or staged deliveries to avoid overloads and idle time.
• Validate with resource owners and vendors to confirm feasibility and identify constraints or alternatives.

Example

For a 12-week initiative, the team analyzes each work package and derives the following time-phased needs:

• Analysis: 2 Business Analyst FTEs for weeks 1-4; 1 Architect at 50% for weeks 2-3.
• Build: 3 Specialist FTEs for weeks 5-9; 1 test environment for weeks 6-10; 200 units of consumables by week 5.
• Pilot and rollout: 1 Trainer FTE for weeks 10-12; 10 loaner devices for week 11; a training room for 3 days.

These requirements feed the staffing plan, reserve the environment, and trigger a purchase order for consumables with a 3-week lead time.

Pitfalls

• Listing headcount without units or time-phasing, making integration with schedule and cost unreliable.
• Ignoring calendars, lead times, or onboarding time, which inflates risk of delays.
• Underestimating non-labor resources (facilities, licenses, materials) and focusing only on people.
• Failing to capture the basis of estimate, hindering future refinement and stakeholder trust.
• Double-counting shared resources across activities or not accounting for multitasking limits.
• Skipping validation with resource owners or vendors, leading to infeasible plans.

PMP Example Question

While estimating resource requirements for each activity, the team needs to express labor needs in a way that supports scheduling and cost estimating. What is the best practice?

1. Record headcount by name for the entire project duration.
2. Document effort and capacity using units such as person-hours or FTEs and time-phase them.
3. Estimate only critical path activities since noncritical work can be adjusted later.
4. Defer non-labor resources to procurement planning.

Correct Answer: B — Document effort and capacity using units such as person-hours or FTEs and time-phase them.

Explanation: Quantified, time-phased requirements integrate cleanly with calendars, cost rates, and scheduling. The other options reduce accuracy or delay important planning for non-labor needs.