Process — Managing Technical Aspects →mediumMultiple Select

PMP Process — Managing Technical Aspects Practice Question

You are managing a project that is experiencing resource constraints. Two critical tasks are scheduled concurrently but require the same specialized resource. Which TWO actions should the project manager consider to resolve this conflict?

⚠ Common exam trap

Many exam-takers confuse resource leveling with resource smoothing, but leveling can change the critical path and extend duration, while smoothing only adjusts within float; the PMP exam expects you to recognize that leveling is appropriate when resource constraints are absolute and cannot be resolved by adding resources or resequencing.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Adjust task dependencies to sequence the tasks if possible.

Option D is correct because adjusting task dependencies to sequence the two tasks resolves the conflict by ensuring the shared specialized resource is used on one task at a time, eliminating the concurrent demand without changing the resource pool. Option E is correct because resource leveling is the standard PMBOK technique for resolving resource overallocation or resource conflicts; it delays tasks (potentially extending the schedule) so that demand for the constrained resource never exceeds its availability. Option A is not appropriate because crashing adds resources to compress the schedule, but the constraint is a specialized resource that cannot simply be duplicated, so adding generic resources would not resolve the conflict and could increase cost. Option B is not appropriate because hiring contractors for a specialized resource is often infeasible or impractical, and it does not guarantee the same specialized skill set is available. Option C is not appropriate because removing a task from the schedule is a drastic scope reduction that is not a standard resource-conflict resolution technique and would likely harm project objectives.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Crash the schedule by adding more resources to both tasks.
Why it's wrong here
Crashing the schedule is a schedule compression technique primarily aimed at shortening the project duration by adding resources or working overtime, which inherently increases project costs and risks. While it involves adding resources, it does not directly resolve a resource conflict where a single, specialized resource is over-allocated across simultaneous tasks; simply adding more of the same resource to both tasks might not be feasible or effective if the resource is unique or the conflict is due to a single individual's availability.
✗
Hire additional contractors to perform one of the tasks.
Why it's wrong here
Hiring additional contractors is a resource acquisition strategy that can resolve resource conflicts by augmenting the project team's capacity. However, this approach introduces significant new costs, requires procurement processes, and involves lead times for onboarding and integration. It is generally considered a more drastic and costly measure, typically explored after internal schedule adjustments or resource reallocations have been deemed insufficient or unfeasible.
✗
Remove one task from the schedule to prioritize the other.
Why it's wrong here
Removing a task from the schedule is an extreme measure that directly impacts the project's scope and deliverables, potentially compromising the project's objectives or stakeholder expectations. This action implies eliminating a planned deliverable or work package rather than managing resource constraints to complete it. Such a drastic step should only be considered as a last resort when all other resource optimization and scheduling techniques have been exhausted.
✓
Adjust task dependencies to sequence the tasks if possible.
Why this is correct
Adjusting task dependencies to sequence tasks is a fundamental scheduling technique for resolving resource conflicts when two or more tasks require the same limited resource concurrently. By changing parallel tasks to a finish-to-start dependency, the resource can complete one task before starting the next, thereby eliminating the simultaneous demand on that specific resource without increasing project costs or requiring additional personnel, provided the project timeline can accommodate the sequential execution.
✓
Apply resource leveling to smooth the resource demand.
Why this is correct
Applying resource leveling is a specific resource optimization technique used to address resource over-allocations by adjusting activity start and finish dates based on resource availability. This method typically involves delaying non-critical path activities or utilizing available float to smooth resource usage, ensuring that no resource is assigned more work than they can handle at any given time, often extending the project duration but avoiding resource constraints.

Visual reference

Go deeper

PMP Process — Managing Technical Aspects Practice Question

Why each option matters

Option-by-option breakdown

Related to this question