How do resource smoothing and resource leveling differ from each other?
Resource smoothing aims to maintain original project deadlines while increasing project costs. On the other hand, resource leveling does not alter the existing resource capacity but instead emphasizes rescheduling, which may have an impact on project deadlines.
The accompanying diagram, sourced from the APM Body of Knowledge, provides a comparison between the two approaches.
Resource levelling and smoothing options (APM, 2019, p. 179)
© Association for Project Management (APM) (2019) APM Body of Knowledge (7th edn), Princes Risborough: APM.
At a more significant level of impact, certain projects undergo more than just rescheduling or resource allocation adjustments. They may undergo a reevaluation of their project scope by the project sponsor. This involves a broader analysis of the entire project and requires reconsideration of how time, cost, and quality interact within the project.
A prime example is the review of large-scale infrastructure projects like railways. Such projects often undergo rescaling due to increased costs, resulting in significant deviations from the original plans. The consequences of these revisions can affect the client and a wider range of stakeholders and may even result in the loss of subsequent work opportunities (Kerzner, 2009, p. 529).
Now, let’s consider MTD, the water installation events company, and the Glasgow event that you have been following in the course videos thus far. When examining the provided figure, do you think it would be feasible to implement a resource leveling approach in this scenario?
Share your thoughts and join the discussion below.
© The Open University
Your article helped me a lot, is there any more related content? Thanks!
I suggest Resource Levelling.
Hi my name is Pamela
Resource smoothing and resource leveling differ mainly in how they treat time and resources. Resource smoothing keeps the original project deadline and adjusts resources, often increasing costs through overtime or additional staff. Resource leveling, however, works within fixed resource limits and resolves over-allocation by rescheduling tasks, which can extend the project duration.
In the case of MTD and the Glasgow event, using resource leveling would be difficult because the project has a fixed event deadline that cannot be moved. Delaying activities to resolve resource constraints would risk missing the event date. Resource smoothing is therefore more suitable, as it allows MTD to meet the deadline by increasing resources or costs rather than changing the schedule.
Overall, for event-based projects like this, meeting the deadline is more critical than controlling costs, making resource smoothing the more realistic approach.
”In the context of the MTD Glasgow event, implementing a resource leveling approach is unfeasible because it is a time-limited project with a hard deadline.
According to the APM Body of Knowledge, resource leveling prioritizes resource constraints over the schedule, which often causes the end date to slip. For a live event where infrastructure must be operational by the start date, such a delay represents project failure.
Therefore, MTD must adopt a resource smoothing strategy. This approach focuses on maintaining the original project deadline even when a resource shortfall occurs. While this ensures the water is running on time for the event, it requires trade-offs—specifically an increase in costs.
MTD may need to pay for overtime, hire additional contractors, or expedite equipment delivery.
Choosing to increase costs through smoothing is the most responsible path because the alternative—reducing the project scope —poses significant risks. Failing to deliver the promised services would lead to severe reputational damage and the potential loss of future contract opportunities with Key Players like the Glasgow City Council and major Sponsors.”
It can be feasible but it will highly impact the project deadline
In this case, applying a full resource levelling approach would be difficult because major events have fixed deadlines that cannot slip. Instead, resource smoothing is more realistic, as MTD would need to maintain the event date by increasing or reallocating resources where necessary. But limited levelling can still be used internally, like adjusting staff shifts or equipment use, as long as it does not affect the final delivery date.
It might not be feasible to implement a resource leveling approach in this scenario given that one process is tied to another and there’s a timeline for each process to happen.
Yes
I think MTD can have resource levelling not all the stakeholders (workers) are needed on the work site at the same time
For instance, they are working in a community in their home country, they can reschedule the time each worker comes to work to reduce the load on the facilities provided for the worker’s comfort e.g accommodation, feeding, transportation and much more
In the case of the MTD project, the resource levelling approach can be applicable because it’s not time constraints.
Yes, i think resource levelling can be employed in mid projects-
For instance, the stakeholders delivering the water il a non- critical task which can be floated, for instance supplying water in the morning must not be by 6am as they can delay the supply to 8am which in still with the morning zone.
It is not feasible to employ resource levelling. The best and effective one is to adopt resource smoothing.
it will not be feasible because the project can’t be floated.