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
My little understanding about resource leveling and resource smoothing
Resource leveling adjusts the project schedule to match resource availability, potentially extending the timeline, it is used when there are limited resources and the project timeline can be adjusted,
Resource smoothing works within the existing timeline and redistributes tasks to prevent overloading, it2 is used when the project deadline is fixed and resources need to be optimized within that timeline
for the case of MTD and Glasgow, resource smoothing is advisable. Resource smoothing would be more appropriate in cases where an error was discovered a few days prior to the event. Reducing interruptions and making sure the event goes according to schedule should be the main priorities. Resource levelling at this stage could impede the project and harm the standing of the company. Water is urgently needed for the first group of participants, and a major postponement could negatively affect the event’s outcome. Little changes can be made thanks to resource smoothing without impacting the project’s schedule.
My thoughts on the concepts of resource smoothing and resource levelling in project management.
1. Resource Smoothing:
Resource smoothing is a technique used to adjust resource usage within a project while keeping the project schedule unchanged.
– The primary goal of resource smoothing is to minimize fluctuations in resource utilization, especially when dealing with limited resources.
– In resource smoothing, the focus is on managing resource peaks and valleys to achieve a more consistent resource allocation.
– It allows for small adjustments to resource assignments without affecting project deadlines.
– Resource smoothing is particularly useful when there are external constraints (such as contractual obligations or fixed deadlines) that prevent rescheduling.
– However, it may result in additional costs due to overtime or other resource adjustments.
2. Resource Leveling:
– Resource levelling, on the other hand, involves rescheduling tasks within a project to **balance resource demand.
– The primary goal of resource levelling is to avoid resource overloads by shifting tasks or changing their timing.
– In resource levelling, the focus is on achieving an even distribution of resource usage over time.
– It may involve delaying non-critical tasks or rearranging dependencies to accommodate resource availability.
– Resource levelling can be more disruptive to the project schedule because it may require changing task sequences or extending project duration.
– It is suitable when project deadlines are flexible and when resource constraints can be managed through rescheduling.
3. Application to MTD and Glasgow Cases:
– For the MTD case, where an error was identified a few days before the event, resource smoothing would be more appropriate. The focus should be on minimizing disruptions and ensuring that the event proceeds as planned. Implementing resource levelling at this point could hinder the project and damage the organization’s reputation.
– Similarly, for the Glasgow case, resource smoothing is advisable. The need for water for the first set of participants is urgent, and any significant rescheduling could impact the event’s success. Resource smoothing allows for minor adjustments without affecting the project timeline.
It is important to note that resource smoothing is preferable when external constraints or urgent situations arise, while resource levelling is more suitable when there is flexibility in project deadlines and resource adjustments can be made through rescheduling.
To me, resource levelling isn’t suitable for the MTD project because the event have been planned for a long time with other resources so the delivery date can’t be rescheduled because of maybe 10% of the whole plan so the best option to go for us the resource smoothing.
Resource smoothing focuses on preserving deadlines and end dates while increasing projects costs and adding new resources to the project. Resource leveling however, focuses on balancing the workload on resources in order to align the usage of the resources with their available capacity which mostly results to the change or rescheduling of end date.
With what we have learnt so far, I would agree and say it is feasible to implement a resource leveling approach. In this scenario.
Resource leveling will help the project manager enough time to stabilize the work load and reduce the risk of stress on the workers.
The end date can be rescheduled as long as it is communicated effectively with the shareholders and clients and agreed upon so as to still meet client satisfaction and quality requirements.
Resource smoothing prevents rescheduling and helps meet deadlines, although it might incur extra costs. On the other hand, resource leveling promotes rescheduling while maintaining the existing capacity.
Implementing the resource leveling approach for the cases of MTD and Glasgow is not advisable. The resource smoothing approach is more suitable, particularly for MTD. They identified an error a few days before the event, with the first set of participants expected soon and needing water. Using resource leveling at this point would hinder the project and could damage their reputation.
I do not think it would be feasible to implement a resource leveling approach in this scenario? The reason being that the approach entails doing the best with the resources available but the project end date slips and you have a new project end date. The Glasgow event is a fixed event scheduled already to take place at a particular days of the month and year. The organizers of the Glasgow event and MTD does not have the luxury of time hence the water infrastructure must be completed within the projected time frame so as to be ready on time for the event.
Already in some of the videos watched, the project manager talked of instances where contingency measures had to be embraced just to make sure MTD delivers within project time frame.
Consequently, resource smoothing which allows for engagement of extra resources even though at an extra cost in order to maintain and keep to the projected timeline of delivery is a better option in this situation.
From I have learnt so far, I think that the MTD project would benefit more from project smoothing and not leveling. It there’s an event that was fast approaching and with rescheduling, deadline will be missed. Though project smoothing would lead to more cost, but in the end there will be customers satisfaction.
In MTDs case resource smoothing is the best i will suggest as thus allow for meeting dead lines and given expected timely at the expense of additional cost with events tend to be time bound.
Resource smoothing prevents rescheduling and also helps meeting deadlines although, this might attracts extra cost while resource leveling promotes rescheduling while all other existing capacity remains the same .
In the case of MTD and Glasgow, I will suggest resource smoothing because the date of the event would have been announced and every effort to meet up with the deadline will be adopted. Yes, it attracts extra cost and I feel this can be discussed between both companies and resolved.
I will like to approach this discussion these points Resource Smoothing is were a new member is added to join the team.
NB:
1) It will definitely increase the over head cost of the project.
2) There will be need for training and time to bring the new member up to speed on current position of the project to be able to meet the dead line of the project..
While for Resource Leveling, the team member might be greatly affected.
1) it also affects cost as over time hours means extra cost on the initial budget.
2) Members will stressed working extra hours
3) This will affect quality as a result of much fatigue.
Finally 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.