HKSM

Documented changes to organizational and external conditions identified while securing team and physical resources. Typical items include resource availability, market labor rates, vendor capacity, facility constraints, and regulatory lead times that affect staffing and procurement.

Key Points

• Output of Acquire Resources capturing shifts in the environment that affect how resources can be obtained and used.
• Reflects conditions not directly controlled by the project, such as market supply, labor rates, union rules, and facility capacity.
• Feeds enterprise-level references so future projects and functions (HR, procurement, facilities) make informed decisions.
• Distinct from OPA updates, which cover policies, procedures, and templates; EEF updates describe prevailing conditions.
• May trigger related actions, such as adjusting estimates, negotiating with vendors, or updating the risk register.

Purpose

Ensure the organization has an accurate, current view of factors that influence acquiring and managing resources. This reduces surprises, supports realistic plans and budgets, and improves negotiation leverage across projects.

• Promote consistent enterprise decisions based on current market and capacity conditions.
• Shorten lead times by surfacing constraints early to functional owners.
• Improve cost, schedule, and risk forecasts related to staffing and equipment.

How to Create

• Capture evidence during sourcing and onboarding: vendor quotes, HR candidate pipeline data, facility capacity notices, regulatory lead times.
• Validate with authoritative sources (HR, procurement, legal, facilities, vendors) to confirm scope, location, and timeframe of the condition.
• Classify as EEF (external or internal condition) versus OPA (policy/procedure) to avoid misrouting.
• Draft an update record with description, date observed, data source, affected resource categories, geographic scope, and expected duration.
• Note project impact (cost/schedule/risk) and recommended enterprise action (e.g., new supplier pool, alternate location, rate guidance).
• Submit to the owning function and PMO for inclusion in enterprise references and communicate to impacted stakeholders.

How to Use

• Refine recruiting and vendor strategies using updated availability, lead times, and rate guidance.
• Adjust cost estimates and schedules for staffing, equipment delivery, and facility access windows.
• Update risk responses when scarcity or constraints raise probability or impact.
• Inform make-versus-buy decisions and location choices for co-location, remote, or hybrid models.
• Coordinate with other projects to stagger demand when capacity limits are enterprise-wide.

Ownership & Update Cadence

• Ownership: HR/Talent Acquisition (labor availability and rates), Procurement/Vendor Management (supplier capacity), Facilities/IT Operations (space and infrastructure capacity), Legal/Compliance (regulatory lead times), PMO (coordination and visibility).
• Cadence: As-needed when new conditions are discovered during negotiations, onboarding, or facility scheduling; periodic enterprise reviews (e.g., quarterly) to consolidate and publish updates.
• Triggers: Major contract awards, regulatory changes, market shifts, supply disruptions, or seasonal capacity swings.

Example

While staffing a cloud migration, vendors report a 10–12 week lead time for GPU servers in the region, and recruiters confirm a 15% quarter-over-quarter increase in contract cloud architect rates. The project logs EEF updates describing the regional hardware lead time and market rate change, cites sources, scope, and expected duration, and routes them to Procurement and HR. These updates prompt revised rate guidance and an alternate supplier search for future projects.

PMP Example Question

During Acquire Resources, you learn the on-site lab is at full capacity for the next two months and local contract engineers are scarce, driving rates up. What should you update to reflect these enterprise-level conditions?

1. Organizational process assets with a new onboarding checklist.
2. A change request to modify the resource management plan only.
3. Enterprise environmental factor updates capturing capacity limits and market scarcity.
4. The issue log only, since this is a project-specific problem.

Correct Answer: C — Enterprise environmental factor updates capturing capacity limits and market scarcity.

Explanation: Lab capacity and labor market conditions are environment factors outside the project’s control and should be recorded as EEF updates. OPAs cover policies and templates, while an issue log entry alone would not update enterprise-wide references.