5 Resource Planning and Management
Learn how to estimate, assign, balance, and monitor project resources while keeping responsibilities and commitments aligned with actual availability.
Estimate resource needs
Start with the project’s work breakdown structure or activity list. For every activity, identify the resources required and the conditions under which they can be used.
Estimate each activity’s:
Type and quantity: for example, two software testers, one excavator, or 500 metres of cable.
Required capability: the skills, experience, certifications, or equipment specifications needed.
Effort and duration: effort is the amount of work, such as 40 person-hours; duration is the elapsed time to complete it. They are related but not interchangeable. Forty hours of effort might take one person a week or two people about half a week, if the work can be divided.
Timing and availability: when a resource is required, how long it is needed, and limits such as other commitments, maintenance, leave, or delivery lead times.
Constraints and assumptions: for example, a specialist may be available only two days per week, or a test facility may be shared with another team.
Use expert judgment, comparable past work, task-level estimates, and supplier information as appropriate. Record assumptions and uncertainty: estimates are planning forecasts, not guarantees. Check that the combined work fits the capability and capacity actually available. A person listed at capacity may still have meetings, operational duties, or other assignments that reduce usable project time.
Organize needs over time
A can group needs by category, such as personnel, equipment, materials, and facilities. A time-phased shows the quantities needed in each period, making peaks and shortages easier to identify.
Resource planning includes identifying needs, checking availability, scheduling use, and monitoring actual use against the plan. Review resource needs as the schedule and project conditions change.
Allocate resources and clarify responsibilities
Assign resources to specific work packages or activities, and confirm commitments with the people or managers who control them. A role-based estimate, such as “electrical engineer,” helps establish the capability required; confirm a named assignment before relying on that person in a committed schedule. For external resources, account for procurement, onboarding, delivery, and contract constraints.
A links project work to the people or roles responsible for it. is one common form:
Responsible: performs the work.
Accountable: owns the result or decision. Normally, assign one clear accountable role to each activity.
Consulted: provides input before or during the work.
Informed: receives updates.
For example, equipment specification approval may have the project manager consulted, the engineer responsible, the supplier consulted, and the sponsor accountable. For equipment delivery, the project manager is informed, the engineer consulted, and the supplier responsible and accountable, while the sponsor is informed. For equipment acceptance, the project manager is accountable, the engineer responsible, the supplier consulted, and the sponsor informed.
The matrix makes handoffs and decision ownership visible, but it does not replace discussion. Clarify authority, expected outputs, and escalation routes with the people involved.
Balance resource demand
A shows how much of each resource each activity requires over time. Compare this demand with realistic capacity. If demand exceeds capacity, consider these options:
Change timing: move non-urgent work or sequence activities differently.
Adjust assignments: use another qualified person or equipment item, if available.
Change the work approach: divide work, reduce unnecessary effort, or use a suitable alternative method.
Add capacity: recruit, contract, rent, or purchase resources, considering cost and lead time.
Revisit project commitments: negotiate changes to scope, budget, or completion dates when the shortage cannot otherwise be resolved.
moves work within its available schedule flexibility to reduce peaks, while keeping the planned completion date unchanged when possible. adjusts activity dates to respect resource limits; it can extend project duration or change the critical path. The choice depends on which constraints—date, cost, or resource availability—are firm.
For example, a project has one qualified tester, but two activities each need that tester during the same week. If one activity has schedule flexibility, move it to a later available period to smooth demand. If neither can move without delaying delivery, consider a second qualified tester, a revised delivery date, or another agreed change. Do not silently schedule the same person for conflicting work.
Monitor and update the plan
During delivery, compare planned and actual resource use. Track assignments and availability, hours or quantities used, forecast demand, unresolved shortages, and work delayed by resource conflicts.
Investigate variances: a task may need more effort than estimated, a resource may be unavailable, or priorities may have changed. Update assignments and forecasts when conditions change. Use the project’s change-control process when changes affect approved scope, schedule, or budget. Coordinate resource release and reassignment as work finishes.
Keeping the current helps decision-makers see trade-offs early rather than discovering a shortage at a delivery milestone.