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
In the case of MTD and Glasgow projects. Resource smoothing is better here because of events that have been fixed and cannot be altered. The stakeholders needs to come together on how cost can be increased so their clients won’t be disappointed.
While Resource Smoothing appears to be a better option in order to keep to deadlines, it is important to have a round table discussion with all stakeholders regarding the cost implication of this, so that all parties are aligned.
Where the parties concerned are willing to bear costs, the projects proceeds smoothly. Where this is not the case, then, practically a degree of Resource Leveling maybe introduced after critical assessment has be done to determine what aspects of Resource Leveling can be applied.
Regarding the MTD and Glasgow situation, employing the resource leveling method isn’t practical. This approach entails task rescheduling, which could significantly disrupt the project schedule by altering task sequences or prolonging the project duration. It’s worth mentioning that resource smoothing is favored for addressing external constraints or urgent scenarios, whereas resource leveling is more appropriate when project deadlines are flexible, and resource adjustments can be accommodated through rescheduling.
In the case of MTD and Glasgow projects, resource smoothing is better as their clients have fixed dates for the events. Resource smoothing will increase the cost of the project but maintain the end date of the project. This is highly important to the clients. Resource levelling though helps to maintain cost,is not suitable for projects with fixed timelines which cannot be exceeded.
For the MTD and Glasglow scenario, it is not feasible to use the resource leveling approach because it involves rescheduling tasks and can be more disruptive to the project schedule because it may require changing task sequences or extending project duration.
It is important to note that resource smoothing is preferable when external constraints or urgent situations arise, while resource leveling is more suitable when there is flexibility in project deadlines and resource adjustments can be made through rescheduling.
“If there are no deadlines to meet, The combination of the two approaches is not bad for the MMT project, because aside from resources other factors like weather conditions and logistic accessibility can delay a project. Resources smoothing can be used for constructing tasks, while resources level can be used for tasks that are sensitive to weather changes.
I believe the MTD project would benefit more from project smoothing and not leveling. If a event is fast approaching and with rescheduling, one will not meet up . Although project smoothing might seem expensive, but in the end customers will be satisfied.
I think resource smoothing is best for this kind of project.
I also think it is not feasible to use the resource leveling approach because it involves reassigning tasks and this can be more disruptive to the project assignment because it may require changing task sequences or extending project duration. The event has been planned for a long time with other resources so the delivery date can not be rescheduled
Left to me, I feel resource levelling is not good for the MTD project because the event has been planned for a long time with other resources so the delivery date can not be rescheduled so the best option to go for us the resource smoothing.
it is not also feasible to use the resource leveling approach because it involves reassigning tasks and this can be more disruptive to the project assignment because it may require changing task sequences or extending project duration.
So I think resource smoothing is best for this kind of project.
For the MTD and Glasglow scenario, it is not feasible to use the resource leveling approach because it involves rescheduling tasks and can be more disruptive to the project schedule because it may require changing task sequences or extending project duration.
So i strongly believe that resource smoothing is the best approach for the MTD and Glasglow projects