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
Taking the MTD’s Glasgow project as a context, there cannot be any availability of floating which will therefore make resource levelling a bad strategy here. Hence, resource smoothing could be employed by adding new resources such as water source or personnel to ensure that the deadline is met. Also, overtime may really be considered in order to ensure that all necessary measures are put in place within the agreed time.
Considering MTD, the best method to use is resource smoothing which involves using overtime so as to meet up with the schedule.
Resource levelling approach can only be used if critical activities duration is extended which will definitely affect the project cost.
With respect to the MTD Glasgow event, resource leveling will be a wrong approach because the project deadline cannot be changed. The entire project objective was to supply drinking water to an event and the date of the event was fixed.
Resource smoothing will be the right approach although it will impact the project cost.
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.
——————————————–
I do not think resource leveling will work because it is solely focused on rescheduling and there is possible impact on project deadlines. A company like MTD can not afford to reschedule because their client event date is fixed.
But the project could be subject to revision, project sponsors are invited to a roundtable to evaluate or revise the scope .
Resource smoothing aims at maintaining original project deadlines while increasing project costs. Whilst Resource leveling focuses on rescheduling with possible impacts on project timelines without altering the project capacity.
Resource levelling approach could be used by extending the critical activities duration. Though that would affect the cost. Crticial activities could be started on time by extending the duration of it so as to spread workload for more extended days.
But I feel the best method would be resource smoothing by using overtime so as to meet up with the schedule.
Resource smoothing will work best in MTD event because there is a limited time frame and they might not necessarily be able to reschedule so increasing the project costs and preserving the planed deadline will be the best option
MTD projects take their origin from global or national programs such as it being announced as Official Sponsor of the Olympic and Paralympic Games Paris 2024. Their projects are not stand-alone. Thus challenges encountered require remediation in the areas of resource increase which ensures project completion within allotted floats. These increases include
1. Additional toilets added
2. Shortfall in the volume of water:
I. An extra buffer put in place
ii. More contingencies such as tanker support
iii. Speaking with local authorities with a view to increase the volume of water.
These decisions had to be made in line with the client’s timelines adhered to.
The foregoing decisions indicate the nature of the project which is linear with dependencies and non-flexible deadlines. Strictly, resource-smoothing is the right fit.
Resource-leveling would have scored a point had the MTD projects been stand-alone, bearing the undeniable label of Agile or iterative. Such would have gulped in either or all of the intrinsic elements of resource-leveling listed below:
1. Delay non-critical activities within their available floats
2. Extend non-critical activity duration within their available floats
3. Delay critical activities
4. Extend critical activities durations
5. Split an activity into non-sequential activity.
Resource leveling focuses on rescheduling with possible impacts on project timelines, however it does not alter the project capacity. So it is very feasible to implement this approach on many projects types including the MTD and Glasgow event.
Considering that events are planned are held in a pre-adopted and limited period of time, I don’t think it would be possible to apply resource levelling in this scenario, as the deadline cannot be extended.