5.1 Resource Management
Key Takeaways
- Resource management covers both human resources (the project team) and physical resources (materials, equipment, facilities); CAPM tests them as one knowledge area split across six processes.
- A RACI chart (Responsible, Accountable, Consulted, Informed) needs exactly ONE Accountable and at least ONE Responsible per activity; multiple A's is the classic wrong setup.
- Resource leveling resolves over-allocation and MAY extend the schedule (it can change the critical path); resource smoothing stays within free/total float and never extends the end date.
- Tuckman's ladder (Forming, Storming, Norming, Performing, Adjourning) is not strictly linear; adding members or losing a leader can drop a team back to Storming or Forming.
- Herzberg's hygiene factors (salary, conditions, security) only prevent dissatisfaction; motivators (achievement, recognition, growth) are what actually drive performance.
What Resource Management Covers
Resource management is the knowledge area that identifies, acquires, develops, and controls everything a project consumes. The CAPM Exam Content Outline folds this into Domain 1 (Project Management Fundamentals, 36% of the exam), so it is heavily weighted. Two resource families exist: human resources (team members, their skills, availability, and behavior) and physical resources (materials, equipment, facilities, and infrastructure). The CAPM expects you to treat them as one area but apply different tools to each.
| Process | Process Group | Purpose |
|---|---|---|
| Plan Resource Management | Planning | Define how resources are estimated, acquired, managed, released |
| Estimate Activity Resources | Planning | Determine type and quantity of resources per activity |
| Acquire Resources | Executing | Obtain team members and physical resources |
| Develop Team | Executing | Raise competencies, interaction, and overall team environment |
| Manage Team | Executing | Track performance, give feedback, resolve conflict |
| Control Resources | Monitoring & Controlling | Ensure physical resources arrive and perform as planned |
Note the split: Develop Team and Manage Team apply only to people, while Control Resources applies only to physical things. A common trap question asks which process handles "a delivery of steel arriving late" — the answer is Control Resources, not Manage Team.
The RACI Chart
A RACI chart is a type of Responsibility Assignment Matrix (RAM) that maps people to activities. The four roles are:
| Letter | Role | Rule |
|---|---|---|
| R — Responsible | Does the actual work | At least one R per activity |
| A — Accountable | Has final approval and answerability | Exactly one A per activity |
| C — Consulted | Provides input via two-way dialogue | Optional, can be several |
| I — Informed | Kept updated via one-way communication | Optional, can be many |
| Activity | Project Manager | Business Analyst | Developer | Sponsor |
|---|---|---|---|---|
| Define Requirements | A | R | C | I |
| Design Solution | C | A | R | I |
| Approve Deliverable | R | C | I | A |
The single most-tested rule: one A, at least one R. If a row has two A's, authority is ambiguous; if it has zero R's, no one is doing the work. Both are exam-wrong configurations.
Tuckman's Ladder of Team Development
- Forming — members meet, are polite, look to the PM for direction.
- Storming — conflict peaks as approaches and roles clash. Highest tension.
- Norming — trust builds, the team agrees on working norms.
- Performing — the team is interdependent and high-output; the PM can delegate and step back.
- Adjourning — work completes, the team releases; celebrate and capture lessons learned.
Key nuance: progression is not guaranteed or linear. Adding a new member, swapping the leader, or a major scope change can knock a Performing team back to Storming. The PM's leadership style should shift from directing (Forming) toward delegating (Performing).
Resource Optimization: Leveling vs. Smoothing
| Technique | What it does | Effect on end date |
|---|---|---|
| Resource Leveling | Resolves over-allocation by shifting work | May extend duration; can change the critical path |
| Resource Smoothing | Shifts activities only within their float | Never extends duration; critical path unchanged |
Worked scenario: a single tester is assigned 16 hours of work in an 8-hour day (over-allocated). If the schedule must absorb this even at the cost of a later finish, you level. If the over-allocation can be fixed by sliding non-critical tasks within their available float, you smooth. Memory hook: Leveling can make the project Longer.
Motivation Theories on the CAPM
| Theory | Author | Core idea |
|---|---|---|
| Hierarchy of Needs | Maslow | Five levels, physiological up to self-actualization |
| Two-Factor | Herzberg | Hygiene prevents dissatisfaction; motivators create satisfaction |
| Theory X / Theory Y | McGregor | X = people avoid work; Y = people are self-driven |
| Acquired Needs | McClelland | Achievement, affiliation, power |
| Expectancy | Vroom | Motivation = Expectancy x Instrumentality x Valence |
Herzberg's most-tested trap: raising a low salary removes dissatisfaction but does not motivate. Recognition, growth, and meaningful work are the true motivators. If a question describes a team that is paid well yet disengaged, the fix is a motivator, not more pay.
Acquire Resources and Negotiation
In a matrix organization the PM rarely owns the staff outright, so Acquire Resources often means negotiating with functional managers for the right people. Three acquisition options the CAPM tests:
- Pre-assignment — specific people are named in the charter or as a condition of selection.
- Negotiation — the PM bargains with functional or other project managers for staff.
- Acquisition / outsourcing — hire externally when internal skills or capacity are missing (links directly to the procurement make-or-buy decision in section 5.4).
Virtual teams expand the talent pool across locations and time zones but raise communication and trust challenges, so the PM must invest more deliberately in Develop Team activities.
Develop Team Tools
The Develop Team process aims to lift competency, interaction, and the overall environment. Tools the exam names include co-location (placing the team physically together, sometimes called a "war room" or "tight matrix") to speed communication, team-building activities that move the group up Tuckman's ladder, recognition and rewards tied to desirable behavior, and training to close skill gaps identified during planning.
The output that measures success is the team performance assessment — an evaluation of how effectively the team is working, covering improvements in skills, reduced staff turnover, and increased cohesion.
Conflict Management
The Manage Team process includes resolving conflict. PMI's preferred resolution approaches, from best to worst:
| Approach | What it does |
|---|---|
| Collaborate / problem-solve | Work together for a win-win; PMI's preferred method |
| Compromise / reconcile | Each side gives up something; lose-lose middle ground |
| Smooth / accommodate | Emphasize agreement areas, downplay differences |
| Force / direct | One party imposes a view; win-lose, fast but resentment-prone |
| Withdraw / avoid | Retreat from the conflict; postpones rather than resolves |
When a CAPM question asks for the best way to resolve a disagreement, the answer is almost always collaborate/problem-solve, because it produces durable, mutually owned solutions.
In a RACI chart, how many people should be designated "Accountable" for a single activity?
A single tester is scheduled for 16 hours of work in one 8-hour day. You must resolve the over-allocation even though it pushes the project finish date later. Which technique applies?
A team that was performing smoothly suddenly experiences friction after two new developers join mid-project. Which Tuckman stage best describes the likely shift?
A team is paid above market rate but remains disengaged. According to Herzberg, what is the most effective intervention?