November 1, 2012 6 Comments
One of the consistent struggles of working in a “standalone” project management environment is the fact that you do not have visibility of the “total picture” associated with resources. Resource loading in MS Project provides visibility of resource utilization vs. capacity on your project – not across all resource commitments (e.g., other projects and operational activities). You can utilize the “max units %” to reflect that a resource is something less than 100% available to the project, but this information is only relevant if it is regularly reviewed and updated.
In my opinion, the most significant benefit associated with Enterprise Project Management tools such as MS Project Server, is providing enterprise wide visibility of planned resource utilization vs. capacity. As a by-product of maintaining resource loaded project and operational schedules within MS Project Server, up-to-date resource utilization information is available in a very flexible and easy to access and consume manner.
5 Benefits of Using MS Project Server for Resource Management
1. Consistent definition of resources – Maintaining the Global Resource Pool in MS Project Server ensures that resources are defined in a consistent manner across all projects. Without consistency it is difficult to efficiently roll-up resource utilization information from multiple projects. Key elements maintained in the Global Resource Pool are:
- Resource Name – It is important to establish a standard format for resource names (e.g., first name, last name).
- Role – The role field provides the ability to view groupings of resources that perform a similar function across projects (e.g., Business Analyst, SharePoint Developer).
- Base Calendar – The calendar field establishes the appropriate calendar for the resource (e.g., non-working days, working hours).
- Generic Resources – The generic resource flag provides the ability to create generic resources that are utilized for resource loading purposes prior to assigning a named resource to the project.
- RBS / Team Name / Department – MS Project Server provides a lot of flexibility to define the attributes/hierarchy specific to your organization (RBS, departments, and teams).
- Booking Type – This field is utilized to establish the default booking type for the resource assignment. “Committed” represents a firm commitment/assignment to the project, and “proposed” represents a future/planned assignment.
- Current Max Units % – Max units represents the % resources are available for work that is scheduled in MS Project Server. This field is utilized to calculate the resource capacity displayed on the resource availability charts.
- Rate – The rate fields establish the standard and overtime rates utilized for costing / billing purposes.
Below is a summary view of the Global Resource Pool. Views can be tailored to meet the needs of your organization in the same manner that views are created in SharePoint.
Below are screen shots of the details captured for each resource.
2. Understanding resource availability across multiple projects – The Resource Availability feature in MS Project Server provides very useful views of planned resource utilization vs. capacity. These views display resource utilization for specified periods (days, weeks, months) for each of the schedules maintained in MS Project Server. The views are available in both chart and table format (depicted below). In addition, you have the ability to view utilization for a single resource or a group of resources.
3. Visibility of Firm vs. Planned Resource Commitments – Within the “build team” function, you have the ability to specify whether resources are loaded into the schedule as firm commitments (committed) or planned future assignments (proposed). The proposed booking type is utilized for planning resource utilization at a high level for future projects/periods.
The chart below depicts including proposed hours (in addition to committed hours) in the resource availability view.
4. Ability View Availability for Resource Groups – MS Project Server provides the ability to select groups of resources to view total resource utilization vs. capacity for a specific role (e.g., business analysts). This feature is particularly helpful when you have resources that are interchangeable across projects.
The chart below depicts resource utilization vs. capacity by resource for the selected periods (days, weeks, months).
5. Ability to “Drill Down” to View Resource Utilization – From the resource availability views MS Project Server provides the ability to “drill down” to view the detail task assignments for a specific resource or group of resources. The resource assignment details provide resource and project managers with the information required to resolve specific “peaks” or “valleys” in resource utilization.
3 Critical Success Factors for Effective Resource Management
The following are 3 factors that are critical to realize the benefits of using MS Project Server for resource management within your project environment.
1. Resource Pool – Data captured in the resource pool must be defined and captured based upon the resource management needs of your organization. This success factor includes standard naming convention for resources, logical structure of the organization and team hierarchy, and meaningful definition of the project roles. These decisions drive how data is displayed within many of the resource management views.
2. Resource Capacity – The capacity line is driven from the Max Units % maintained for each resource. This percent must reflect the availability of the resource to be scheduled on the projects and operational activities maintained within the MS Project Server implementation. For example, if MS Project Server implementation does not include system support activities, then the Max Unit % should be reduced to reflect the time allocated to these activities for each resource. A process should be established for reviewing and updating this information on a regular basis (I recommend monthly or quarterly).
3. Resource Loaded Projects – The information associated with planned resource utilization on projects and operational activities is only as good as the accuracy and completeness of the resource loading within the individual project schedules. This is a very obvious statement, but I have seen many Enterprise Project Management implementations fail because the resource data within project schedules did not reflect reality. Coaching and mentoring of individual project managers is often required to ensure that project schedules are resource loaded and updated accurately throughout the project life cycle.