Unit 9: Resolving Overallocations - Subjective Questions

Resource overallocation occurs when a resource is assigned more work than it can complete within its available working time during a specific period.

Common causes:

• Assigning the same resource to overlapping tasks.
• Scheduling work beyond the resource's maximum availability.
• Underestimating task duration or required effort.
• Changes to task dependencies, calendars, or deadlines.
• Assigning a part-time resource as though the resource were available full-time.

Consequences:

• Delayed task completion and schedule slippage.
• Increased employee stress and reduced productivity.
• Greater risk of errors and poor-quality output.
• Higher costs due to overtime or the need for additional resources.
• Unrealistic project plans and unreliable progress forecasts.

Overallocations should therefore be identified and resolved while preserving important project constraints such as deadlines, costs, and resource availability.

Manual task delay resolves an overallocation by moving one of the conflicting tasks to a later time when the resource is available.

Procedure:

• Identify the resource and the time period in which the overallocation occurs.
• Examine the tasks assigned to that resource.
• Select a task that can be postponed without violating an important deadline.
• Enter an appropriate delay for the task or move its start date.
• Recheck the resource schedule to confirm that the overlap has been removed.
• Review the project finish date and dependent tasks for side effects.

A task with sufficient free slack or total slack is generally a suitable candidate for delay. Manual delay gives the project manager direct control, but it can create scheduling conflicts if task dependencies and constraints are not considered.

Resource leveling is a scheduling technique that adjusts task timing to eliminate or reduce resource overallocations.

During leveling, the scheduling tool may:

• Delay tasks until the assigned resources become available.
• Split tasks when work can be interrupted and resumed later.
• Reorder tasks according to priority, dependencies, constraints, and slack.
• Extend the project duration when insufficient slack is available.

Leveling generally does not reduce the amount of work assigned. Instead, it redistributes that work across available time. The result is a more realistic resource schedule, although the project finish date may be postponed. The project manager should review the leveled schedule to ensure that automatic changes remain consistent with business priorities.

Automatic resource leveling:

• Is performed by project management software using predefined rules.
• Can evaluate many resource conflicts quickly.
• Uses factors such as task priority, slack, constraints, and dependencies.
• May delay or split tasks without individual approval for every change.
• Can produce unexpected schedule extensions if the settings are not reviewed.

Manual resource leveling:

• Is performed by the project manager after examining each conflict.
• Allows business importance and practical knowledge to influence decisions.
• May involve delaying, splitting, reassigning, or rescheduling selected tasks.
• Provides greater control but requires more time and careful analysis.

Automatic leveling is useful for large schedules, while manual leveling is valuable when task priorities or organizational constraints cannot be fully represented by software settings.

Important resource-leveling settings include:

• Leveling calculation: Determines whether leveling occurs automatically or only when manually initiated.
• Leveling range: Specifies whether the entire project or only a selected date range will be leveled.
• Leveling order: Controls how tasks are selected for delay, such as by task ID, standard scheduling rules, or task priority.
• Available slack: Allows the tool to delay tasks only within their available slack when the project finish date must be protected.
• Task splitting: Determines whether tasks may be interrupted and resumed to resolve conflicts.
• Individual assignment adjustment: Controls whether separate assignments on the same task can be adjusted independently.
• Proposed versus confirmed resources: Determines which resource booking types are considered.

These settings should be chosen according to deadline sensitivity, task flexibility, and the organization's scheduling policies.

These scheduling properties guide the leveling engine when it decides which task should be delayed:

• Task priority: A high-priority task is less likely to be delayed, while a low-priority task is a stronger candidate for adjustment.
• Dependencies: A task cannot normally be moved in a way that violates its predecessor or successor relationships.
• Constraints: Restrictions such as a fixed start or finish date can limit or prevent movement during leveling.
• Slack: Tasks with available slack may be delayed without immediately changing the project finish date.

A leveling tool evaluates these factors together. For example, it may delay a low-priority task with significant slack instead of a high-priority critical task. Incorrect priorities or rigid constraints can reduce the effectiveness of leveling and may force the project finish date to move.

The Leveling Gantt view is used to compare the original task schedule with the schedule produced by resource leveling.

It helps the project manager to:

• Identify tasks that have been delayed by leveling.
• Observe changes in task start and finish dates.
• View leveling delay values in the associated table.
• Compare pre-leveling and post-leveling Gantt bars.
• Detect tasks that were split or moved.
• Assess whether the project finish date has changed.
• Verify that resource conflicts have been removed.

This view is particularly useful because it makes the effects of leveling visible instead of presenting only the final dates. The manager can use it to decide whether to retain the changes, modify task priorities, clear leveling, or apply a different conflict-resolution method.

Decreasing work time means reducing the amount of effort assigned to an overallocated resource on one or more tasks.

It can be done by:

• Reducing the resource's assignment units.
• Removing unnecessary work from the task.
• Transferring part of the work to another resource.
• Revising the task scope or deliverables.
• Using a more efficient method that genuinely requires fewer labor hours.

Limitations:

• Reducing assignment units may extend task duration, depending on the task type and scheduling settings.
• Arbitrarily reducing work can make the plan unrealistic if the original effort is still required.
• Scope reduction may require stakeholder approval.
• The change may affect costs, quality, and successor tasks.

The amount of work should be decreased only when the project manager can justify that the task requires less effort or that part of the work has been reassigned or removed.

Task splitting divides a task into separate working segments with a nonworking gap between them. The resource completes part of the task, pauses it to perform another activity, and resumes the remaining work later.

Advantages:

• Removes conflicts during the period of the split.
• Allows urgent or higher-priority work to be completed first.
• Retains the original resource assignment.
• Can avoid delaying the start of the entire task.

Disadvantages:

• Interruptions may reduce productivity because of context switching and restart effort.
• Some tasks cannot be practically interrupted.
• Splits can make the schedule more difficult to monitor.
• The task finish date and dependent work may be delayed.

Splitting is appropriate when the work is interruptible and when the cost of pausing and restarting is lower than the impact of leaving the overallocation unresolved.

Delaying a task moves the task or its remaining work to a later start time. The task is generally performed continuously after the delay. It is suitable when the entire task can wait and when sufficient slack is available.

Splitting a task retains one or more portions of work at their existing dates but introduces a gap during the conflict period. It is suitable when some work can begin immediately but must pause while the resource performs another task.

Key differences:

• Delay changes when the task begins or resumes; splitting creates multiple working segments.
• Delay is simpler to manage; splitting can increase scheduling complexity.
• Delay may postpone all task output; splitting may allow partial progress before the interruption.
• Both techniques can affect successor tasks and the project finish date.

The choice depends on task interruptibility, priority, available slack, and the operational cost of stopping and restarting work.

Free slack is the amount of time a task can be delayed without delaying the early start of any successor task.

Total slack is the amount of time a task can be delayed without delaying the project finish date or violating a relevant scheduling constraint.

Conceptually, total slack may be calculated as:

or equivalently:

When resolving an overallocation, a manager can first delay tasks that have positive slack. Free slack provides room to move a task without affecting its immediate successors, while total slack provides room to move it without affecting the overall project deadline. A task with zero total slack is normally critical and should be delayed only after evaluating its effect on project completion.

Slack can be examined in a task-oriented table, such as a schedule table containing the Free Slack and Total Slack fields.

Interpretation:

• A positive free-slack value indicates that the task can move by that amount without delaying a successor.
• A positive total-slack value indicates that the task can move by that amount without delaying project completion.
• Zero total slack generally identifies a critical task.
• Negative slack indicates that the current schedule cannot satisfy a deadline or constraint without corrective action.

To analyze an overallocation, the project manager can filter or sort affected tasks by slack and select tasks with the greatest scheduling flexibility for delay. The table should be reviewed together with task dependencies, priorities, constraints, and milestones because a numeric slack value alone may not represent every practical restriction.

In a Gantt view, slack is commonly displayed as a line or bar extending from the scheduled finish of a task toward its latest permissible finish. Critical tasks usually show no available total slack.

Advantages of viewing slack graphically:

• Flexible and critical tasks can be identified quickly.
• The amount of scheduling freedom can be compared visually.
• Relationships between slack, dependencies, and deadlines are easier to understand.
• Tasks that can be delayed to resolve an overallocation become more apparent.
• The effect of schedule adjustments can be evaluated in the context of the full timeline.

A Gantt representation is especially useful for detecting where flexibility exists across a phase. However, the manager should use table fields when exact slack values are required.

Reassigning resources involves replacing an overallocated resource or transferring part of its work to another available resource.

Before making the reassignment, the project manager should evaluate:

• The substitute resource's skills and experience.
• Availability during the required period.
• Maximum assignment units and existing workload.
• Differences in productivity or work rate.
• Cost rates and budget impact.
• Access permissions, equipment, and location constraints.
• Training, handover, and communication effort.
• Effects on task duration, quality, and risk.

After reassignment, the manager should recalculate or inspect the schedule, verify that the original overallocation is removed, and confirm that the replacement resource has not become overallocated. A resource should not be treated as interchangeable merely because that resource has free time.

Reassigning a resource:

• Changes who performs some or all of the work.
• Can preserve task dates when another qualified resource is available.
• May alter task cost, productivity, quality, or risk.
• Can require handover or training.

Leveling the existing resource's tasks:

• Retains the original resource assignment.
• Resolves the conflict mainly by changing task timing.
• May delay tasks or extend the project duration.
• Avoids skill-transfer issues but may affect deadlines.

Reassignment is preferable when schedule dates are important and a suitable replacement is available. Leveling is preferable when the original resource's expertise is essential and the schedule contains enough flexibility. A combined approach may be required when neither method alone resolves all conflicts.

Increasing working hours expands a resource's available capacity during the conflict period. This may be done by modifying the resource calendar to add working time on selected days, extend daily working hours, or temporarily make a normally nonworking period available.

Potential benefits:

• Required work may be completed without delaying tasks.
• Existing assignments and task ownership can be preserved.
• Short-term conflicts may be resolved quickly.

Risks and limitations:

• Calendar changes may incorrectly treat additional hours as regular work instead of overtime.
• Extended schedules can cause fatigue, errors, and reduced productivity.
• Labor laws, contracts, and organizational policies may restrict working hours.
• Additional cost may be incurred.
• A temporary capacity increase does not solve a persistent workload imbalance.

The calendar should reflect genuine availability. Increasing hours should be approved, time-limited, and reviewed for health, cost, quality, and compliance implications.

Overtime work is the portion of a resource's assigned effort that is scheduled outside regular working capacity and paid at the resource's overtime rate.

General procedure:

• Confirm that the resource is permitted and available to work overtime.
• Define an overtime rate for the resource.
• Open an assignment-oriented view, such as task usage or resource usage.
• Add or display the overtime-work field.
• Enter the amount of assigned work that will be performed as overtime.
• Review the recalculated duration, finish date, and cost.

Assigning overtime can shorten a task or prevent schedule delay because some work is completed outside normal hours. It usually increases cost and does not remove the physical effort required from the resource. Excessive overtime may create fatigue and quality risks, so it should be used selectively rather than as a permanent solution to insufficient capacity.

Increasing regular working hours changes the resource calendar so that additional periods are treated as normal availability. Work scheduled in those periods may be calculated using the standard rate unless other settings apply.

Assigning overtime work identifies a specific portion of an assignment as overtime. That work is associated with the resource's overtime rate and is explicitly tracked as overtime effort.

Main distinctions:

• Calendar changes affect general availability; overtime is recorded at the assignment level.
• Regular-hour increases may affect multiple tasks; overtime can be targeted at a particular task.
• Overtime generally increases cost according to the overtime rate.
• Both approaches can increase short-term capacity, but neither should represent availability that does not actually exist.

The correct method depends on whether the resource's standard schedule has genuinely changed or whether exceptional additional work is being authorized.

Resource contouring is the distribution of assignment work at different intensities across the duration of a task. Instead of assigning work uniformly, a contour models how effort is expected to rise, fall, or vary over time.

Common contour patterns include:

• Flat: Work is distributed evenly throughout the assignment.
• Back-loaded: Less work occurs initially and more work occurs near the end.
• Front-loaded: More work occurs initially and less work occurs near the end.
• Double peak: Work intensity rises twice during the assignment.
• Early peak: The highest workload occurs relatively early.
• Late peak: The highest workload occurs relatively late.
• Bell: Work gradually rises to a middle peak and then falls.
• Turtle: Work rises rapidly, remains high for a period, and then decreases.

Contours help create realistic plans when resource effort is not constant throughout a task.

A systematic resolution strategy should proceed as follows:

1. Confirm the conflict: Use resource and task views to identify the exact dates, assignments, and amount of excess work.
2. Analyze slack: Display free slack and total slack. Consider delaying the task with greater slack so that critical work is protected.
3. Review priorities and dependencies: Determine which task is more important and whether either task has a fixed constraint or dependent milestone.
4. Apply leveling: Use controlled leveling settings to delay flexible work. Review the result in the Leveling Gantt view.
5. Consider splitting: If a complete delay is unacceptable and the task is interruptible, split lower-priority work around the conflict period.
6. Evaluate reassignment: Transfer work to a qualified and available resource when task dates must be preserved.
7. Consider additional capacity: Use approved overtime or a temporary calendar change only when cost, policy, and employee well-being permit it.
8. Adjust contours: Redistribute assignment intensity when the task does not require uniform effort, ensuring that work is shifted to periods with available capacity.
9. Validate the result: Confirm that no new overallocation has been created and review duration, cost, quality, and the project finish date.

The preferred solution is the one that produces a feasible schedule while causing the least acceptable impact on scope, cost, quality, deadlines, and employee workload.