HKSM

A resource management plan explains how the project will identify, acquire, organize, develop, and manage both team and physical resources. It defines roles, decision rights, calendars, and methods to monitor, adapt, and resolve resource issues across the life cycle.

Definition

A resource management plan is a component of the project management plan that sets out the approach for securing, coordinating, and governing people and physical resources so the right capabilities are available at the right time and cost.

Key Points

• Covers both team members (skills, roles, authority) and physical resources (equipment, facilities, materials).
• Aligns with schedule, budget, risk, procurement, and stakeholder engagement plans.
• Created early and refined as estimates mature; significant changes follow change control.
• Clarifies decision rights and handoffs using tools like RACI and team charters.
• Tailored to the delivery approach (predictive, iterative, agile, or hybrid).
• Defines resource calendars, onboarding, release plans, and conflict resolution mechanisms.

Purpose

• Ensure the project has the right people, tools, and materials when needed.
• Set clear expectations for roles, responsibilities, and authority.
• Prevent resource conflicts and over-allocation across teams and functions.
• Provide a basis for developing, engaging, and retaining the project team.
• Support monitoring, reporting, and corrective actions for resource performance.

Typical Sections

• Resource strategy and approach (build, buy, borrow; insource vs. outsource).
• Team structure, roles, responsibilities, and authority levels.
• RACI or similar responsibility assignment matrix.
• Staffing plan: acquisition, onboarding, ramp-up, and release criteria.
• Resource calendars and availability constraints.
• Skills and competency requirements; training and coaching plan.
• Team norms, engagement, recognition, and well-being practices.
• Physical resource plan: equipment, materials, facilities, and logistics.
• Interfaces with HR, procurement, vendors, and shared services.
• Compliance, safety, and environmental considerations.
• Monitoring and control: KPIs, capacity/utilization metrics, reports, and meetings.
• Conflict resolution, escalation paths, and decision-making rules.

How to Create

• Review inputs: charter, scope and WBS, schedule milestones, budget limits, organizational policies, and risks.
• Define resource strategy: make-or-buy, sourcing channels, and engagement model (predictive vs. agile teams).
• Identify roles and competencies, then draft an org chart and a RACI matrix.
• Plan acquisition and onboarding timelines aligned to the schedule and funding gates.
• Plan team development: training, coaching, feedback cadence, and recognition mechanisms.
• Specify physical resource needs, lead times, and logistics; coordinate with procurement and facilities.
• Set up resource calendars, availability constraints, and release criteria.
• Define monitoring and control: metrics (e.g., capacity, utilization, vacancy rate), reports, and escalation.
• Tailor for the delivery approach and integrate with schedule, cost, risk, and procurement plans; obtain approval.

How to Use

• Guide staffing, onboarding, and release decisions throughout the project.
• Communicate roles, decision rights, and collaboration norms to all team members.
• Coordinate with functional managers and vendors to resolve allocation conflicts.
• Plan and track resource utilization, capacity, and skills coverage against milestones.
• Trigger risk responses and change requests when resource assumptions change.
• Support performance feedback, coaching, and team health actions.

Maintenance Cadence

• Review at phase gates, major backlog reordering, or quarterly planning events.
• Assess after organizational changes, vendor shifts, or significant risk outcomes.
• Update at least monthly in predictive projects; per iteration in agile or hybrid.
• Process material changes through integrated change control and communicate updates promptly.

Example

Excerpt from a resource management plan for a mid-size project:

• Team structure: 1 project manager, 1 business lead, 2 analysts, 4 developers, 1 tester; PM holds day-to-day decision authority within approved constraints.
• RACI: Requirements (Business Lead - Accountable; Analysts - Responsible; PM - Consulted; Sponsor - Informed).
• Staffing plan: Two developers onboard in Month 1, two in Month 2; tester added before System Test; release developers after deployment plus two-week warranty.
• Calendars: Core hours 9:00–15:00 local; no weekend work; vendor equipment delivery requires 10 business days lead time.
• Team development: Peer reviews weekly; training on tool X in Week 3; monthly recognition at sprint review.
• Monitoring: Weekly capacity vs. planned burn; vacancy rate under 5%; escalate conflicts to sponsor if unresolved within 2 working days.

PMP Example Question

A functional manager assigns team members to multiple projects, causing over-allocation just as execution begins. What should the project manager do first?

1. Submit a change request to extend the schedule.
2. Escalate immediately to the sponsor for a decision.
3. Review and use the resource management plan to engage the functional manager and realign staffing and calendars.
4. Hire external contractors to replace the over-allocated team members.

Correct Answer: C — Review and use the resource management plan to engage the functional manager and realign staffing and calendars.

Explanation: The plan defines roles, acquisition, calendars, and conflict resolution methods. Apply the agreed approach before escalating or changing scope, time, or cost.