MANAGING PROJECT RESOURCES

Project CrashingThe process of accelerating a project is referred as crashing.Crashing a project relates to resource commitment; the more resources expended, the faster the project will finish.There are several reasons to crash a project:Initial schedule was too optimistic Market needs change and the project is in demand earlier than anticipatedThe project has slipped considerably behind scheduleThere are contractual late penalties

Project CrashingPrincipal methods for crashing are:Improving existing resources productivityChanging work methodsIncreasing the quantity of resourcesIncreasing the quantity of resources is the most commonly used method for project crashing. There are 2 approaches:Working current resources for longer hours (overtime, weekend work, etc.)Adding more personnel

Project CrashingTime-Cost Trade-Offs for Crashing ActivitiesFully expedited (no expense is spared)

Project CrashingIn analyzing crash options, the goal is to find the point at which time and cost trade-offs are optimized.

Various combinations of time-cost trade-offs for crash options can be determined by using the following formula:

Slope = crash cost normal cost normal time crash time

Project Crashing ExampleSUPPOSE: NORMAL ACTIVITY DURATION = 8 WEEKSNORMAL COST = $14,000CRASHED ACTIVITY DURATION = 5 WEEKSCRASHED COST = $23,000THE ACTIVITY COST SLOPE = 23,000 14,000 OR $9,000 = $3,000 per week 8 5 3 Cease crashing whenthe target completion time is reachedthe crash cost exceeds the penalty cost

Project Crashing Example Normal CrashedActivityDuration CostDuration CostA4 days$1,0003 days$2,000B5 days$2,5003 days$5,000C3 days$7502 days$1,200D7 days$3,5005 days$5,000E2 days$5001 day$2,000F5 days$2,0004 days$3,000G9 days$4,5007 days$6,300Calculate the per day costs for crashing each activityWhich are the most attractive candidates for crashing? Why?

Project Crashing Example ActivityPer Day CostA$1,000B$1,250C$450D$750E$1,500F$1,000G$900

Project Crashing Example When deciding on whether or not to crash project activities, a project manager was faced with the following information. Activities of the critical path are highlighted with an asterisk:

NormalCrashedActivityCostDurationExtra CostDurationA5,0004 weeks4,0003 weeksB*10,0005 weeks3,0004 weeksC3,5002 weeks3,5001 weekD*4,5006 weeks4,0004 weeksE*1,5003 weeks2,5002 weeksF7,5008 weeks5,0007 weeksG*3,0007 weeks2,5006 weeksH2,5006 weeks3,0005 weeks

Project Crashing Example The correct sequence for crashing activities is listed as:Activity E or G (they both cost $2,500 more)Activity E or GActivity BActivity D

Project Crashing Example Suppose project overhead costs accrued at a fixed rate of $500 per week. Assume that a project penalty clause kicks in after 19 weeks.The penalty charged is $5,000 per week.

DurationDirect CostsPenaltiesOverheadTotal21 weeks37,50010,00010,50058,00020 weeks40,0005,00010,00055,00019 weeks42,500- 0 -9,50052,00018 weeks45,500- 0 -9,00054,00016 weeks49,500- 0 -8,00056,500

Resource Allocation ProblemA shortcoming of most scheduling procedures is that they do not address the issues of resource utilization and availability.

Scheduling procedures tend to focus on time rather than physical resources.

Resource Allocation ProblemSchedules should be evaluated not merely in terms of meeting project milestones, but also in terms of the timing and use of scarce resources.

A fundamental measure of the project managers success in project management is the skill with which the trade-offs among performance, time, and cost are managed.

I can shorten this project by 1 day at a cost of $400. Should I do it?

Resource Allocation ProblemThe extreme points of the relationship between time use and resource use are the following:Time Limited: The project must be finished by a certain time, using as few resources as possible. But it is time, not resource usage, that is criticalResource Limited: The project must be finished as soon as possible, but without exceeding some specific level of resource usage or some general resource constraint

Resource LoadingResource loading describes the amounts of individual resources an existing schedule requires during specific time periods.

The loads (requirements) of each resource type are listed as a function of time period.

Resource loading gives a general understanding of the demands a project or set of projects will make on a firms resources.

Resource LoadingThe project manager must be aware of the flows of usage for each input resource throughout the life of the project.

It is the project managers responsibility to ensure that the required resources, in the required amounts, are available when and where they are needed.

Resource Loading Table

Resource Leveling (Smooting)Resource leveling aims to minimize the period-by-period variations in resource loading by shifting tasks within their slack allowances.The purpose is to create a smoother distribution of resource usage.Resource leveling, referred to as resource smoothing, has two objectives:To determine the resource requirements so that they will be available at the right time,To allow each activity to be scheduled with the smoothest possible transition across usage levels.

Resource Leveling (Smooting)Resource management is a multivariate, combinatorial problem, i.e. multiple solutions with many variables, the mathematically optimal solution may be difficult or infeasible.

More common approach to analyzing resource leveling problems is to apply some resource leveling heuristics.

Resource Leveling HeuristicsPrioritizing resource allocation include applying resources to activities:with the smallest amount of slackwith the smallest durationthat start earliestwith the most successor tasksrequiring the most resources

Resource Leveling StepsCreate a project activity network diagramCreate a table showing the resources required for each activity, durations, and the total float availableDevelop a time-phased resource loading tableIdentify any resource conflicts and begin to smooth the loading table using one or more heuristics

Resource Leveling Example

Critical path:A-C-F-H-K

Resource Leveling Example

Critical path:A-C-F-H-K

Resource Leveling Example

ActivityDurationTotal FloatResource Hours Needed Per WeekTotal ResourcesRequiredA50630B4128C50420D63318E61318F60212G43416H70321I53420J3526K50525Total194

Resource Leveling Example

Chart8

6

6

6

6

6

9

9

9

9

10

8

9

9

9

9

8

9

9

7

7

3

3

3

5

5

5

5

5

Project Days

Resource Requirements

Sheet1

Resource requirements by project duration

6

6

6

6

6

9

9

9

9

10

8

9

9

9

9

8

9

9

7

7

3

3

3

5

5

5

5

5

Sheet1

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

Project Days

Resource Requirements

Sheet2

Sheet3

Resource Leveling Example

On day 10 the required resource hours is 10If project is budgetted for up to 10 resource units per day, then it is acceptable.C, D, and E are all scheduled on this day and have require 4, 3, and 3 hours respectivelyWhich activity should be adjusted?C is on the critical path E has 1 day slack D has 3 days of slack (we can split the activity)

Resource Leveling Example

Resource Loading Chart

Another way to create a visual diagram of resource management problem is to use resource-loading charts.Resource conflicts can be seen in the resource-loading charts.They are used to display the amount of resources required as a function of time on a graph.Each activitys resource requirements are represented as a block (resource requirement over time).

Resource Loading ChartResource limit is set at 8 hourly units per day.Display the amount of resources required as a function of time.Start with a network diagram

Resource Loading ChartProduce a table that shows the duration, early start, late finish, slack, and resource(s) required for each activity.

ActivityResourceDurationESSlackLFA64004B21405C234411D74509E329011F6111012

Resource Loading ChartDraw an initial loading chart with each activity scheduled at its ES.

Resource imbalance

Resource Loading ChartRearrange activities within their slack to create a more level profile. Splitting C creates a more level project.

Resource Loading Chart

Critical Chain Project Management

Critical Chain Project Management (CCPM), which was developed and publicized by Dr. Eliyahu M. Goldratt (1997) in his book Critical Chain, is a novel approach for managing projects. Goldratt is well known in the operations management community as the inventor of the Theory of Constraints (TOC). TOC is a tool for managing repetitive production systems based on the principle that every system has a constraint, and system performance can only be improved by enhancing the performance of the constraining resource.

Critical Chain Project Management

CCPM identifies the critical chain as the set of tasks that results in the longest path to project completion after resource leveling. CCPM is the same as conventional project management except for the terminology "critical chain", which would otherwise be called the "leveled critical path".

Critical Chain Project Management

CCPM planning consists of recalculating the project schedule based on shortened task duration estimates. The rationale for shortening the original duration estimates is as follows:all tasks in the project are subject to some degree of uncertaintywhen asked to provide an estimate of the duration, the task owner adds a safety margin in order to be almost certain of completing the task on time. This means that, in general, task durations are overestimatedIn most cases, the task will not require the entire amount of safety margin and should be completed sooner than scheduledBecause the safety margin is internal to the task, if it is not needed, it is wasted.

Critical Chain Project Management

For project plan execution, CCPM prescribes the following principles:

Resources working on critical chain tasks are expected to work continuously on a single task at a time. They do not work on several tasks in parallel or suspend their critical tasks to do other workResources are to complete the task assigned as soon as possible, regardless of scheduled dates

Critical Chain Project Management

If the task is completed ahead of schedule, work on its successor is to begin immediately. If the task successor utilizes a critical resource for which a resource buffer has been defined, advance warning is provided to that resource at the point in time where the resource buffer beginsIf the task is completed past its planned completion date, as shown on the CCPM schedule, this is no reason for immediate concern, as the buffer will absorb the delay.

Source: http://en.wikipedia.org/wiki/Critical_chain