Resource planning is the art and science of ensuring that the right tools, materials, and—most importantly—people are available at the right time to execute the project schedule. It is where the mathematical perfection of the Gantt chart meets the messy reality of human availability.
The Evolution of Resource Management
In the early industrial era, resource planning was synonymous with Labor Scheduling. Workers were treated as interchangeable units of production. However, as we moved into the knowledge economy, the focus shifted to Intellectual Capital Management. In modern project management, we don't just plan "hours"; we plan "expertise," "context," and "innovation."
Key Concepts & Frameworks
1. Resource Leveling vs. Smoothing
- Resource Leveling: Adjusting the project dates to address resource over-allocation. This can change the critical path and delay the project.
- Resource Smoothing: Adjusting activities within their float/slack so that resources do not exceed pre-defined limits. This does not delay the project finish date.
2. The RACI Matrix
A fundamental framework for resource clarity:
- Responsible: Who is doing the work.
- Accountable: The one who "owns" the result (only one per task).
- Consulted: Those whose opinions are sought.
- Informed: Those kept up-to-date on progress.
The Traps: Learning from Failure
The "Resource-as-a-Brick" Fallacy
Treating human beings like static resources (like concrete or timber) is the fastest way to break a schedule. Humans have learning curves, emotional states, and varying productivity levels. Doubling the people does not always halve the time.
The Context-Switching Tax
When a resource is assigned to three different projects, they don't give 33% to each. They lose a significant percentage of their time just switching context between tasks. This hidden "tax" is often the root cause of project delays.
Recommended Reading List
- The Mythical Man-Month — Frederick Brooks The "bible" of software resource planning. Introduces Brooks' Law: "Adding manpower to a late software project makes it later."
- Peopleware — Tom DeMarco & Timothy Lister A deep dive into the human element of project resources, focusing on environment and team chemistry.
- Critical Chain — Eliyahu M. Goldratt Introduces the Theory of Constraints (ToC) to project scheduling, focusing on resource-constrained paths.
- Drive — Daniel Pink Explores what actually motivates modern knowledge workers: Autonomy, Mastery, and Purpose.
The Scrum Perspective: From Resources to People
Scrum intentionally avoids the word "Resources" when referring to people. Instead, it focuses on Cross-Functional Teams:
- Stable Teams: Instead of moving people to projects, move work to stable teams. This eliminates the "forming-storming" overhead.
- Capacity vs. Velocity: Scrum teams plan based on their Capacity (how much time they actually have in the next 2 weeks) and track their Velocity (how much work they historically complete).
- Self-Organization: The team decides how to use their collective resources to meet the Sprint Goal, rather than a PM assigning individual tasks.