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
There is already an issue of time constraint on the project. Considering the option of resource levelling will delay the start time of the project and will distrupt a lot concerning the event. It is better that MTD spends more and preserve the deadline. Therefore, it is better that MTD considers resource smoothing
Considering the decision of MTD as touching the Glass glow event. I will suggest the resource smoothing idea , reason been that the glass glow event has already been fixed and the time for change seems not be feasible. Hence, the date needs to hold but project cost increases.
For the MTD and Glasgow event. I suggest leveling, it’s does not change the current capacity but instead focuses on rescheduling, with a possible impact on a project deadlines and also, Unlike Smoothing that focuses on preserving planned deadlines but increases more additional cost. But it’s constraint is resources.
For the MTD and Glasgow event I don’t think the leveling approach would be the best way to go, I feel the smoothing approach is the best way to Go as this would enable both projects to finished at the stipulated time
Considering MTD water installation events company and the glasgow event, applying a resource levelling approach might be challenging due to the dynamic and unpredictable nature of events. Resource levelling assumes a stable and predictable resource demand which might not be the case in events with variable crowd sizes, technical issues and last-minute changes.
Resource levelling would require careful planning, monitoring and adjustments to ensure its effectiveness in the dynamic event environment.
Resource smoothing is best for the Glasgow and MTD, as keeping to the stipulated time, is a measure to calculate project success in stakeholders view, and any time further buffering might be considered a fail or no satisfaction.
Each project comes with its difficulties and issues.
In this case, it is good to follow the most sufficient way to deliver on the targeted end date.
By evaluating the type of project before deciding on going with a smoothing or a levelling approach.
The MTD considers negotiating with its customers, so if it demands taking such a step depending on the approach the project falls on.
If the project demands an additional cost to get the necessary things done and deliver at the end date, then it’s fine.
If there’s a need for levelling and still getting the project done before the end date, it’s also fine.
In order to optimize resource utilization, minimize idle time and overallocation, and address resource conflicts and bottlenecks, the resource leveling approach would be beneficial for both the MTD project and the Glasgow event. Implementing this approach would enable project managers to create a more feasible and realistic schedule without incurring additional costs.
I think because the event is time based, the best approach to adopt is resource smoothing, which entails incurring extra costs just to ensure that the event runs smoothly without having to be postponed.
In my opinion resource smoothing would be more preferable for Glasgow and MTD because it’s helps them to retain their schedule even if the cost or price is higher, and it also allow them to keep to time
Given the difficulties of rescheduling the events and the high expense of doing so, resource leveling may not be possible in this situation. This is mostly because advertisements for the event, tickets, and invitations have already been made and sent out. Because resource smoothing makes it possible to finish the task by the deadline or perhaps even ahead of schedule, it becomes a more sensible option.