Project Management Foundations - Performing Resource Analysis and Creating the Resource Plan

June 2, 2011 | Author: PM Hut | Filed under: Project Management Guides, Project Plan Development, Resource Leveling, Scheduling

Project Management Foundations - Performing Resource Analysis and Creating the Resource Plan
By Steve Hart

In a previous article, I talked about resource loading your project schedule (estimating the resource needs, and loading resource estimates into your project schedule). Before you call your project schedule “complete”, it is a best practice to perform resource analysis & leveling, and create the resource plan. The resource plan is utilized to confirm the project resource assignments with resource managers, and it is a direct input to creating the labor component of the project budget.

Again the best practices areas associated with resource planning are:

  • How to estimate the resource requirements for schedule activities
  • How to load the resource assignments and work effort estimates into the project schedule
  • How to perform resource usage analysis, and resource leveling techniques
  • How to create the resource plan utilized to finalize resource assignments, and provide a key input to create the project budget

This article is focused on the last two – performing resource analysis & creating the resource plan

Resource Analysis & Leveling

The first decision to make when performing resource analysis is what is the proper time period to use for resource usage optimization. In other words, is it at the level of days, weeks or months that you need to make sure you have the right resources assigned to support planned project activities. For projects 3 months or greater, I find that it is most appropriate to perform resource analysis and leveling to the “month level” of precision. Attempting to level resources to a more granular level is not necessary to create a “workable” project schedule.

To start the resource analysis process, access the Resource View in your project management tool, and change the timescale to “months”. This view provides the number of planned hours for a resource for each month. Based upon this information, and the percentage each resource is allocated to the project, you have the information required to identify months in which resources are under or over allocated to project activities. Just because a resource (or a month) is highlighted in red does not mean you have a resource usage problem. It may just mean that a day or week is over allocated, and that does not necessarily represent a problem that requires adjustments to the schedule.

The following represents the best practices for resolving resource issues:

  • Look at the detail activities within the resource usage view for the period that is over or under loaded in the schedule
  • Challenge the resource hours (or resource % allocations) on specific activities
  • Look for opportunities to assign other resources
  • Look for opportunities to move activities up or back (pay attention to how resources are loaded in preceding and subsequent periods). Use dependencies to move the activities around (you are changing the soft dependency logic to level the resource loading).

Below is an example of the resource usage summary and detail views utilized to analyze and level resources.

Resource Usage Summary

Figure 1: Resource Usage Summary

Before making adjustments to the project schedule, it is recommended to save a “back-up” version of the project schedule (in case you do not like the results of the adjustments). Make the appropriate changes, and then review the impact on resource usage and key milestone dates. Based upon the impact of the changes, you may need to challenge specific assumptions to improve the milestone dates (e.g., durations, dependencies, resource availability).

Note: I do not recommend using the “Level Resources” function within the project management tool to perform resource leveling. This function attempts to automate the decision making process described above (with the default of moving dates based upon resource availability). Reworking the result of this automated process is generally more work (not to mention more frustrating) than manually reviewing and adjusting the schedule.

The Resource Graph (below) is another tool available within the project management tool that provides an excellent summary of resource utilization for each resource. This view provides a quick preview of the impact of schedule adjustments on resource utilization. It is also a valuable way to demonstrate the impact of alternative schedule solutions (“what if” scenarios) on resource utilization. Snapshots of this view are often utilized within core team or sponsor review sessions to communicate resourcing opportunities or challenges within the project schedule. Make sure you are solving resource issues based upon the “materiality threshold” established in the schedule management plan. Things are going to change throughout the project life cycle, therefore you are trying to get the resources leveled to a reasonable level – your goal is to arrive at a reasonable schedule (not the perfect schedule).

Resource Graph

Figure 2: Resource Graph

Creating the Resource Plan

Once you are satisfied with the reasonableness of the project schedule (timing of both key milestones and resource utilization), it is time to create a first cut of the resource plan. The resource plan provides a summary of the resource hours required to complete the project. The resource plan is used for the following:

  • Confirm resource allocations with resource providers
  • Key input to the labor component of the project budget

Steps to create the resource plan:

  • Create a list of the resources, sorted / grouped appropriately (e.g., by type of resource, internal vs. external) within the resource plan worksheet.
  • Cut and paste in the hours from the resource usage view (in the project management tool) into the spreadsheet.
  • “Adjust” the project hours to add in indirect project hours (activities that are not helpful to load directly into the project schedule). The hours for each resource in the Resource Plan should be compared to what is going to be “charged” to the project (% the resource is allocated to the project each month).
  • Review the plan for reasonableness. Reconcile/resolve significant differences between the Resource Plan and the Resource Usage view from your project schedule.

Resource Plan

Figure 3: Resource Plan

Note: The resource plan represents a worksheet built into the Project Budget Workbook. This approach enables pointing calculations directly to the planned hours in the resource plan to drive cost estimates on the labor budget worksheet.

Resource Planning Best Practices

In summary, the following are the best practices associated with the resource planning processes:

  • Do not add “noise” into the schedule by attempting to account for all hours expended on the project (activities in the project schedule should be limited to “direct” project activities). The hours reflected in the resource plan can be adjusted (generally increased) to account for indirect project hours. The resource plan should represent the hours that will be “charged” to the project by each resource (vs. the direct project activities planned in the project schedule for each resource).
  • Do not attempt to over-engineer the resource leveling process. The objective of the resource leveling process is to “smooth” the resource usage reflected in the project schedule, reducing the over and under allocation situations. Change is inevitable throughout the project life cycle, therefore your goal is to create a project schedule that can be effectively monitored and managed throughout the execution phase of the project – reasonableness, not perfection.

  • Plan to the appropriate time windows. Understanding the resource usage on a monthly basis is normally good enough to create a “workable” project schedule. In the context of this blog post, the term “workable” means a schedule that supports a timeline and budget that is understandable and defensible.

Steve Hart, PMP is the Practice Manager responsible for project leadership & delivery services for the Cardinal Solutions Group in the RTP area. He has 25 years of project management and technical leadership roles, and has developed an extensive practical knowledge that spans a wide variety of industries, and project delivery approaches. Steve recently transferred to the North Carolina Chapter of PMI from the Dayton Ohio PMI Chapter, where he was active as the editor of the chapter newsletter, and PMP certification instructor. You can read more from Steve Hart on his blog.

Share this article:
  • Facebook
  • LinkedIn
  • TwitThis

1 person has left a comment

One other item to consider for best practices is analyzing resource performance, as not all resources are equal. There are star players, workers, and weak links. For exampple star player might complete tasks, on average, 20% faster than your average worker, while a weak link takes 50% longer to complete a task.

You want to make sure your critical projects have star players on the team, and you need to identify weak links and bring them up to an acceptable level of performance.

Joe MacNish wrote on June 2, 2011 - 2:21 pm | Visit Link

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Project Management Categories