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
Urgent events cannot utilize the resource leveling system, as exemplified by the MTD. However, implementing resource smoothing would be beneficial in such cases.
I’ll recommend resource smoothing for the following reasons:
1. Strict Time Constraints:
In urgent events like the MTD water company, and Glasgow company, meeting deadlines is the top priority. Resource leveling, which postpones tasks to balance resource allocation, can lead to delays, making it impractical for time-critical situations.
2. Need for Continuity:
Resource smoothing fine-tunes task schedules within available float without extending the project’s overall duration, ensuring steady progress. This method is better suited for urgent events as it optimizes resource usage while adhering to strict deadlines.
Urgent events cannot utilize the resource leveling system, as exemplified by the MTD. However, implementing resource smoothing would be beneficial in such cases.
I’ll recommend resource smoothing for the following reasons:
1. Strict Time Constraints:
In urgent events like the MTD (Minimum Time Duration), meeting deadlines is the top priority. Resource leveling, which postpones tasks to balance resource allocation, can lead to delays, making it impractical for time-critical situations.
2. Need for Continuity:
Resource smoothing fine-tunes task schedules within available float without extending the project’s overall duration, ensuring steady progress. This method is better suited for urgent events as it optimizes resource usage while adhering to strict deadlines.
I don’t think resource levelling will be the best option for MTD water company and Glasgow company. because it has to do with time frame. The projects are time frame and any further extension in the deadline of the project might affect the output of the delivery. Which might leads to lost of money and resources
Resource smoothing focuses on preserving planned deadlines but increasing project costs; resource levelling does not change the current capacity but focuses instead on rescheduling, with a possible impact on project deadlines.
From the two explanations above and considering MTD’s need at this time, implementing a resources levelling approach may not be feasible. Resources smoothing would be the best approach, though with an increase or additional cost to the project, the results would be achievable. MTD already have the capacity to deliver, all it takes is an holistic review of the resources to achieve and deliver without altering the deadlines.
Yes
Events that require urgency cannot adopt the resource leveling system.
MTD as a case study would require resources smoothing not resources leveling. Considering fixed deadlines with an immediately follow-up event. To avoid chaos allocation of more resources to enable a significant push to meet with the stakeholders initial time scheduled.
from the last video, where he spoke about one of their challenges being, that they are the first to arrive and last to leave, they don’t have enough time to consider resource levelling, resource smoothing will come in handy and he mentioned it when he said in Glasgow they had to bring another resource which increased their cost, but they just had to deliver.
Events that require urgency cannot adopt the resource leveling system and the MTD is an example of such cases. Resource smoothing on the other hand will be advantageous if implemented.
Resource smoothing would be the best approach for MDT to keep up with deadline and schedules on delivery of their project services.However ,this comes with increase cost ,and some times extension of time on the project.It is important that customers are happy and received quality service,the resultant chain reaction from customer ‘s satisfaction over time may compensate for additional costs incurred.
Resource levelling wouldn’t have been a good option for MTD Water company and Glasgow because it has to do with time frame. The event would have been greatly affected, and a whole lot of money and resources would have gone down with it. It couldn’t have in anyway be postponed or shifted.