Estimate Resources
| Resources/Planning/Estimate Resources | ||
|---|---|---|
| Inputs | Tools & Techniques | Outputs |
|
||
Inputs, tools & techniques, and outputs for this process.
A planning activity that determines the types, quantities, and timing of team, equipment, and material resources needed to perform project work across predictive, agile, or hybrid approaches.
Purpose & When to Use
Estimate Resources determines what resources are needed to complete the work and when they are required. It informs the schedule, cost estimates, procurement decisions, and team staffing. Use it early during planning and revisit it whenever scope, approach, risks, or availability change.
- Clarify the mix of people, skills, equipment, facilities, and materials needed for each activity or for a stable team in agile settings.
- Support make-or-buy choices and vendor lead times.
- Expose resource risks, constraints, and training needs.
- Enable resource leveling or smoothing to create a realistic schedule.
- Align resource demand with budgets and capacity.
Mini Flow (How It’s Done)
- Review scope, WBS or backlog, activity list, assumptions, and constraints.
- Identify resource types per activity or team: roles, skills, equipment, materials, and facilities.
- Select estimation approaches: analogous, parametric, bottom-up, and three-point where uncertainty is high.
- Perform alternatives analysis: in-house vs. contract, different tooling, skill mixes, or batch sizes.
- Check availability with resource calendars, capacity, vendor lead times, and organizational policies.
- Model options using PMIS, resource histograms, and a resource breakdown structure to visualize demand.
- Resolve conflicts by leveling or smoothing and, if needed, sequence or split work to match capacity.
- Document activity-level resource requirements and the basis of estimate, including assumptions and constraints.
- Update related plans: schedule, cost estimates, procurement strategy, risk responses, and team plan.
- Socialize and validate estimates with SMEs, functional managers, vendors, and the team.
Quality & Acceptance Checklist
- Resource needs are traceable to specific activities or backlog items.
- Quantities, skill levels, and units of measure are clear and testable.
- Availability windows and calendars are verified with owners and vendors.
- Assumptions, constraints, and data sources are recorded in the basis of estimate.
- Alternatives considered and the chosen rationale are documented.
- Resource risks, learning curves, and ramp-up time are reflected in estimates.
- Estimates align with budget caps, procurement lead times, and labor policies.
- Visuals such as an RBS and histograms are available and current.
- Agile teams show capacity and throughput expectations instead of task-hour guesses.
- Peer or SME review completed and approvals captured as required.
Common Mistakes & Exam Traps
- Confusing duration estimating with resource estimating; first decide what resources are needed, then how long work will take.
- Ignoring non-labor resources such as equipment, materials, and facilities.
- Estimating named individuals too early instead of roles and skills, which reduces flexibility.
- Skipping resource calendars and vendor lead times, leading to unrealistic plans.
- Not performing alternatives analysis to find lower-cost or faster combinations.
- Failing to update cost and schedule when resource choices change.
- Treating leveling as a separate step done later; it should inform estimates now.
- In agile, using task hours instead of stable team capacity and historical velocity.
- Overlooking training, onboarding, and learning curves for new tools or team members.
- Assuming unlimited access to shared resources in a matrix environment.
PMP Example Question
While planning, the team identified required skills and equipment for each activity, but several key resources are unavailable during critical weeks. What should the project manager do next?
- Consult resource calendars, level or smooth the schedule, and update the resource estimates and assumptions.
- Request overtime to keep the baseline dates unchanged.
- Compress the schedule using crashing to maintain the original plan.
- Ask the sponsor for additional budget before revising estimates.
Correct Answer: A — Consult resource calendars, level or smooth the schedule, and update the resource estimates and assumptions.
Explanation: When availability conflicts appear during resource estimating, adjust the plan using calendars and leveling or smoothing, then update the basis of estimate. Overtime or crashing come later if needed and justified.
HKSM