Resource leveling heuristics is a prioritization process that allocates scarce resources to critical path activities first. In other words, it is a technique that resolves resource conflicts by delaying tasks within their slack allowances.
Projects seldom have an abundance of resources. In many situations, a project will require a critical resource that must be available at certain project points. To ensure availability, the critical resource will need to be scheduled in reverse from the project ending date, this is known as reverse resource allocation scheduling.
To use the reverse resource allocation scheduling method, you must be able to complete the activity with the limited number of resources that are available. For example, the resource requirements for a renovations project indicates that three electrical engineers are needed. However, the project manager discovers that the work, which was scheduled to be done by three people, must now be done by two. The result is that the activity may take three weeks with two engineers instead of two weeks with three engineers as originally planned.
Another method of resource leveling is the resource-based method. This involves looking at the workload for each resource in a given work period and assigning a more realistic workload.
Resource leveling is the activity in which project teams encounter problems when developing their project schedules. If a company has multiple projects running simultaneously that require the same resources, problems can arise. Problems may occur when not enough attention is paid to resource allocations and their conflicts.
When conducting resource leveling heuristics, there are a number of details that must be taken into consideration. Asking the following questions will help you to determine where leveling is required or possible.
Does the activity have slack time?
If activities have little or no slack time, they are usually critical path activities. They are provided with the necessary resource requirements, when possible. If for example, activity A has zero float, activity B has a three-day float and activity C has a two-day float. Activity A is allocated resources first.
Is this activity high priority?DataWare Software Development (DSD) is currently working on a project to develop education software. The project manager has been informed of both a reverse resource allocation scheduling conflict and a resource-based conflict. He has already determined that each of these activities has slack time and neither is on the critical path.
If resources are limited, higher-priority activities are allocated resources before lower-priority activities. Activities that are higher priority are normally on the critical path. For example, if activity D is a critical path activity and activity B a non-critical activity, activity D is allocated resources before activity B.
Can this activity be split?
If resources for an activity are only available at particular times, splitting the activity may be required. For example, the resources for activity E are only available on Mondays, Wednesdays and Fridays. Therefore, the manager must split the activity into three non-consecutive days.
Is this a flagged activity?
If an activity is flagged, it means that a component of that activity has a significant detail attached. Flagged activities have a higher priority than others. For example, a computer design project may require a special part that is only available at a certain time. The activity requiring this part would be flagged.
Can the activity requirements be altered without affecting the overall project?
If an activity can be altered to reflect the availability of resources, then that activity is finished when the resources are available. For example, an activity requires two engineers 100 percent of the time: one is only available 75 percent of the time. The activity will be finished when the other resource is available.
The resource requirements call for two graphic artists. Unfortunately, only one is available. The project manager will have to perform resource leveling by lengthening the schedule so that the work to be done by two people can be done by one.
The schedule calls for the audio to be recorded for three different projects at the same time. When the project manager applies resource leveling heuristics, these three projects will take three days for audio instead of the one day originally scheduled.
Resource leveling requires a degree of common sense. If an adjustment does not seem realistic, don't make it as it may do more harm than good.
1 comment:
Tag: PM206A55. Let me share all of you about #5 Tips for Project Management Success,, I hope you enjoy it
1. Plan your day using time management techniques
As a project manager, time management skills are essential because you are dealing with a wide range of tasks that demand a quick turnaround time. Planning your day will go a long way in keeping you organized and increasing your productivity. Assist your task planning by using project management software which helps you track the work of you and your team.
If you are not very tech savvy, a simple to-do list can also be a great organizational tool. Prioritize your most important tasks by putting them at the top of the list and less important ones at the bottom. Having a visual plan of your daily tasks helps to keep you on track and aware of time.
Related post: Free ebook 104 secrets to become a great project manager
2. Include stakeholders in important project conversations
While you will have plenty of responsibilities regarding the project, don’t neglect your clients.
Good communication is essential is keeping both parties informed of project progression, curtailing scope creep, and apprised of changing requirements. Some clients may have different expectations when it comes to communication, so make sure to establish the frequency and type of communication (like emails, phone calls, and face-to-face conversations) at the beginning of your project.
Establishing communication expectations early helps alleviate stakeholder uncertainty about communication frequency and delivery.
3. Regularly communicate with your team
Daily team communication helps keep misunderstandings and unclear requirements under control. Keeping your team informed in every step of the project is essential to project management success.
For example, a study published by Procedia Technology found that good communication skills were the cornerstone of project management. The study examined over 300 “construction project managers, architects, construction managers, engineers and quantity surveyors” and their successes and failures on various construction projects.
4. Anticipate project setbacks
Even the best-laid plans often go awry.
Remember that even with a high amount of planning and attention to detail, your project may still encounter some challenges. Pay attention to complaints from stakeholders or colleagues, and other warning signs, like a missed deadline or cost overrun, that there may be a problem.
Preventing a crisis will keep your project running smoothly, save you a lot of time, and keep you, your team, and your stakeholders confident in progressing with the project.
Unfortunately not every complication can be avoided. Crisis management skills are essential for dealing with the unexpected. Project managers need to be flexible and pragmatic. Improvise and make sharp decisions when needed.
Related post: 92 free project management templates
5. Stay focused on the details
A common problem project managers encounter is having the project aims not aligned with the organization’s objectives. A great project manager will strategize a plan for the project to lead back to the overall success of the business.
Know your project’s scope by heart and avoid wandering outside of the project’s requirements. It’s too easy to get lost in minor details and forget what your focus is, so a well-planned project scope is essential for success.
And final, you should use KPI to measure effectiveness of the project, here are full list: 76 project management KPIs
Post a Comment