Human Resources

The Project Schedule Part 4 – Resource Assignments And Estimates

Professor of Project Management Project Planning ,
Planning

Once you have defined your Work Breakdown Structure (WBS) the next step in creating a schedule is to assign resources and estimates to each task (the lowest level items in your WBS). A starting point in assigning resources is to consult the “Roles & Responsibilities” matrix you created as part of the Project Charter. You are looking for the stakeholders that are in the category of “helping you execute your project”.

You may find that some WBS tasks need resources that have not yet been specifically identified as assigned to the project. In this case you will meet with the managers of the areas that have the resource expertise and agree on the assignment. In other cases you may need to contract for professional services. This should have been included in your Project Budget and the Procurement Plan. If not, you will have to use the formal Project Change Management process to alter the budget to include these services.

Microsoft Project allows you to assign resources to a task. You can also assign the percentage of the resource’s time that will be dedicated to the task. In addition, you can assign more than one resource to a given task.

Once you have resources assigned to a task you can attach estimates. You can estimate using “Duration” (the length of time the task will take independent of the resources assigned) or “Effort” (the amount of hours or days a task will take given undivided attention of the resources). Which one you use will depend on the type of project, type of task and organization culture. As a general rule I like to use “Effort” and let MS Project calculate the duration given the resource percent allocation and other tasks assigned to that resource.

When defining estimates, take into account the expertise of the resource(s) assigned to that task. An expert resource may complete a task much faster than a novice. Sometimes estimates are placed on a task prior to the resource assignment to get an idea of how the schedule will look. If you do this, remember to re-estimate once the specific resource is assigned.

There are many techniques to creating estimates. I will not address them all here. The most common are:

  • We’ve done this task before so we know how long it takes
  • The assigned resource supplies the estimate. Be careful with this one. People tend to be overly optimistic on how much time a task will take.
  • A small group of people with expertise in that task are asked to independently estimate the task, then the group discusses the discrepancies and comes to a consensus
  • Management may dictate the duration of the task in which case the PM may have to assign resources with more expertise or add resources (if feasible) to meet the deadline.

You can also use a 3-point estimate (optimistic, pessimistic and most likely) and calculate your estimate using PERT (I recommend you Google this term for the details). For a more advanced scheduling technique, you can investigate “Critical Chain and Buffer Management”. This technique that will need organizational buy-in from the top down.

Note: Much more detail on creating a Project Schedule can be found in my Kindle book “Project Management For The Real World”, available at

https://www.amazon.com/author/lettera

#projectmanagement

Advertisement

The Project Schedule Part 4 – Resource Assignments and Estimates

Professor of Project Management Project Planning ,

Planning

Once you have defined your Work Breakdown Structure (WBS) the next step in creating a schedule is to assign resources and estimates to each task (the lowest level items in your WBS). A starting point in assigning resources is to consult the “Roles & Responsibilities” matrix you created as part of the Project Charter. You are looking for the stakeholders that are in the category of “helping you execute your project”.

You may find that some WBS tasks need resources that have not yet been specifically identified as assigned to the project. In this case you will meet with the managers of the areas that have the resource expertise and agree on the assignment. In other cases you may need to contract for professional services. This should have been included in your Project Budget and the Procurement Plan. If not, you will have to use the formal Project Change Management process to alter the budget to include these services.

Microsoft Project allows you to assign resources to a task. You can also assign the percentage of the resource’s time that will be dedicated to the task. In addition, you can assign more than one resource to a given task.

Once you have resources assigned to a task you can attach estimates. You can estimate using “Duration” (the length of time the task will take independent of the resources assigned) or “Effort” (the amount of hours or days a task will take given undivided attention of the resources). Which one you use will depend on the type of project, type of task and organization culture. As a general rule I like to use “Effort” and let MS Project calculate the duration given the resource percent allocation and other tasks assigned to that resource.

When defining estimates, take into account the expertise of the resource(s) assigned to that task. An expert resource may complete a task much faster than a novice. Sometimes estimates are placed on a task prior to the resource assignment to get an idea of how the schedule will look. If you do this, remember to re-estimate once the specific resource is assigned.

There are many techniques to creating estimates. I will not address them all here. The most common are:

  • We’ve done this task before so we know how long it takes
  • The assigned resource supplies the estimate. Be careful with this one. People tend to be overly optimistic on how much time a task will take.
  • A small group of people with expertise in that task are asked to independently estimate the task, then the group discusses the discrepancies and comes to a consensus
  • Management may dictate the duration of the task in which case the PM may have to assign resources with more expertise or add resources (if feasible) to meet the deadline.

You can also use a 3-point estimate (optimistic, pessimistic and most likely) and calculate your estimate using PERT (I recommend you Google this term for the details). For a more advanced scheduling technique, you can investigate “Critical Chain and Buffer Management”. This technique that will need organizational buy-in from the top down.

Note: Much more detail on creating a Project Schedule can be found in my Kindle book “Project Management For The Real World”, available at

https://www.amazon.com/author/lettera

Building Blocks of a Successful Project Part 4 – Human Resources

Professor of Project Management Project Initiation , ,

Initiation

The first step in obtaining your project’s human resource needs is to create a “Roles/Responsibilities” matrix. In the first column, you define the project roles required. For example “Project Manager”, “Business Analyst”, “Subject Matter Experts”. These are not job titles but roles defined for the needs of the project. The second column describes the scope of responsibilities for that role. The third column is the name or names of those people assigned to that role. The rest of the columns contain contact information, and the assignee’s department and manager.

The next step is obtaining the commitments for these resources to work on the project. I have seen many projects given the approval to begin without the commitment (or even awareness) of key stakeholders (business units that will have project task assignments). This leaves the Project Manager in the position of negotiating with the business units for resource time and priority. This is typically the result of lack of Project Portfolio Management and control of the project intake process, especially in regard to resource capacity.

A best practice in Project Management is to secure the resource commitments prior to the approval of the Business Case. This means doing a thorough stakeholder analysis of all of the roles and responsibilities needed for the project. A brainstorming session with those having a broad knowledge of the business functions can help identify key stakeholders.

The Executive Sponsor (with support from the Project Manager) is responsible for communicating with the affected business units and securing the commitments. If these commitments have not been made and the project is directed to proceed, then this must be handled using formal Risk Management (which will be addressed in a future post).

In addition to having committed resources, they must also be the right resources. They must have skills that match the assigned roles. If they don’t and you have no resource alternatives then your project must include a plan for skills development and your task estimates must take into account the skill levels of the task assignee.

For your “core” team (the small group that attends almost all meetings and contribute to planning) you must make sure they are empowered as decision makers. If your team is constantly saying “I have to get my manager’s approval”, your schedule may be significantly impacted.